Re: tar 1.33 symlinks : Cannot change mode to...

2021-01-12 Thread ASSI
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.

Re: tar 1.33 symlinks : Cannot change mode to...

2021-01-12 Thread Marco Atzeri via Cygwin
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 migh

[ANNOUNCEMENT] socat 1.7.4.1-1

2021-01-12 Thread Andrew Schulman via Cygwin-announce via Cygwin
socat 1.7.4.1-1 is now available in Cygwin. This release has bug fixes and a few new features. See the Release Notes[1] and CHANGES[2] files for details. socat is a relay for bidirectional data transfer between two independent data channels. Each channel may be a file, pipe, device (serial line et

Re: tar 1.33 symlinks : Cannot change mode to...

2021-01-12 Thread Ken Brown via Cygwin
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 appear

Re: tar 1.33 symlinks : Cannot change mode to...

2021-01-12 Thread Corinna Vinschen via Cygwin
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: > > > https://list

Re: tar 1.33 symlinks : Cannot change mode to...

2021-01-12 Thread Ken Brown via Cygwin
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

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

2021-01-12 Thread Matt D. via Cygwin
Operations like cp and rsync etc. should still work. The type of symbolic link to be created can be read from the file attributes of the one being copied. On Mon, Jan 4, 2021 at 10:46 AM Jeffrey Altman via Cygwin wrote: > > On 1/4/2021 10:27 AM, Matt D. via Cygwin (cygwin@cygwin.com) wrote: > >

Re: tar 1.33 symlinks : Cannot change mode to...

2021-01-12 Thread Achim Gratz
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 bec

Re: tar 1.33 symlinks : Cannot change mode to...

2021-01-12 Thread Corinna Vinschen via Cygwin
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 cygwin1.dll

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

2021-01-12 Thread Andrey Repin
Greetings, Matt D.! Please no top posting in this list. > On Mon, Jan 4, 2021 at 10:46 AM Jeffrey Altman via Cygwin wrote: >> >> On 1/4/2021 10:27 AM, Matt D. via Cygwin wrote: >> > I am using symbolic links native to Windows. My CYGWIN environment >> > variable has been set to "winsymlinks:nativ

Re: misterious GIT failure

2021-01-12 Thread matthew patton via Cygwin
Andrey wrote:> 1. Try rebasing your Cygwin install. deleted cygwin64 and installed to \cygwin. Immediate failure. No apparent grace period like before. > 2. See if your antivirus is interfering. Had corporate IT put me in a special exclusion group (supposedly) to no avail. See #1 On Friday,