Re: possible snprintf() regression in 3.3.2

On Wed, 17 Nov 2021 11:37:18 +1100 Tony Cook wrote: > This came up from regression testing perl. > > Regression testing of perl @4a1b9dd524007193213d3919d6a331109608b90c > used (from uname): > > cygwin_nt-10.0 fv-az177-186 3.3.1(0.34153) 2021-10-28 20:52 x86_64 cygwin > > this did not exhibit t

Re: possible snprintf() regression in 3.3.2

On Nov 17 18:21, Takashi Yano via Cygwin wrote: > On Wed, 17 Nov 2021 11:37:18 +1100 > Tony Cook wrote: > > This came up from regression testing perl. > > > > Regression testing of perl @4a1b9dd524007193213d3919d6a331109608b90c > > used (from uname): > > [...] > I found the caused by the commit: >

Re: libfido2’s dependency on libcbor is dropped in setup.ini

On Nov 17 11:57, ggl329 via Cygwin wrote: > cygfido2-1.dll (from libfido2-1.9.0-1) depends on cygcbor-0.8.dll . > But the dependency is dropped in setup.ini (depends2 field). > In addition, the current libcbor-0.9.0-2 doesn’t provide cygcbor-0.8.dll but > cygcbor-0.9.dll . > Maybe, libfido2 needs

[ANNOUNCEMENT] libfido2 1.9.0-2

The following packages have been uploaded to the Cygwin distribution: * libfido2-1.9.0-2 * libfido2-devel-1.9.0-2 This is a rebuild, statically linked against libcbor, to avoid problems with missing binary compatibility between libcbor 0.X versions. libfido2 provides library functionality and c

[ANNOUNCEMENT] libcbor 0.9.0-3

The following packages have been uploaded to the Cygwin distribution: * libcbor-0.9.0-3 * libcbor-devel-0.9.0-3 Rebuild, removing the DLLs and just providing a library for static linking. libcbor is a C library for parsing and generating CBOR. -- Problem reports: https://cygwin.com/proble

Misbehaviour of cygpath -am between versions 3.1.4 and 3.3.2

Dear folks! The command 'cygpath -am .' yields different results between cygwin-3.1.4-1 and cygwin-3.3.2-1 on a Windows 10 box when the current directory is a network share. Example with V3.1.4: cygpath -am .  ---> P:/mytool/gbuild/wintel/libtiff Example with V3.3.2-1 cygpath -am .  ---> /

Re: Cygwin 3.3.0 regression: "make" segmentation faults

On 11/16/21 9:11 AM, Takashi Yano wrote: Thanks for the report. I could reproduce the problem and found that the cause is the same with: https://cygwin.com/pipermail/cygwin/2021-November/249913.html I will submit the patch for these issues shortly. Nice. Let me know when there is a testable bi

Re: Misbehaviour of cygpath -am between versions 3.1.4 and 3.3.2

Greetings, Wolfgang S. Kechel! > The command 'cygpath -am .' yields different results between > cygwin-3.1.4-1 and cygwin-3.3.2-1 on a Windows 10 box when the current > directory is a network share. > Example with V3.1.4: > cygpath -am .  ---> P:/mytool/gbuild/wintel/libtiff > Example with V3.

[ANNOUNCEMENT] Updated: Perl distributions

The following Perl distributions have been updated to their latest release version available on CPAN: noarch -- perl-Date-Manip-6.86-1 perl-HTTP-Message-6.35-1 perl-HTTP-Tiny-0.080-1 perl-Image-ExifTool-12.30-1 perl-Test2-Suite-0.000142-1 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE I

Re: Misbehaviour of cygpath -am between versions 3.1.4 and 3.3.2

On Nov 17 19:44, Andrey Repin via Cygwin wrote: > Greetings, Wolfgang S. Kechel! > > > The command 'cygpath -am .' yields different results between > > cygwin-3.1.4-1 and cygwin-3.3.2-1 on a Windows 10 box when the current > > directory is a network share. > > > Example with V3.1.4: > > > cygpa

Re: possible snprintf() regression in 3.3.2

On Wed, Nov 17, 2021 at 01:27:55PM +0100, Corinna Vinschen via Cygwin wrote: > On Nov 17 18:21, Takashi Yano via Cygwin wrote: > > On Wed, 17 Nov 2021 11:37:18 +1100 > > Tony Cook wrote: > > > This came up from regression testing perl. > > > > > > Regression testing of perl @4a1b9dd524007193213d39

terminfo packaging glitch?

Does this: $ ls /usr/share/terminfo/terminfo lrwxrwxrwx /usr/share/terminfo/terminfo -> /usr/share/terminfo/ serve a purpose, or supply a workaround .. or .. is it a packaging glitch? (Only in Cygwin64, not Cygwin32.) -- Problem reports: https://cygwin.com/problems.html FAQ: