Hi, While checking this again (as I've also been awaiting a fix), I noticed that in addition to having version 2.2.3-2 packaged in bookworm-backports, a patch set containing the fix was also pushed to the bookworm branch on top of the released 2.1.11 version: ff4499f12efeb0d48899c686b26450bb060abbf0
However, that commit-- which states that it closes #1056752, which was actually archived without a resolution in Debian stable-- has not been released yet, either. This seems like a policy issue rather than an issue of doing the work, since packages for newer upstream versions and a patched downstream version exist on Debian Salsa. Is there a reason why none of these can be moved forward? This bug was seen as fairly low-priority on most real-world systems partially because it didn't affect most 8.x (and older) versions of coreutils, but Debian stable does contain coreutils 9.1. - Jacob Kauffmann
