coreutils/NEWS, branch v9.8Mirror of https://https.git.savannah.gnu.org/git/coreutils.git/
https://git.shady.money/coreutils/atom?h=v9.82025-09-22T16:50:52Zversion 9.82025-09-22T16:50:52ZPádraig BradyP@draigBrady.com2025-09-22T16:50:52Zurn:sha1:76e161dc2d70f2d3e0b908e756d62be91bb72c41
* NEWS: Record release date.
dd: don't mistakenly use O_EXCL on GNU/Hurd2025-09-19T06:31:18ZCollin Funkcollin.funk1@gmail.com2025-09-19T06:29:02Zurn:sha1:2662ddf335c9c5bafefa9c8c0b25c26e73d192ab
* src/dd.c (v): Add the O_EXCL flag to the set of bits that we do not
want to use for our definitions.
* cfg.mk (sc_dd_O_FLAGS): Adjust to pass syntax-check.
* NEWS: Mention the fix.
Reported by Bruno Haible.
doc: add hardware acceleration configuration docs2025-09-16T23:22:50ZPádraig BradyP@draigBrady.com2025-09-16T21:51:20Zurn:sha1:168ae824f78d2e02b5d21680306bca8771bf7b2c
* NEWS: Mention the new GLIBC_TUNABLES feature.
* doc/coreutils.texi (Hardware Acceleration): A new node
detailing the build time and run time configuration options.
fold: fix write error checks with invalid multi-byte input2025-09-16T17:41:51ZPádraig BradyP@draigBrady.com2025-09-16T15:45:02Zurn:sha1:c95c7ee76ff4480125a15b8e53945b60e58de400
* src/fold.c (write_out): A new helper to check all writes.
(fold-file): Use write_out() for all writes.
* tests/fold/fold-zero-width.sh: Adjust to writing more
data in various patterns, rather than two buffers of NULs.
This is a more robust memory bound check, and the '\303' case
tests this particular logic change.
* NEWS: fold now exits immediately, not just promptly.
fold: exit promptly upon write errors2025-09-16T13:10:31ZPádraig BradyP@draigBrady.com2025-09-16T12:07:35Zurn:sha1:10459ca7ed15456a6dbfebc7d718c8d713fbfe70
* NEWS: Mention the improvement.
* src/fold.c (fold_file): Check for write errors
after each buffer read from stdin.
* tests/misc/write-errors.sh: Add test cases.
doc: NEWS: fold: clarify mem exhaustion trigger2025-09-16T12:56:35ZPádraig BradyP@draigBrady.com2025-09-16T12:56:35Zurn:sha1:7de9140e7a61e87e94bb67ffa1a796e2b2f5695e
* NEWS: Long lines were not an issue in previously
released coreutils, only the -w limitation was.
doc: NEWS: correct the previous commit2025-09-16T04:40:56ZCollin Funkcollin.funk1@gmail.com2025-09-16T04:40:56Zurn:sha1:e33bfb5886f3e4c0e45b833289a210d673947e49
* NEWS: The memory allocated by 'fold' in the past was also bounded by
--width.
doc: NEWS: mention fold can operate on very long lines2025-09-16T04:09:42ZCollin Funkcollin.funk1@gmail.com2025-09-16T04:09:42Zurn:sha1:58b5fd0bc8f0c398c1dbb4f90d2940dab30c9115
* NEWS: Before commit fb9016d50 (fold: use fread instead of getline,
2025-08-24), fold required that the maximum line size in a file fit into
memory. Document that this is no longer the case.
nohup: avoid FORTIFY runtime failure on Bionic libc2025-09-09T11:21:41ZPádraig BradyP@draigBrady.com2025-09-09T11:11:00Zurn:sha1:2ed207cb1fe7ae51ffc1c987ef1c7848f2b56358
The meaning of non-file permission umask bits is implementation defined.
On Bionic libc, attempting to set them triggers a FORTIFY runtime check.
$ nohup true
FORTIFY: umask: called with invalid mask -601
Aborted nohup true
* src/nohup.c: (main) Avoid setting non-permission bits in umask.
Just clear the umask to ensure we create nohup.out with u+rw,
as we restore the original umask before the exec().
* tests/misc/nohup.sh: Add a test case.
* NEWS: Mention the bug fix.
basenc: ensure partial padding with newlines induces an error2025-09-08T18:39:47ZPádraig BradyP@draigBrady.com2025-09-08T17:22:20Zurn:sha1:d9b68362edcb509ecb00cf900617f55574212a96
* src/basenc.c (has_padding): A more robust helper to
identify padding in the presence of trailing newlines.
(do_decode): Use has_padding() rather than just looking
at the last character.
* tests/basenc/base64.pl: Fully test commit v9.4-53-g378dc38f4
by ensuring partially padded data is diagnosed.
baddecode9 is the case fixed in this commit.
* NEWS: Mention the bug fix.