kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/archivers/gtar-base/distinfo

11 lines
672 B
Text
Raw Normal View History

Update to 1.31 Changelog: version 1.31 - Sergey Poznyakoff, 2019-01-02 * Fix heap-buffer-overrun with --one-top-level. Bug introduced with the addition of that option in 1.28. * Support for zstd compression New option '--zstd' instructs tar to use zstd as compression program. When listing, extractng and comparing, zstd compressed archives are recognized automatically. When '-a' option is in effect, zstd compression is selected if the destination archive name ends in '.zst' or '.tzst'. * The -K option interacts properly with member names given in the command line Names of members to extract can be specified along with the "-K NAME" option. In this case, tar will extract NAME and those of named members that appear in the archive after it, which is consistent with the semantics of the option. Previous versions of tar extracted NAME, those of named members that appeared before it, and everything after it. * Fix CVE-2018-20482 When creating archives with the --sparse option, previous versions of tar would loop endlessly if a sparse file had been truncated while being archived.
2019-01-05 00:16:12 +01:00
$NetBSD: distinfo,v 1.42 2019/01/04 23:16:12 ryoon Exp $
+ move the distfile digest/checksum value from files/md5 to distinfo + move the patch digest/checksum values from files/patch-sum to distinfo
2001-04-17 12:10:18 +02:00
Update to 1.31 Changelog: version 1.31 - Sergey Poznyakoff, 2019-01-02 * Fix heap-buffer-overrun with --one-top-level. Bug introduced with the addition of that option in 1.28. * Support for zstd compression New option '--zstd' instructs tar to use zstd as compression program. When listing, extractng and comparing, zstd compressed archives are recognized automatically. When '-a' option is in effect, zstd compression is selected if the destination archive name ends in '.zst' or '.tzst'. * The -K option interacts properly with member names given in the command line Names of members to extract can be specified along with the "-K NAME" option. In this case, tar will extract NAME and those of named members that appear in the archive after it, which is consistent with the semantics of the option. Previous versions of tar extracted NAME, those of named members that appeared before it, and everything after it. * Fix CVE-2018-20482 When creating archives with the --sparse option, previous versions of tar would loop endlessly if a sparse file had been truncated while being archived.
2019-01-05 00:16:12 +01:00
SHA1 (tar-1.31.tar.bz2) = 2a0a6f04b9b51136836f1344b555076ab15ed03e
RMD160 (tar-1.31.tar.bz2) = 7880d038dcc1f1152189633f9900e013dcfb848c
SHA512 (tar-1.31.tar.bz2) = 0f4d00e08d56a8f8c32aac0afa2845397efb8ad72eaa6af47334cef9612adb1a4b91406bdc2c3a2cf1b9cc8b92c12735a331e0d137b24f66703f6af6219464f6
Size (tar-1.31.tar.bz2) = 2946047 bytes
Fix problems with xattr detection on OS X using upstream patch. Patch found and adapted for pkgsrc by J. Lewis Muir, with further changes by myself to avoid auto* dependencies.
2014-08-21 22:44:16 +02:00
SHA1 (patch-Makefile.in) = 78cc142b9370317c52215c106ea1e7217e71f9b5
(pkgsrc) - two patches are removed, upstream change (upstream) - Updated archivers/gtar to 1.29 Updated archivers/gtar-base to 1.29 Updated archivers/gtar-info to 1.29 ------------------------------------ version 1.29 - Sergey Poznyakoff, 2016-05-16 * New options: --verbatim-files-from, --no-verbatim-files-from The --verbatim-files-from option instructs tar to treat each line read from a file list as a file name, even if it starts with a dash. File lists are supplied with the --files-from (-T) option. By default, each line read from a file list is first stripped off the leading and trailing whitespace and, if the result begins with a dash, it is treated as tar command line option. Use the --verbatim-files-from option to disable this special handling. This facilitates the use of tar with file lists created automatically (e.g. by find(1) command). This option affects all --files-from options that occur after it in the command line. Its effect is reverted by the --no-verbatim-files-from option. * --null option reads file names verbatim The --null option implies --verbatim-files-from. I.e. each line read from null-delimited file lists is treated as a file name. This restores the documented behavior, which was broken in version 1.27. * New options: --owner-map=FILE and --group-map=FILE These two options provide fine-grained control over what user/group names (or IDs) should be mapped when adding files to archive. For both options, FILE is a plain text file with user or group mappings. Empty lines are ignored. Comments are introduced with # sign (unless quoted) and extend to the end of the corresponding line. Each non-empty line defines translation for a single UID (GID). It must consist of two fields, delimited by any amount of whitespace: OLDNAME NEWNAME[:NEWID] OLDNAME is either a valid user (group) name or a ID prefixed with +. Unless NEWID is supplied, NEWNAME must also be either a valid name or a +ID. Otherwise, both NEWNAME and NEWID need not be listed in the system user database. * New option --clamp-mtime The new --clamp-mtime option changes the behavior of --mtime to only use the time specified if the file mtime is newer than the given time. The --clamp-mtime option can only be used together with --mtime. Typical use case is to make builds reproducible: to loose less information, it's better to keep the original date of an archive, except for files modified during the build process. In that case, using reference (and thus reproducible) timestamps for the latter is good enough. See <https://wiki.debian.org/ReproducibleBuilds> for more information. * Deprecated --preserve option removed * Sparse file detection Tar now uses SEEK_DATA/SEEK_HOLE on systems that support it. This allows for considerable speed-up in sparse-file detection. New option --hole-detection is provided, that allows the user to select the algorithm used for hole detection. Available arguments are: --hole-detection=seek Use lseek(2) SEEK_DATA and SEEK_HOLE "whence" parameters. --hole-detection=raw Scan entire file before storing it to determine where holes are located. The default is to use "seek" whenever possible, and fall back to "raw" otherwise.
2016-05-31 17:04:51 +02:00
SHA1 (patch-gnu_readlinkat.c) = ce9869bfcd75005bb4ddac4e3223df01a26a2b29
Fix problems with xattr detection on OS X using upstream patch. Patch found and adapted for pkgsrc by J. Lewis Muir, with further changes by myself to avoid auto* dependencies.
2014-08-21 22:44:16 +02:00
SHA1 (patch-lib_xattr-at.c) = c69631c118558c0c056feb5b55188b2b4c92cc19
Add credit to Fink for the diagnosis and suggested fix.
2015-01-26 13:41:53 +01:00
SHA1 (patch-src_system.c) = cd9f7358fa93ed0ba4a1b3fffdae5d7f84ef4791
Reference in a new issue Copy permalink