Re: cygwin Rsync x32 issue

2021-02-14 Thread Jim Brain
On 2/14/2021 8:21 PM, Ken Brown via Cygwin wrote:   strace -o rsync.strace rsync... Then post rsync.strace somewhere where people can look at it. https://www.dropbox.com/s/v1n9i77jhq3b3zh/rsync.strace?dl=0 Jim -- Problem reports: https://cygwin.com/problems.html FAQ:

Re: cygwin Rsync x32 issue

2021-02-14 Thread Ken Brown via Cygwin
On 2/14/2021 9:04 PM, Jim Brain wrote: On 2/14/2021 6:01 PM, Ken Brown via Cygwin wrote: On 2/13/2021 11:33 PM, Jim Brain wrote: There was a bug in Cygwin's implementation of fstatat(2) that was recently reported and fixed.  It affected 32-bit only.  On the chance that you've bumped into t

Re: cygwin Rsync x32 issue

2021-02-14 Thread Jim Brain
On 2/14/2021 6:01 PM, Ken Brown via Cygwin wrote: On 2/13/2021 11:33 PM, Jim Brain wrote: There was a bug in Cygwin's implementation of fstatat(2) that was recently reported and fixed.  It affected 32-bit only.  On the chance that you've bumped into the same bug, you could try a snapshot of

Re: Cygwin doesn't handle SIGWINCH properly in Windows Terminal

2021-02-14 Thread Takashi Yano via Cygwin
On Sun, 14 Feb 2021 12:44:32 -0800 L A Walsh wrote: > On 2021/02/14 00:43, Takashi Yano via Cygwin wrote: > > This is because cygwin console handles SIGWINCH when the input > > messages is processed. If the process does not call either read() > > or select(), SIGWINCH will not be sent. This is the

Re: Cygwin doesn't handle SIGWINCH properly in Windows Terminal

2021-02-14 Thread Takashi Yano via Cygwin
On Sun, 14 Feb 2021 12:44:32 -0800 L A Walsh wrote: > On 2021/02/14 00:43, Takashi Yano via Cygwin wrote: > > This is because cygwin console handles SIGWINCH when the input > > messages is processed. If the process does not call either read() > > or select(), SIGWINCH will not be sent. This is the

Re: cygwin Rsync x32 issue

2021-02-14 Thread Ken Brown via Cygwin
On 2/13/2021 11:33 PM, Jim Brain wrote: I perused the archive and did not see anything noted about this, but please forgive me if it's been discussed. Server: ubuntu 2004, running rsync 3.1.3 protocol version 31 client Windows 10 x64. When calling rsync x64 3.2.4dev, transfer works fine. Whe

Re: Cygwin doesn't handle SIGWINCH properly in Windows Terminal

2021-02-14 Thread L A Walsh
On 2021/02/14 00:43, Takashi Yano via Cygwin wrote: This is because cygwin console handles SIGWINCH when the input messages is processed. If the process does not call either read() or select(), SIGWINCH will not be sent. This is the long standing problem of the implementation and hard to fix. ..

[ANNOUNCEMENT] Updated: python packages

2021-02-14 Thread Marco Atzeri via Cygwin-announce via Cygwin
Several python packages have been updated python{36,37,38}-opengl-3.1.5-1 python{36,37,38}-opengl-accelerate-3.1.5-1 python{36,37,38}-pygame-2.0.1-1 and the following added python{36,37,38}-pkgconfig-1.5.1-1 CYGWIN CHANGES As python2 is no longer supported htt

Re: Cygwin doesn't handle SIGWINCH properly in Windows Terminal

2021-02-14 Thread Takashi Yano via Cygwin
On Sat, 13 Feb 2021 20:39:39 +1000 Alvin Seville wrote: > Windows build number: Win32NT 10.0.19042.0 Microsoft Windows NT 10.0.19042.0 > Windows Terminal version (if applicable): 1.5.10271.0 > > Script to reproduce this issue: > > #!/usr/bin/env bashfunction outputText() > { > local text=$1 >

[ANNOUNCEMENT] Updated: python packages

2021-02-14 Thread Marco Atzeri via Cygwin-announce via Cygwin
Several python packages have been updated python{36,37,38}-mutagen-1.45.1-1 python{36,37,38}-h5py-3.1.0-1 and the following added python{36,37,38}-musicbrainzngs-0.7.1-1 python{36,37,38}-py3c-1.3.1-1 python{36,37,38}-zipp-3.4.0-1 CYGWIN CHANGES As pytho