Hi, just wanted to ask: what is the status on this now sufficiently old issue?
I keep hitting this via apt-listbugs reports when trying to upgrade from coreutils 8.13-3 to 8.23-4. However, note that the original report said "[bug introduced in coreutils-8.11]" (upstream version value, I assume) So, while I am currently upgrading, it looks like the issue actually already *is* present on my system since I'm *post* 8.11, thus the apt-listbugs warning is somewhat moot/useless here since I'm already past potentially hitting a regression. Thus, perhaps original attributes which were given as: Package: coreutils Version: 8.13-3.5 Severity: grave ought to be request-corrected to properly indicate an *earlier* Debian package version that already was affected (that way my apt-listbugs activity probably would not list this issue during upgrade of the versions that are relevant on my system, since there actually is no status change during this transition). But perhaps the more modern version value was intentionally specified in order to *do* always warn about this issue, even on systems which already upgraded to an affected coreutils version... And then, of course, there remains the question of whether the currently provided (upgrade target) version (8.23-4) already is one where this issue indeed is fixed. However since original report said "It is present in the wheezy coreutils version and is fixed in jessie/sid. A backport of the fix or an update of coreutils would be welcomed for wheezy." yet https://packages.debian.org/search?keywords=coreutils reports version in jessie as 8.23-4 which is exactly my upgrade target and which is a version which is said to be fixed, I'd come to think that this bug report is missing specification of some sort of "fixed-in" attribute. Hmm, but there's no "fixed-in" tag (since I assume the way to mark this is to simply and properly close a bug), but perhaps using "wheezy" (https://www.debian.org/Bugs/Developer#tags) would be the way to go? As it stands, I'm predominantly irritated by the fact that apt-listbugs somehow decides to keep reporting an issue which *is* said to be fixed in this very upgrade target version (and, to make matters much worse, this warning report may actively and strongly deter people from promoting an unhealthy system to a healthy state i.e. an actually fixed version!!!) [personally, I have now decided to proceed with the upgrade since it seems correct and important] Thanks, Andreas Mohr
