./archivers/gtar, The meta-package for the GNU tape archiver (tar)

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 1.35, Package name: gtar-1.35, Maintainer: pkgsrc-users

GNU tar, is a full-featured tar command that can access remote
and local magnetic tapes, tar files (ustar, POSIX, and V7), and
even compressed or gzipped versions of these.

This package provides easy installation of both the actual GNU
tape archiver and its associated info documentation.


Required to run:
[archivers/gtar-info] [archivers/gtar-base]

Required to build:
[pkgtools/cwrappers]

Master sites: (Expand)

Filesize: 2262.898 KB

Version history: (Expand)


CVS history: (Expand)


   2023-08-06 09:23:08 by Adam Ciarcinski | Files touched by this commit (6) | Package updated
Log message:
gtar: updated to 1.35

version 1.35

* Fail when building GNU tar, if the platform supports 64-bit time_t
  but the build uses only 32-bit time_t.

* Leave the devmajor and devminor fields empty (rather than zero) for
  non-special files, as this is more compatible with traditional tar.

* Bug fixes

** Fix interaction of --update with --wildcards.

** When extracting archives into an empty directory, do not create
   hard links to files outside that directory.

** Handle partial reads from regular files.

** Warn "file changed as we read it" less often.
   Formerly, tar warned if the file's size or ctime changed.
   However, this generated a false positive if tar read a file
   while another process hard-linked to it, changing its ctime.
   Now, tar warns if the file's size, mtime, user ID, group ID,
   or mode changes.  Although neither heuristic is perfect,
   the new one should work better in practice.

** Fix --ignore-failed-read to ignore file-changed read errors
   as far as exit status is concerned.  You can now suppress file-changed
   issues entirely with --ignore-failed-read --warning=no-file-changed.

** Fix --remove-files to not remove a file that changed while we read it.

** Fix --atime-preserve=replace to not fail if there was no need to replace,
   either because we did not read the file, or the atime did not change.

** Fix race when creating a parent directory while another process is
   also doing so.

** Fix handling of prefix keywords not followed by "." in pax headers.

** Fix handling of out-of-range sparse entries in pax headers.

** Fix handling of --transform='s/s/@/2'.

** Fix treatment of options ending in / in files-from list.

** Fix crash on 'tar --checkpoint-action exec=\"'.

** Fix low-memory crash when reading incremental dumps.

** Fix --exclude-vcs-ignores memory allocation misuse.
   2021-02-18 11:33:54 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
gtar*: update to 1.34

version 1.34 - Sergey Poznyakoff, 2021-02-13

* Fix extraction over pipe (savannah bug #60002)

* Fix memory leak in read_header (savannah bug #59897)

* Fix extraction when . and .. are unreadable

See https://lists.gnu.org/archive/html/bug-tar/2021-01/msg00012.html

* Gracefully handle duplicate symlinks when extracting

See https://lists.gnu.org/archive/html/bug-tar/2021-01/msg00026.html

* Re-initialize supplementary groups when switching to user privileges
   2021-01-12 13:10:27 by Ryo ONODERA | Files touched by this commit (5)
Log message:
gtar: Update to 1.33

Changelog:
version 1.33 - Sergey Poznyakoff, 2021-01-07

* POSIX extended format headers do not include PID by default

The intent is to make binary-equivalent PAX archives easy to create.  If
POSIXLY_CORRECT is set, the POSIX standard default is used, which embeds
the pid.

* --delay-directory-restore works for archives with reversed member ordering

* Fix extraction of a symbolic link hardlinked to another symbolic link

* Wildcards in exclude-vcs-ignore mode don't match slash

* Fix the --no-overwrite-dir option

Given this option, previous versions of tar failed to preserve
permissions of empty directories and to create files under directories
owned by the current user that did not have the S_IWUSR bit set.

* Fix handling of chained renames in incremental backups

* Link counting works for file names supplied with -T

* Accept only position-sensitive (file-selection) options in file list files.

Using such options as -f, -z, etc. is senseless in a file list file and
bypasses option consistency checks in decode_options.  Therefore,
only options related to file selection (a.k.a position-sensitive options)
are allowed in file list files.
   2020-01-19 00:36:14 by Roland Illig | Files touched by this commit (3046)
Log message:
all: migrate several HOMEPAGEs to https

pkglint --only "https instead of http" -r -F

With manual adjustments afterwards since pkglint 19.4.4 fixed a few
indentations in unrelated lines.

This mainly affects projects hosted at SourceForce, as well as
freedesktop.org, CTAN and GNU.
   2019-05-02 22:27:43 by Sebastian Wiedenroth | Files touched by this commit (3)
Log message:
gtar: fix build on SunOS

resolve conflict with sys/limits.h
   2019-02-24 16:18:45 by Thomas Klausner | Files touched by this commit (3) | Package updated
Log message:
gtar: update to 1.32

version 1.32 - Sergey Poznyakoff, 2019-02-23

* Fix the use of --checkpoint without explicit --checkpoint-action

* Fix extraction with the -U option

See http://lists.gnu.org/archive/html/bug-tar/2019-01/msg00015.html,
for details

* Fix iconv usage on BSD-based systems

* Fix possible NULL dereference (savannah bug #55369)

* Improve the testsuite
   2019-01-05 00:16:12 by Ryo ONODERA | Files touched by this commit (2)
Log message:
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.
   2018-03-11 18:28:08 by Thomas Klausner | Files touched by this commit (3) | Package updated
Log message:
gtar: update to 1.30

version 1.30 - Sergey Poznyakoff, 2017-12-17

* Member names containing '..' components are now skipped when extracting.

This fixes tar's behavior to match its documentation, and is a bit
safer when extracting untrusted archives over old files (an unsafe
practice that the tar manual has long recommended against).

* Report erroneous use of position-sensitive options.

During archive creation or update, tar keeps track of positional
options (see the manual, subsection 3.4.4 "Position-Sensitive
Options"), and reports those that had no effect.  For example, when
invoked as

   tar -cf a.tar . --exclude '*.o'

tar will create the archive, but will exit with status 2, having
issued the following error message

   tar: The following options were used after non-optional
   arguments in archive create or update mode.  These options are
   positional and affect only arguments that follow them.  Please,
   rearrange them properly.
   tar: --exclude '*.o' has no effect
   tar: Exiting with failure status due to previous errors

* --numeric-owner now affects private headers too.

This helps the output of 'tar' to be more deterministic.

* Fixed the --delay-directory-restore option

In some cases tar would restore the directory permissions too early,
causing subsequent link extractions in that directory to fail.

* The --warnings=failed-read option

This new warning control option suppresses warning messages about
unreadable files and directories. It has effect only if used together
with the --ignore-failed-read option.

* The --warnings=none option now suppresses all warnings

This includes warnings about unreadable files produced when
--ignore-failed-read is in effect. To output these, use
--warnings=none --warnings=no-failed-read.

* Fix reporting of hardlink mismatches during compare

Tar reported incorrect target file name in the 'Not linked to'
diagnostic message.