From: Daniel Abrahamsson <daniel.abrahamsson@prover.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Cygwin test 3.5.0 tar symlinks error messages and failure status
Date: Wed, 21 Jun 2023 06:05:54 +0000 [thread overview]
Message-ID: <AS8PR08MB6936C91AC7D8AB22FD0EF37DE95DA@AS8PR08MB6936.eurprd08.prod.outlook.com> (raw)
("Manually" replying to an email in the archive (https://cygwin.com/pipermail/cygwin/2023-May/253742.html) since I don't have the original email anymore).
Achim Gratz wrote:
> Brian Inglis via Cygwin writes:
> > Problem writing tar (with Cygwin default sys) symlinks before target
> > created under Cygwin 3.5.0 - error messages are issued and tar exits
> > with failure status!
> […]
> > The only likely culprit between 3.4.6 and that commit seems to be
> > commit 2023-04-18 fa84aa4dd2fb43eaf7fcdfb040aef854f2f19d01 Cygwin: fix
> > errno values set by readlinkat.
> >
> > Still seems to work as expected despite the error messages and failure status.
> >
> > Runs without any messages or failure under Cygwin stable 3.4.6.
We started seeing the same problem after cygwin 3.4.7 was released (I note it includes the commit Brian mentions). As a workaround, we just ignore the exit code of the tar command, but understandably we would rather not do that. Extracting the same archive works fine without warnings or errors on Linux.
> The interface mentioned above is known to be wonky on various systems.
> You might need to re-build tar in oder for it to detect any changed
> level of wonkiness and adapt accordingly.
Do you mean that the tar package would need an update?
// Daniel
next reply other threads:[~2023-06-21 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 6:05 Daniel Abrahamsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-28 0:05 Brian Inglis
2023-05-28 5:42 ` Achim Gratz
2023-06-24 8:30 ` David Allsopp
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=AS8PR08MB6936C91AC7D8AB22FD0EF37DE95DA@AS8PR08MB6936.eurprd08.prod.outlook.com \
--to=daniel.abrahamsson@prover.com \
--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).