Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-03-06 Thread Rainer Emrich via Cygwin
Hi Corinna, hi Takashi, Am 06.03.2025 um 11:23 schrieb Rainer Emrich: Hi Corinna, hi Takashi, Am 06.03.2025 um 10:58 schrieb Corinna Vinschen via Cygwin: with a big "THANK YOU!" to Takashi, the "Lost connection" problem will be fixed in 3.6: a really big thank you to both of you. https://s

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-03-06 Thread Rainer Emrich via Cygwin
Hi Corinna, hi Takashi, Am 06.03.2025 um 10:58 schrieb Corinna Vinschen via Cygwin: with a big "THANK YOU!" to Takashi, the "Lost connection" problem will be fixed in 3.6: a really big thank you to both of you. https://sourceware.org/cgit/newlib-cygwin/commit/?id=691afb1f6d5a The next test

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-03-06 Thread Corinna Vinschen via Cygwin
Hi Rainer, with a big "THANK YOU!" to Takashi, the "Lost connection" problem will be fixed in 3.6: https://sourceware.org/cgit/newlib-cygwin/commit/?id=691afb1f6d5a The next test release cygwin-3.6.0-0.422.g691afb1f6d5a will contain the patch. Should be up in about an hour. Thanks, Corinna

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-03-03 Thread Jeremy Drake via Cygwin
On Fri, 21 Feb 2025, Jeremy Drake via Cygwin wrote: > I rebased msys2's msys2-runtime fork of cygwin on top of cygwin's master > branch, and then rebased git-for-windows' msys2-runtime on top of THAT. > > 1. Git for Windows's test suite still passes with that (which is nice, it > tended to hang wh

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-28 Thread Rainer Emrich via Cygwin
Hi Corinna, Am 28.02.2025 um 13:46 schrieb Corinna Vinschen via Cygwin: Hi Rainer, On Feb 17 20:37, Rainer Emrich via Cygwin wrote: Am 17.02.2025 um 18:00 schrieb Corinna Vinschen via Cygwin: On Feb 17 12:51, Rainer Emrich via Cygwin wrote: I'm facing a strange major issue with scp. The issu

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-28 Thread Corinna Vinschen via Cygwin
Hi Rainer, On Feb 17 20:37, Rainer Emrich via Cygwin wrote: > Am 17.02.2025 um 18:00 schrieb Corinna Vinschen via Cygwin: > > On Feb 17 12:51, Rainer Emrich via Cygwin wrote: > > > I'm facing a strange major issue with scp. The issue exists in all cygwin > > > version later than 3.5.3, > > > incl

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-25 Thread Corinna Vinschen via Cygwin
On Feb 25 14:49, Christian Franke via Cygwin wrote: > Corinna Vinschen via Cygwin wrote: > > [I sent this on 2024-02-14 to the cygwin-announce mailing list, > > but forgot to CC the cygwin mailing list. Doing it now...] > > > > > > Hi folks, > > > > we're planning the next major release in the

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-25 Thread Christian Franke via Cygwin
Corinna Vinschen via Cygwin wrote: [I sent this on 2024-02-14 to the cygwin-announce mailing list, but forgot to CC the cygwin mailing list. Doing it now...] Hi folks, we're planning the next major release in the next few (hopefully not more than two) weeks. ... Below you'll find a list of c

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-22 Thread Corinna Vinschen via Cygwin
On Feb 22 09:24, Jeremy Drake via Cygwin wrote: > On Sat, 22 Feb 2025, Corinna Vinschen via Cygwin wrote: > > > On Feb 21 14:35, Jeremy Drake via Cygwin wrote: > > > 2. This seems to have fixed a severe performance regression in Curl's test > > > suite (https://github.com/curl/curl/pull/16217) tha

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-22 Thread Jeremy Drake via Cygwin
On Sat, 22 Feb 2025, Corinna Vinschen via Cygwin wrote: > On Feb 21 14:35, Jeremy Drake via Cygwin wrote: > > 2. This seems to have fixed a severe performance regression in Curl's test > > suite (https://github.com/curl/curl/pull/16217) that I was recently > > looking into. My research tracked it

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-22 Thread Corinna Vinschen via Cygwin
On Feb 21 14:35, Jeremy Drake via Cygwin wrote: > I rebased msys2's msys2-runtime fork of cygwin on top of cygwin's master > branch, and then rebased git-for-windows' msys2-runtime on top of THAT. > > 1. Git for Windows's test suite still passes with that (which is nice, it > tended to hang when w

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-21 Thread Jeremy Drake via Cygwin
I rebased msys2's msys2-runtime fork of cygwin on top of cygwin's master branch, and then rebased git-for-windows' msys2-runtime on top of THAT. 1. Git for Windows's test suite still passes with that (which is nice, it tended to hang when we did this with 3.5.5). 2. This seems to have fixed a sev

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-19 Thread Corinna Vinschen via Cygwin
On Feb 19 09:54, Takashi Yano via Cygwin wrote: > On Wed, 19 Feb 2025 01:20:59 +0100 > Lionel Cons wrote: > > Something is very wrong with bash. If I redirect the output of xcopy > > or icacls into a bash variable, like stdout="$(icacls "$(cygpath -w > > "$PWD")")", then sometimes I get only a lett

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-18 Thread Takashi Yano via Cygwin
On Wed, 19 Feb 2025 01:20:59 +0100 Lionel Cons wrote: > Something is very wrong with bash. If I redirect the output of xcopy > or icacls into a bash variable, like stdout="$(icacls "$(cygpath -w > "$PWD")")", then sometimes I get only a letter in the middle. Very > strange Thanks for the report. B

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-18 Thread Lionel Cons via Cygwin
Something is very wrong with bash. If I redirect the output of xcopy or icacls into a bash variable, like stdout="$(icacls "$(cygpath -w "$PWD")")", then sometimes I get only a letter in the middle. Very strange Lionel On Tue, 18 Feb 2025 at 10:37, Corinna Vinschen via Cygwin wrote: > > > [I sen

[CALL FOR TESTING] Cygwin-3.6.0

2025-02-18 Thread Corinna Vinschen via Cygwin
[I sent this on 2024-02-14 to the cygwin-announce mailing list, but forgot to CC the cygwin mailing list. Doing it now...] Hi folks, we're planning the next major release in the next few (hopefully not more than two) weeks. We're looking forward to more people giving the latest test release

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-17 Thread Rainer Emrich via Cygwin
Hi Corinna, Am 17.02.2025 um 18:00 schrieb Corinna Vinschen via Cygwin: On Feb 17 12:51, Rainer Emrich via Cygwin wrote: Hi Corinna, Am 14.02.2025 um 20:03 schrieb Corinna Vinschen via Cygwin-announce: we're planning the next major release in the next few (hopefully not more than two) weeks.

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-17 Thread Jeremy Drake via Cygwin
On Mon, 17 Feb 2025, Corinna Vinschen via Cygwin wrote: > In fact, I can reproduce this occassionally back to 3.5.0 and back to > OpenSSH 9.7p1. We can't easily try this with older Cygwin versions. > It's getting increasingly hard to build older Cygwin versions due to > compiler dependencies and

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-17 Thread Corinna Vinschen via Cygwin
Hi Rainer, On Feb 17 12:51, Rainer Emrich via Cygwin wrote: > Hi Corinna, > > Am 14.02.2025 um 20:03 schrieb Corinna Vinschen via Cygwin-announce: > > we're planning the next major release in the next few (hopefully > > not more than two) weeks. > > [...] > > At this point, we're most interested

Re: [CALL FOR TESTING] Cygwin-3.6.0

2025-02-17 Thread Rainer Emrich via Cygwin
Hi Corinna, Am 14.02.2025 um 20:03 schrieb Corinna Vinschen via Cygwin-announce: we're planning the next major release in the next few (hopefully not more than two) weeks. We're looking forward to more people giving the latest test release of Cygwin a try! The most recent test release, which y