RE: Re: Updated: coreutils 8.32
>> 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 Thank you. > What products or processes does it affect negatively, and are there > arguments for suppression, other than backward compatibility? None central. I have a script with sequenced case `uname -s` in allowing for multiple platforms and it wobbled with this change. I will rewrite it. Thanks for clarity. Fergus -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Updated: coreutils 8.32
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.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Updated: coreutils 8.32
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? -- 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.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Updated: coreutils 8.32
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? Fergus -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: coreutils 8.32
The following package has been in test for two weeks with no reported or
obvious issues and has now been upgraded to current stable in the Cygwin
distribution:
* coreutils 8.32
GNU core utilities (includes fileutils, shellutils and textutils)
Common core utilities include: [ arch b2sum base32 base64
basename cat chcon chgrp chmod chown chroot cksum comm cp csplit cut date
dd df dir dircolors dirname du echo env expand expr factor false fmt fold
gkill groups head hostid id install join link ln logname ls md5sum mkdir
mkfifo mknod mktemp mv nice nl nohup nproc numfmt od paste pathchk pinky
pr printenv printf ptx pwd readlink realpath rm rmdir runcon seq sha1sum
sha224sum sha256sum sha384sum sha512sum shred shuf sleep sort split stat
stdbuf stty sum sync tac tail tee test timeout touch tr true truncate
tsort tty uname unexpand uniq unlink users vdir wc who whoami yes
For more information, see the project home pages:
https://www.gnu.org/software/coreutils
https://savannah.gnu.org/projects/coreutils
In case of doubts about changes, it may be useful to check the FAQ or
Gotchas:
https://www.gnu.org/software/coreutils/faq/coreutils-faq.html
https://www.pixelbeat.org/docs/coreutils-gotchas.html
For the many changes since the previous Cygwin release, see below or
read /usr/share/doc/coreutils/NEWS after installation; for complete
details see:
https://github.com/coreutils/coreutils/blob/v8.32/NEWS
https://git.sv.gnu.org/gitweb/?p=coreutils.git;a=log;h=refs/tags/v8.32
/usr/share/doc/coreutils/ChangeLog
Noteworthy changes in release 8.32 (2020-03-05)
Bug fixes
* cp now copies /dev/fd/N correctly on platforms like Solaris where
it is a character-special file whose minor device number is N.
[bug introduced in fileutils-4.1.6]
* dd conv=fdatasync no longer reports a "Bad file descriptor" error
when fdatasync is interrupted, and dd now retries interrupted calls
to close, fdatasync, fstat and fsync instead of incorrectly
reporting an "Interrupted system call" error.
[bugs introduced in coreutils-6.0]
* df now correctly parses the /proc/self/mountinfo file for unusual entries
like ones with '\r' in a field value ("mount -t tmpfs tmpfs /foo$'\r'bar"),
when the source field is empty ('mount -t tmpfs "" /mnt'), and when the
filesystem type contains characters like a blank which need escaping.
[bugs introduced in coreutils-8.24 with the introduction of reading
the /proc/self/mountinfo file]
* factor again outputs immediately when stdout is a tty but stdin is not.
[bug introduced in coreutils-8.24]
* ln works again on old systems without O_DIRECTORY support (like Solaris 10),
and on systems where symlink ("x", ".") fails with errno == EINVAL
(like Solaris 10 and Solaris 11).
[bug introduced in coreutils-8.31]
* rmdir --ignore-fail-on-non-empty now works correctly for directories
that fail to be removed due to permission issues. Previously the exit status
was reversed, failing for non empty and succeeding for empty directories.
[bug introduced in coreutils-6.11]
* 'shuf -r -n 0 file' no longer mistakenly reads from standard input.
[bug introduced with the --repeat feature in coreutils-8.22]
* split no longer reports a "output file suffixes exhausted" error
when the specified number of files is evenly divisible by 10, 16, 26,
for --numeric, --hex, or default alphabetic suffixes respectively.
[bug introduced in coreutils-8.24]
* seq no longer prints an extra line under certain circumstances (such as
'seq -f "%g " 100 100').
[bug introduced in coreutils-6.10]
Changes in behavior
* Several programs now check that numbers end properly. For example,
'du -d 1x' now reports an error instead of silently ignoring the 'x'.
Affected programs and options include du -d, expr's numeric operands
on non-GMP builds, install -g and -o, ls's TABSIZE environment
variable, mknod b and c, ptx -g and -w, shuf -n, and sort --batch-size
and --parallel.
* date now parses military time zones in accordance with common usage:
"A" to "M" are equivalent to UTC+1 to UTC+12
"N" to "Y" are equivalent to UTC-1 to UTC-12
"Z" is "zulu" time (UTC).
For example, 'date -d "09:00B" is now equivalent to 9am in UTC+2 time zone.
Previously, military time zones were parsed according to the obsolete
rfc822, with their value negated (e.g., "B" was equivalent to UTC-2).
[The old behavior was introduced in sh-utils 2.0.15 ca. 1999, predating
coreutils package.]
* ls issues an error message on a removed directory, on GNU/Linux systems.
Previously no error and no entries were output, and so indistinguishable
from an empty directory, with default ls options.
* uniq no longer uses strcoll() to determine string equivalence,
and so will operate more efficiently and consistently.
New Features
* ls now supports the --time=birth option to display and sort by
file creation time, where available.
* od
Updated: coreutils 8.32
The following package has been in test for two weeks with no reported or
obvious issues and has now been upgraded to current stable in the Cygwin
distribution:
* coreutils 8.32
GNU core utilities (includes fileutils, shellutils and textutils)
Common core utilities include: [ arch b2sum base32 base64
basename cat chcon chgrp chmod chown chroot cksum comm cp csplit cut date
dd df dir dircolors dirname du echo env expand expr factor false fmt fold
gkill groups head hostid id install join link ln logname ls md5sum mkdir
mkfifo mknod mktemp mv nice nl nohup nproc numfmt od paste pathchk pinky
pr printenv printf ptx pwd readlink realpath rm rmdir runcon seq sha1sum
sha224sum sha256sum sha384sum sha512sum shred shuf sleep sort split stat
stdbuf stty sum sync tac tail tee test timeout touch tr true truncate
tsort tty uname unexpand uniq unlink users vdir wc who whoami yes
For more information, see the project home pages:
https://www.gnu.org/software/coreutils
https://savannah.gnu.org/projects/coreutils
In case of doubts about changes, it may be useful to check the FAQ or
Gotchas:
https://www.gnu.org/software/coreutils/faq/coreutils-faq.html
https://www.pixelbeat.org/docs/coreutils-gotchas.html
For the many changes since the previous Cygwin release, see below or
read /usr/share/doc/coreutils/NEWS after installation; for complete
details see:
https://github.com/coreutils/coreutils/blob/v8.32/NEWS
https://git.sv.gnu.org/gitweb/?p=coreutils.git;a=log;h=refs/tags/v8.32
/usr/share/doc/coreutils/ChangeLog
Noteworthy changes in release 8.32 (2020-03-05)
Bug fixes
* cp now copies /dev/fd/N correctly on platforms like Solaris where
it is a character-special file whose minor device number is N.
[bug introduced in fileutils-4.1.6]
* dd conv=fdatasync no longer reports a "Bad file descriptor" error
when fdatasync is interrupted, and dd now retries interrupted calls
to close, fdatasync, fstat and fsync instead of incorrectly
reporting an "Interrupted system call" error.
[bugs introduced in coreutils-6.0]
* df now correctly parses the /proc/self/mountinfo file for unusual entries
like ones with '\r' in a field value ("mount -t tmpfs tmpfs /foo$'\r'bar"),
when the source field is empty ('mount -t tmpfs "" /mnt'), and when the
filesystem type contains characters like a blank which need escaping.
[bugs introduced in coreutils-8.24 with the introduction of reading
the /proc/self/mountinfo file]
* factor again outputs immediately when stdout is a tty but stdin is not.
[bug introduced in coreutils-8.24]
* ln works again on old systems without O_DIRECTORY support (like Solaris 10),
and on systems where symlink ("x", ".") fails with errno == EINVAL
(like Solaris 10 and Solaris 11).
[bug introduced in coreutils-8.31]
* rmdir --ignore-fail-on-non-empty now works correctly for directories
that fail to be removed due to permission issues. Previously the exit status
was reversed, failing for non empty and succeeding for empty directories.
[bug introduced in coreutils-6.11]
* 'shuf -r -n 0 file' no longer mistakenly reads from standard input.
[bug introduced with the --repeat feature in coreutils-8.22]
* split no longer reports a "output file suffixes exhausted" error
when the specified number of files is evenly divisible by 10, 16, 26,
for --numeric, --hex, or default alphabetic suffixes respectively.
[bug introduced in coreutils-8.24]
* seq no longer prints an extra line under certain circumstances (such as
'seq -f "%g " 100 100').
[bug introduced in coreutils-6.10]
Changes in behavior
* Several programs now check that numbers end properly. For example,
'du -d 1x' now reports an error instead of silently ignoring the 'x'.
Affected programs and options include du -d, expr's numeric operands
on non-GMP builds, install -g and -o, ls's TABSIZE environment
variable, mknod b and c, ptx -g and -w, shuf -n, and sort --batch-size
and --parallel.
* date now parses military time zones in accordance with common usage:
"A" to "M" are equivalent to UTC+1 to UTC+12
"N" to "Y" are equivalent to UTC-1 to UTC-12
"Z" is "zulu" time (UTC).
For example, 'date -d "09:00B" is now equivalent to 9am in UTC+2 time zone.
Previously, military time zones were parsed according to the obsolete
rfc822, with their value negated (e.g., "B" was equivalent to UTC-2).
[The old behavior was introduced in sh-utils 2.0.15 ca. 1999, predating
coreutils package.]
* ls issues an error message on a removed directory, on GNU/Linux systems.
Previously no error and no entries were output, and so indistinguishable
from an empty directory, with default ls options.
* uniq no longer uses strcoll() to determine string equivalence,
and so will operate more efficiently and consistently.
New Features
* ls now supports the --time=birth option to display and sort by
file creation time, where available.
* od
