Change History (4)
comment:1 by , 19 months ago
comment:2 by , 19 months ago
GNU coreutils NEWS -*- outline -*-
- 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.
comment:3 by , 19 months ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed at commit a6c73fe5b2fb0617d44c1d1119444b1918157e17
The i18n patch still applies fine. The sed is not needed now.