From: "Vincent Rivière" <vincent.riviere@freesbee.fr>
To: cygwin@cygwin.com
Subject: tar 1.33 symlinks : Cannot change mode to...
Date: Mon, 11 Jan 2021 16:27:11 +0100 [thread overview]
Message-ID: <1655a453-25d0-3e71-2e43-0072a795c1f4@freesbee.fr> (raw)
In-Reply-To: <announce.87lfd0uciv.fsf@Rainer.invalid>
On 10/01/2021 à 14:50, Achim Gratz wrote:
> GNU tar has been updated to the latest upstream release 1.33.
Unfortunately it has reintroduced this old bug:
https://lists.gnu.org/archive/html/bug-tar/2011-08/msg00006.html
This happens when symlinks are located before the target in the source
archive. The example given in the above link produces this output:
$ tar -xf directory.tar
tar: directory/1: Cannot change mode to rwxr-xr-x: No such file or directory
tar: directory/2: Cannot change mode to rwxr-xr-x: No such file or directory
tar: directory/3: Cannot change mode to rwxr-xr-x: No such file or directory
tar: Exiting with failure status due to previous errors
Note that files and symlinks are properly extracted, but $? is set to 2 so
scripts can fail.
tar 1.32-2 : ok
tar 1.33-1 : bug
This needs to be fixed.
Regards,
--
Vincent Rivière
next prev parent reply other threads:[~2021-01-11 15:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 13:50 [ANNOUNCEMENT] Updated: tar-1.33-3 Achim Gratz
2021-01-11 15:27 ` Vincent Rivière [this message]
2021-01-11 17:54 ` tar 1.33 symlinks : Cannot change mode to Achim Gratz
2021-01-11 19:57 Morgan King
2021-01-11 23:50 ` Ken Brown
2021-01-12 8:18 ` ASSI
2021-01-12 10:32 ` Marco Atzeri
2021-01-12 16:55 ` Ken Brown
2021-01-12 17:15 ` Corinna Vinschen
2021-01-12 17:49 ` Ken Brown
2021-01-12 18:16 ` Corinna Vinschen
2021-01-12 18:03 ` Achim Gratz
2021-01-30 14:58 ` Michael Soegtrop
2021-01-30 15:11 ` Marco Atzeri
2021-01-30 15:36 ` Michael Soegtrop
2021-01-30 16:57 ` Michael Soegtrop
2021-01-13 16:52 ` Ken Brown
2021-01-13 19:02 ` Corinna Vinschen
2021-01-13 21:07 ` Morgan King
2021-01-13 21:12 ` Ken Brown
2021-04-01 21:23 ` Vincent Rivière
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1655a453-25d0-3e71-2e43-0072a795c1f4@freesbee.fr \
--to=vincent.riviere@freesbee.fr \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).