On Tuesday, April 18, 2023 5:16:29 PM CEST Pádraig Brady wrote: > This is to announce coreutils-9.3, a stable release. > This is a bug fix release coming about 4 weeks after the 9.2 release. > See the NEWS below for a summary of changes.
Thanks! I had to revert the following gnulib commit to be able to build it in the Fedora Rawhide buildroot: https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=4e38f4a0c65d4d19883b404a84169088b84b60d2 ... where it was failing with: FAIL: test-strtoll ================== ../../gnulib-tests/test-strtoll.c:290: assertion 'ptr == input + 1' failed FAIL test-strtoll (exit status: 134) FAIL: test-strtoull =================== ../../gnulib-tests/test-strtoull.c:289: assertion 'ptr == input + 1' failed FAIL test-strtoull (exit status: 134) https://kojipkgs.fedoraproject.org//work/tasks/3697/100103697/build.log Kamil > There have been 26 commits by 3 people in the 29 days since 9.2. > Thanks to everyone who has contributed! > The following people contributed changes to this release: > > Nick Alcock (1) > Paul Eggert (5) > Pádraig Brady (20) > > Pádraig [on behalf of the coreutils maintainers] > > ================================================================== > > Here is the GNU coreutils home page: > http://gnu.org/s/coreutils/ > > For a summary of changes and contributors, see: > http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=shortlog;h=v9.3 > or run this command from a git-cloned coreutils directory: > git shortlog v9.2..v9.3 > > Here are the compressed sources: > https://ftp.gnu.org/gnu/coreutils/coreutils-9.3.tar.gz (14MB) > https://ftp.gnu.org/gnu/coreutils/coreutils-9.3.tar.xz (5.6MB) > > Here are the GPG detached signatures: > https://ftp.gnu.org/gnu/coreutils/coreutils-9.3.tar.gz.sig > https://ftp.gnu.org/gnu/coreutils/coreutils-9.3.tar.xz.sig > > Use a mirror for higher download bandwidth: > https://www.gnu.org/order/ftp.html > > Here are the SHA1 and SHA256 checksums: > > b657a5fe51eed93cdafd9fe69594305ff040dd00 coreutils-9.3.tar.gz > oz0sC8Sb48eaR5SUTc2HEDv0l7U6FLr81DHIylOXUlI= coreutils-9.3.tar.gz > cd1fd7e27d46fd2497b8f2a670b54785530ef7d2 coreutils-9.3.tar.xz > rbz8/omSNbceh2jc8HzVMlILf1T5qAZIQ/jRmakEu6o= coreutils-9.3.tar.xz > > Verify the base64 SHA256 checksum with cksum -a sha256 --check > from coreutils-9.2 or OpenBSD's cksum since 2007. > > Use a .sig file to verify that the corresponding file (without the > .sig suffix) is intact. First, be sure to download both the .sig file > and the corresponding tarball. Then, run a command like this: > > gpg --verify coreutils-9.3.tar.gz.sig > > The signature should match the fingerprint of the following key: > > pub rsa4096/0xDF6FD971306037D9 2011-09-23 [SC] > Key fingerprint = 6C37 DC12 121A 5006 BC1D B804 DF6F D971 3060 37D9 > uid [ unknown] Pádraig Brady <p...@draigbrady.com> > uid [ unknown] Pádraig Brady <pixelb...@gnu.org> > > If that command fails because you don't have the required public key, > or that public key has expired, try the following commands to retrieve > or refresh it, and then rerun the 'gpg --verify' command. > > gpg --locate-external-key p...@draigbrady.com > > gpg --recv-keys DF6FD971306037D9 > > wget -q -O- > 'https://savannah.gnu.org/project/release-gpgkeys.php?group=coreutils&download=1' > | gpg --import - > > As a last resort to find the key, you can try the official GNU > keyring: > > wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg > gpg --keyring gnu-keyring.gpg --verify coreutils-9.3.tar.gz.sig > > This release was bootstrapped with the following tools: > Autoconf 2.72c.17-0cc3 > Automake 1.16.5 > Gnulib v0.1-6046-g4b60490554 > Bison 3.8.2 > > NEWS > > * Noteworthy changes in release 9.3 (2023-04-18) [stable] > > ** Bug fixes > > cp --reflink=auto (the default), mv, and install > will again fall back to a standard copy in more cases. > Previously copies could fail with permission errors on > more restricted systems like android or containers etc. > [bug introduced in coreutils-9.2] > > cp --recursive --backup will again operate correctly. > Previousy it may have issued "File exists" errors when > it failed to appropriately rename files being replaced. > [bug introduced in coreutils-9.2] > > date --file and dircolors will now diagnose a failure to read a file. > Previously they would have silently ignored the failure. > [This bug was present in "the beginning".] > > md5sum --check again correctly prints the status of each file checked. > Previously the status for files was printed as 'OK' once any file had > passed. > This also applies to cksum, sha*sum, and b2sum. > [bug introduced in coreutils-9.2] > > wc will now diagnose if any total counts have overflowed. > [This bug was present in "the beginning".] > > `wc -c` will again correctly update the read offset of inputs. > Previously it deduced the size of inputs while leaving the offset > unchanged. > [bug introduced in coreutils-8.27] > > Coreutils programs no longer fail for timestamps past the year 2038 > on obsolete configurations with 32-bit signed time_t, because the > build procedure now rejects these configurations. > [This bug was present in "the beginning".] > > ** Changes in behavior > > 'cp -n' and 'mv -n' now issue an error diagnostic if skipping a file, > to correspond with -n inducing a nonzero exit status as of coreutils 9.2. > Similarly 'cp -v' and 'mv -v' will output a message for each file skipped > due to -n, -i, or -u. > > ** New features > > cp and mv now support --update=none to always skip existing files > in the destination, while not affecting the exit status. > This is equivalent to the --no-clobber behavior from before v9.2. > > - > Also posted at https://savannah.gnu.org/news/?id=10350 > >
