Updated: coreutils 8.32

[Brian Inglis]

On 2022-05-22 09:24, Brian Inglis wrote:
> On 2022-05-21 23:54, Fergus Daly wrote:
>> I've just updated coreutils. I don't use test versions. So I have
>> $ uname --version
>> uname (GNU coreutils) 8.32
>> Packaged by Cygwin (8.32-1)
>> Now on 32-bit Cygwin I get
>> $ uname -s
>> CYGWIN_NT-10.0-19044-WOW64 [ previously CYGWIN_NT-10.0-WOW ]
>> And on 64-bit Cygwin I get
>> $ uname -s
>> CYGWIN_NT-10.0-19044 [ previously CYGWIN_NT-10.0 ]
>> Packaging error?
> 
> That build is a value we have said for years we would make visible for 
> easier determination of Windows version used (21H2 for you and I), 
> previously only visible in /proc/version:
> 
> $ head /proc/version
> CYGWIN_NT-10.0-19044 version 3.3.5-341.x86_64 (corinna@calimero) (gcc 
> version 11.2.0 20210728 (Fedora Cygwin 11.2.0-2) (GCC) ) 2022-05-13 
> 12:27 UTC
> 
> What products or processes does it affect negatively, and are there 
> arguments for suppression, other than backward compatibility?

This was enabled in an updated Cygwin uname(2) "syscall" in 2019 
January, but not visible to older utilities built against the older API, 
only exposed when coreutils was rebuilt, as intended:

* each string was lengthened from 20 to 65 bytes, and domainname added;
* for kernel, added the Windows build number, and restored the 64 after 
WOW, removed for Windows 10;

* for release, dropped the "s" snap indicator, and the API info in 
parentheses, added a dash and the API minor release, dot and 
architecture, and a ".snap" suffix for snapshots;

* added UTC after version/date;

for details see:

https://sourceware.org/git/?p=newlib-cygwin.git;a=commitdiff;h=84230b71c64765ad0e34faffdfe6d1c58477a84d

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]