summaryrefslogtreecommitdiff
path: root/archivers/gtar-base/patches/patch-ad
AgeCommit message (Collapse)AuthorFilesLines
2014-08-21Fix problems with xattr detection on OS X using upstream patch.wiz1-17/+0
Patch found and adapted for pkgsrc by J. Lewis Muir, with further changes by myself to avoid auto* dependencies.
2011-05-11Changes 1.26:adam1-2/+2
* Fix the --verify option, which broke in version 1.24. * Fix storing long sparse file names in PAX archives. * Fix correctness of --atime-preserve=replace. * Work around POSIX incompatibilities on FreeBSD, NetBSD and Tru64. * Fix bug with --one-file-system --listed-incremental.
2010-12-12Update gtar to 1.25.wiz1-4/+8
version 1.25 - Sergey Poznyakoff, 2010-11-07 * Fix extraction of empty directories with the -C option in effect. * Fix extraction of device nodes. * Make sure name matching occurs before eventual name transformation. Tar 1.24 changed the ordering of name matching and name transformation so that the former saw already transformed file names. This made it impossible to match file names in certain cases. It is fixed now. * Fix the behavior of tar -x --overwrite on hosts lacking O_NOFOLLOW. * Improve the testsuite. * Alternative decompression programs. If extraction from a compressed archive fails because the corresponding compression program is not installed and the following two conditions are met, tar retries extraction using an alternative decompressor: 1. Another compression program supported by tar is able to handle this compression format. 2. The compression program was not explicitly requested in the command line by the use of such options as -z, -j, etc. For example, if `compress' is not available, tar will try `gzip'. version 1.24 - Sergey Poznyakoff, 2010-10-24 * The --full-time option. New command line option `--full-time' instructs tar to output file time stamps to the full resolution. * Bugfixes. ** More reliable directory traversal when creating archives Tar now checks for inconsistencies caused when a file system is modified while tar is creating an archive. In the new approach, tar maintains a cache of file descriptors to directories, so it uses more file descriptors than before, but it adjusts to system limits on the number of file descriptors. Tar also takes more care when a file system is modified while tar is extracting from an archive. The new checks are implemented via the openat and related calls standardized by POSIX.1-2008. On an older system where these calls do not exist or do not return useful results, tar emulates the calls at some cost in efficiency and reliability. ** Symbolic link attributes When extracting symbolic links, tar now restores attributes such as last-modified time and link permissions, if the operating system supports this. For example, recent versions of the Linux kernel support setting times on symlinks, and some BSD kernels also support symlink permissions. ** --dereference consistency The --dereference (-h) option now applies to files that are copied into or out of archives, independently of other options. For example, if F is a symbolic link and archive.tar contains a regular-file member also named F, "tar --overwrite -x -f archive.tar F" now overwrites F itself, rather than the file that F points to. (To overwrite the file that F points to, add the --dereference (-h) option.) Formerly, --dereference was intended to apply only when using the -c option, but the implementation was not consistent. Also, the --dereference option no longer affects accesses to other files, such as archives and time stamp files. Symbolic links to these files are always followed. Previously, the links were usually but not always followed. ** Spurious error diagnostics on broken pipe. When receiving SIGPIPE, tar would exit with error status and "write error" diagnostics. In particular, this occurred if invoked as in the example below: tar tf archive.tar | head -n 1 ** --remove-files `Tar --remove-files' failed to remove a directory which contained symlinks to another files within that directory. ** --test-label behavior In case of a mismatch, `tar --test-label LABEL' exits with code 1, not 2 as it did in previous versions. The `--verbose' option used with `--test-label' provides additional diagnostics. Several volume labels may be specified in a command line, e.g.: tar --test-label -f archive 'My volume' 'New volume' 'Test volume' In this case, tar exits with code 0 if any one of the arguments matches the actual volume label. ** --label used with --update The `--label' option can be used with `--update' to prevent accidental update of an archive: tar -rf archive --label 'My volume' . This did not work in previous versions, in spite of what the docs said. ** --record-size and --tape-length (-L) options Usual size suffixes are allowed for these options. For example, -L10k stands for a 10 kilobyte tape length. ** Fix dead loop on extracting existing symlinks with the -k option.
2010-03-23Update gtar to 1.23 - fixes CVE2010-0624tez1-10/+10
Also: # Improved record size autodetection # Use of lseek on seekable archives # New command line option --warning # New command line option --level # Improved behavior if some files were removed during incremental dumps # Modification times of PAX extended headers # Time references in the --pax-option argument # Augmented environment of the --to-command script # Bugfixes: * Fix handling of hard link targets by -c --transform * Fix hard links recognition with -c --remove-files * Fix restoring files from backup (debian bug #508199) * Correctly restore modes and permissions on existing directories * The --remove-files option removes files only if they were succesfully stored in the archive * Fix storing and listing of the volume labels in POSIX format * Improve algorithm for splitting long file names (ustar format)
2008-05-18Update to GNU tar 1.20.tnn1-5/+5
All self-tests pass under NetBSD-current. Changes: 3.5 years worth of development; too much to list here.
2005-01-09update to gtar 1.15.1recht1-0/+13
changes: - enable installation of grmt changes in gtar: version 1.15.1 - Sergey Poznyakoff, 2004-12-21 This version fixes a bug introduced in 1.15 which caused tar to refuse to extract files from standard input. version 1.15 - Sergey Poznyakoff, 2004-12-20 * Compressed archives are recognised automatically, it is no longer necessary to specify -Z, -z, or -j options to read them. Thus, you can now run `tar tf archive.tar.gz'. * When restoring incremental dumps, --one-file-system option prevents directory hierarchies residing on different devices from being purged. With the previous versions of tar it was dangerous to create incremental dumps with --one-file-system option, since they would recursively remove mount points when restoring from the back up. This change fixes the bug. * Renamed --strip-path to --strip-components for consistency with the GNU convention. * Skipping archive members is sped up if the archive media supports seeks. * Restore script starts restoring only if it is given --all (-a) option, or some patterns. This is to prevent accidental restores. * `tar --verify' prints a warning if during archive creation some of the file names had their prefixes stripped off. * New option --exclude-caches instructs tar to exclude cache directories automatically on archive creation. Cache directories are those containing a standardized tag file, as specified at: http://www.brynosaurus.com/cachedir/spec.html * New configure option --with-rmt allows to specify full path name to the `rmt' utility. This supercedes DEFAULT_RMT_COMMAND variable introduced in version 1.14 * New configure variable DEFAULT_RMT_DIR allows to specify the directory where to install `rmt' utility. This is necessary since modifying --libexecdir as was suggested for version 1.14 produced a side effect: it also modified installation prefix for backup scripts (if --enable-backup-scripts was given). * Bugfixes: ** Fixed flow in recognizing files to be included in incremental dumps. ** Correctly recognize sparse archive members when used with -T option. ** GNU multivolume headers cannot store filenames longer than 100 characters. Do not allow multivolume archives to begin with such filenames. ** If a member with link count > 2 was stored in the archive twice, previous versions of tar were not able to extract it, since they were trying to link the file to itself, which always failed and lead to removing the already extracted copy. Preserve the first extracted copy in such cases. ** Restore script was passing improper argument to tar --listed option (which didn't affect the functionality, but was logically incorrect). ** Fixed verification of created archives. ** Fixed unquoting of file names containing backslash escapes (previous versions failed to recognize \a and \v). ** When attempting to delete a non-existing member from the archive, previous versions of tar used to overwrite last archive block with zeroes.
2002-11-30USE_PKGLOCALEDIR, remove unnecessary patches.salo1-13/+0
2002-11-20Update gtar packages to 1.13.25, with security fixes from redhat.bouyer1-21/+12
Summary of changes (see NEWS and Changelog from the distribution for details): - don't allow absolute paths, and path containing ../ * New option --overwrite-dir * New option --recursion (the default) that is the inverse of --no-recursion. * New options --anchored, --ignore-case, --wildcards, --wildcards-match-slash, and their negations (e.g., --no-anchored). Along with --recursion and --no-recursion, these options control how exclude patterns are interpreted. * The default interpretation of exclude patterns is now --no-anchored --no-ignore-case --recursion --wildcards --wildcards-match-slash. * The --no-recursion option now affects extraction too. * New options --no-same-owner, --no-same-permissions. * New option -y or --bzip2 for bzip2 compression, by popular request.
2002-08-25Merge packages from the buildlink2 branch back into the main trunk thatjlam1-3/+3
have been converted to USE_BUILDLINK2.
1999-09-18Copied from patch-ad,vkim1-0/+22