From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeremy Drake <cygwin@jdrake.com>
Cc: cygwin-patches@cygwin.com
Subject: Re: [PATCH] fchmodat/fstatat: fix regression with empty `pathname`
Date: Tue, 4 Jul 2023 17:50:18 +0200 (CEST) [thread overview]
Message-ID: <968b569c-02a7-b77a-7fde-236a7f12e85b@gmx.de> (raw)
In-Reply-To: <alpine.BSO.2.21.2306281142570.97921@resin.csoft.net>
Hi Jeremy,
On Wed, 28 Jun 2023, Jeremy Drake wrote:
> On Tue, 27 Jun 2023, Johannes Schindelin wrote:
>
> > In 4b8222983f (Cygwin: fix errno values set by readlinkat, 2023-04-18)
> > the code of `readlinkat()` was adjusted to align the `errno` with Linux'
> > behavior.
> >
> > I noticed this issue when one of my workflows failed consistently
> > while trying to untar an archive containing a symbolic link and
> > claiming this:
> >
> > Cannot change mode to rwxr-xr-x: Not a directory
> >
>
> I wonder if this is related to the issue from the thread
> https://cygwin.com/pipermail/cygwin/2023-May/253738.html (sounds like it).
For reference, this is the link I am looking at (because it has superior
thread navigation):
https://inbox.sourceware.org/cygwin/CAJQQdJjUarc1hkZCVX-GWD=Cq7XF4bnWE+ArzLxrUqWWpC7=rg@mail.gmail.com/T/#t
And yes, it looks like it's that very same issue.
> If so, tar was
> rebuilt to pick up the new behavior in 3.4.7 (presumably via configure
> checks), it may need another rebuild to pick up the fixed behavior after
> this fix.
Likely? But then, the patch in question should not _break_ the re-built
`tar`. Or does it?
Ciao,
Johannes
next prev parent reply other threads:[~2023-07-04 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 20:51 Johannes Schindelin
2023-06-28 18:45 ` Jeremy Drake
2023-07-04 15:50 ` Johannes Schindelin [this message]
2023-07-03 10:54 ` Corinna Vinschen
2023-07-04 15:45 ` Johannes Schindelin
2023-07-04 18:38 ` Corinna Vinschen
2023-07-12 11:50 ` Corinna Vinschen
2023-07-04 15:34 ` [PATCH v2] " Johannes Schindelin
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=968b569c-02a7-b77a-7fde-236a7f12e85b@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=cygwin-patches@cygwin.com \
--cc=cygwin@jdrake.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).