On 13/01/2021 at 17:52, Ken Brown via Cygwin wrote:
This turned out to be a Cygwin bug, which has now been fixed.
I upgraded again tar to version 1.34-1: fail.
Then I upgraded to cygwin 3.20.0-1 using official setup-x86.exe: pass!
Many thanks for this fix. Highly appreciated.
Kind regards,
have you tried the Cygwin snapshot as suggested in:
https://sourceware.org/pipermail/cygwin/2021-January/247418.html
The snapshot is hard to use in headless CI systems because the provided
archive contains a cygwin dll, so it cannot be patched from within
cygwin and my experience with doing
Hi Marco,
have you tried the Cygwin snapshot as suggested in:
https://sourceware.org/pipermail/cygwin/2021-January/247418.html
sorry, I somehow missed this message. I will try this and report if it
works.
Thanks!
Best regards,
Michael
--
Problem reports:
On 30.01.2021 15:58, Michael Soegtrop via Cygwin wrote:
Dear Cygwin Team,
is there an update on this? Apparently tar is broken on Cygwin 32 since
the latest update (it works fine on 64 bit Cygwin) and afaik there is no
way to install specific package versions from the command line as would
Dear Cygwin Team,
is there an update on this? Apparently tar is broken on Cygwin 32 since
the latest update (it works fine on 64 bit Cygwin) and afaik there is no
way to install specific package versions from the command line as would
be possible via the Setup UI, so I can't easily roll back
On 1/13/2021 4:07 PM, Morgan King via Cygwin wrote:
On 13 January 2021 19:02, Corinna Vinschen via Cygwin wrote:
On Jan 13 11:52, Ken Brown via Cygwin wrote:
On 1/11/2021 2:57 PM, Morgan King via Cygwin wrote:
Hello,
I am experiencing the same issue with tar and I am able to reproduce it
On 13 January 2021 19:02, Corinna Vinschen via Cygwin wrote:
> On Jan 13 11:52, Ken Brown via Cygwin wrote:
> > On 1/11/2021 2:57 PM, Morgan King via Cygwin wrote:
> > > Hello,
> > >
> > > I am experiencing the same issue with tar and I am able to reproduce it
> following the steps at:
> > >
On Jan 13 11:52, Ken Brown via Cygwin wrote:
> On 1/11/2021 2:57 PM, Morgan King via Cygwin wrote:
> > Hello,
> >
> > I am experiencing the same issue with tar and I am able to reproduce it
> > following the steps at:
> > https://lists.gnu.org/archive/html/bug-tar/2011-08/msg6.html
> >
> >
On 1/11/2021 2:57 PM, Morgan King via Cygwin wrote:
Hello,
I am experiencing the same issue with tar and I am able to reproduce it
following the steps at:
https://lists.gnu.org/archive/html/bug-tar/2011-08/msg6.html
This issue only appears to occur when using 32-bit Cygwin, I am unable to
On Jan 12 12:49, Ken Brown via Cygwin wrote:
> On 1/12/2021 12:15 PM, Corinna Vinschen wrote:
> > On Jan 12 11:55, Ken Brown via Cygwin wrote:
> > > [...]
> > > This appears to be a bug in fstat in 32-bit Cygwin. Here's what I'm
> > > seeing
> > > in gdb, using an unoptimized build of
Ken Brown via Cygwin writes:
[…]
> I don't see how that could be expected to work, since several members
> of struct __stat32 have different sizes than the corresponding members
> of struct stat. I wonder if it worked by accident in the past, but
> the problem is just showing up with newer gcc
On 1/12/2021 12:15 PM, Corinna Vinschen wrote:
On Jan 12 11:55, Ken Brown via Cygwin wrote:
On 1/11/2021 6:50 PM, Ken Brown via Cygwin wrote:
On 1/11/2021 2:57 PM, Morgan King via Cygwin wrote:
Hello,
I am experiencing the same issue with tar and I am able to reproduce
it following the steps
On Jan 12 11:55, Ken Brown via Cygwin wrote:
> On 1/11/2021 6:50 PM, Ken Brown via Cygwin wrote:
> > On 1/11/2021 2:57 PM, Morgan King via Cygwin wrote:
> > > Hello,
> > >
> > > I am experiencing the same issue with tar and I am able to reproduce
> > > it following the steps at:
> > >
On 1/11/2021 6:50 PM, Ken Brown via Cygwin wrote:
On 1/11/2021 2:57 PM, Morgan King via Cygwin wrote:
Hello,
I am experiencing the same issue with tar and I am able to reproduce it
following the steps at:
https://lists.gnu.org/archive/html/bug-tar/2011-08/msg6.html
This issue only
On 12.01.2021 09:18, ASSI wrote:
Ken Brown via Cygwin writes:
I can confirm this. Running the tar command under gdb shows a problem
at gnu/fchmodat.c:94:
94if (S_ISLNK (st.st_mode))
That should be foolproof, but apparently isn't.
Unfortunately the handful of commits that
Ken Brown via Cygwin writes:
> I can confirm this. Running the tar command under gdb shows a problem
> at gnu/fchmodat.c:94:
>
> 94if (S_ISLNK (st.st_mode))
That should be foolproof, but apparently isn't.
> Here st is a stat structure for directory/1, so S_ISLNK() should be
> true.
On 1/11/2021 2:57 PM, Morgan King via Cygwin wrote:
Hello,
I am experiencing the same issue with tar and I am able to reproduce it
following the steps at:
https://lists.gnu.org/archive/html/bug-tar/2011-08/msg6.html
This issue only appears to occur when using 32-bit Cygwin, I am unable to
Hello,
I am experiencing the same issue with tar and I am able to reproduce it
following the steps at:
https://lists.gnu.org/archive/html/bug-tar/2011-08/msg6.html
This issue only appears to occur when using 32-bit Cygwin, I am unable to
reproduce it using 64-bit Cygwin. I need to use
Vincent Rivière writes:
> 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/msg6.html
It's quite unlikely the same bug since there
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/msg6.html
This happens when symlinks are located before the target in the source
20 matches
Mail list logo
