uutils/coreutils

GNU ls --dired ends its output with //DIRED-OPTIONS// --quoting-style=<name>, where <name> is the canonical name of the quoting style in effect. uutils prints the Display form of the internal QuotingStyle enum instead (impl fmt::Display for QuotingStyle in src/uucore/src/lib/features/quoting_style/mod.rs, used at src/uu/ls/src/dired.rs:128), so most style names come out wrong. ls -l --dired <opt> a | tail -1 through a pipe, uutils main vs GNU coreutils 9.12: option uutils prints GNU prints --quoting-style=literal, -N literal literal --quoting-style=shell shell-show-control shell --quoting-style=shell-always shell-always-quote-show-control shell-always --quoting-style=shell-escape shell-escape-show-control shell-escape --quoting-style=shell-escape-always shell-escape-always-quote-show-control shell-escape-always --quoting-style=c, -Q C c --quoting-style=escape, -b C escape --quoting-style=locale literal locale --quoting-style=clocale C clocale QUOTING_STYLE=she

ls --zero should terminate every line with NUL instead of newline. This works for -1 and -m, but when --zero is given before a column format option (-C or -x), the last line is still terminated by \n. Reproduce (in a directory containing a and b), uutils main vs GNU coreutils 9.12: $ coreutils ls --zero -C a b | od -An -c a b \n $ ls --zero -C a b | od -An -c a b \0 $ coreutils ls --zero -x a b | od -An -c a b \n $ ls --zero -x a b | od -An -c a b \0 ls --zero -1, ls --zero -m, and ls -C --zero (where --zero comes last and resets the format to -1) already match GNU. The GNU test tests/ls/zero-option.sh only covers the -C --zero ordering. The following addition passes on GNU 9.12 and fails on uutils main: # --zero must also terminate column output with NUL when it precedes -C or -x mkdir dir2 && touch dir2/a dir2/b || framework_failure_ printf 'a b\0' > exp || framework_failure_ for opt in -C -x; do LC_ALL=C ls --zero $opt -w

printf panics instead of printing when a numeric conversion is given a field width above 65535: $ printf '%65536d' 5 thread 'main' panicked at src/uucore/src/lib/features/format/num_format.rs:781:17: Formatting argument out of range note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace $ echo $? 101 GNU prints the padded field and exits 0: $ /usr/bin/printf '%65536d' 5 | wc -c 65536 The boundary is exactly u16::MAX: %65535d works, %65536d panics. It affects numeric conversions (%d, %f, ...) but not %s, so %65536s is fine. The cause is that the width is passed straight to Rust's formatting machinery, which only accepts a width that fits in a u16. The fix is to stop relying on format! for the padding once the width exceeds that, and emit the padding directly. Where src/uucore/src/lib/features/format/num_format.rs, in the NumberAlignment handling — the write!(writer, "{s:>width$}", ...) / write!(writer, "{sign_indicator}{s:>remaining_width$}") calls (around line

Summary GNU date honours strftime flags and widths on %N (nanoseconds). uutils ignores or mishandles them: %_3N should space-pad to width 3, and %-N should still emit the full 9-digit default, but uutils emits a single 0. Found by a fuzz_date run. Reproduction $ LC_ALL=C TZ=UTC /usr/bin/date -d '@0' '+%_3N' | od -c | head -1 0000000 0 \n $ LC_ALL=C TZ=UTC target/debug/coreutils date -d '@0' '+%_3N' | od -c | head -1 0000000 0 \n $ LC_ALL=C TZ=UTC /usr/bin/date -d '@0' '+%-N' 000000000 $ LC_ALL=C TZ=UTC target/debug/coreutils date -d '@0' '+%-N' 0 Test #[test] fn test_date_strftime_n_width_and_flags() { new_ucmd!() .env("LC_ALL", "C") .env("TZ", "UTC") .arg("-d") .arg("@0") .arg("+%_3N") .succeeds() .stdout_is("0 \n"); new_ucmd!() .env("LC_ALL", "C") .env("TZ", "UTC") .arg("-d") .arg("@0") .arg("+%-N") .succeeds() .stdout_is("000000000\n"); }

Summary GNU date treats composite strftime specifiers (%D, %F, %T, %r, %R, %c, %x, %X) as atomic: flags like - apply to the whole expansion, not to inner sub-fields. uutils lets the - flag propagate into the inner %m, producing 6/15/24 instead of 06/15/24. Found by a fuzz_date run. Reproduction $ LC_ALL=C TZ=UTC /usr/bin/date -d '2024-06-15' '+%-D' 06/15/24 $ LC_ALL=C TZ=UTC target/debug/coreutils date -d '2024-06-15' '+%-D' 6/15/24 Test #[test] fn test_date_strftime_flag_on_composite() { new_ucmd!() .env("LC_ALL", "C") .env("TZ", "UTC") .arg("-d") .arg("2024-06-15") .arg("+%-D") .succeeds() .stdout_is("06/15/24\n"); }