[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug-tar] tar-1.30 released [stable]
From: |
Sergey Poznyakoff |
Subject: |
[Bug-tar] tar-1.30 released [stable] |
Date: |
Sun, 17 Dec 2017 14:27:47 +0200 |
Hello,
This is to announce the release of GNU tar 1.30. Please see below
for a list of noteworthy changes.
Here are the compressed sources:
http://ftp.gnu.org/gnu/tar/tar-1.30.tar.gz (4.0MB)
http://ftp.gnu.org/gnu/tar/tar-1.30.tar.bz2 (2.8MB)
http://ftp.gnu.org/gnu/tar/tar-1.30.tar.xz (2.1MB)
Here are the GPG detached signatures[*]:
http://ftp.gnu.org/gnu/tar/tar-1.30.tar.gz.sig
http://ftp.gnu.org/gnu/tar/tar-1.30.tar.bz2.sig
http://ftp.gnu.org/gnu/tar/tar-1.30.tar.xz.sig
Use a mirror for higher download bandwidth:
http://www.gnu.org/order/ftp.html
Here are the MD5 and SHA1 checksums:
e0c5ed59e4dd33d765d6c90caadd3c73 tar-1.30.tar.gz
8404e4c1fc5a3000228ab2b8ad674a65 tar-1.30.tar.bz2
2d01c6cd1387be98f57a0ec4e6e35826 tar-1.30.tar.xz
4f83a5e9ab6a93ea7ff5fe9a7b0f17763c4f3dca tar-1.30.tar.gz
f56e89603eca86c3571f3cb40a34057ecd1e1086 tar-1.30.tar.bz2
0d442c4565f8131745a5dff1cd08f7eaa797f679 tar-1.30.tar.xz
[*] Use a .sig file to verify that the corresponding file (without the
.sig suffix) is intact. First, be sure to download both the .sig file
and the corresponding tarball. Then, run a command like this:
gpg --verify tar-1.30.tar.gz.sig
If that command fails because you don't have the required public key,
then run this command to import it:
gpg --keyserver keys.gnupg.net --recv-keys 3602B07F55D0C732
and rerun the 'gpg --verify' command.
This release was bootstrapped with the following tools:
Autoconf 2.69
Automake 1.14
Makeinfo 6.5
Gnulib v0.1-1693-g91e8348
Noteworthy changes in this release:
* 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.
Regards,
Sergey
- [Bug-tar] tar-1.30 released [stable],
Sergey Poznyakoff <=