2016-03-01 18:53 GMT+01:00 Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>: > Perhaps. But in any case, even if the underlying problem was actually a > different one, if several people cannot reproduce it in 0.7.x and there > are reasonably indications that it was fixed, it means that it's > probably fixed.
Agreed. > And more in general, if we cannot reproduce it there's not much that we > can do about it. Also agreed, but people can (in the jessie version). > Sorry, but we don't have the resources to backport versions to Jessie, That's perfectly understandable. What bugs me is closing a bug that is neither fixed (in stable) nor (going to get) documented anywhere. It's just going to get archived and then it won't even show up in reportbug anymore. This is not the first bug I've come across in the last few weeks that turned out to be a possible dupe of a months-old archived report, with or without any indication that it still affected the current stable ... In my ideal world this bug would be marked "wontfix" for all versions of aptitude known to be affected (but otherwise kept from being archived as long as an affected version is supported) and "fixed in" for the earliest version known not to be. I'd thought the BTS could do this, but perhaps not. What do I know, I'm just a user. Also a /usr/share/doc/*/ERRATA.Debian containing short summaries of all known issues that won't be fixed in the current branch would be nice. The bug numbers and subjects would do, as long as the latter are descriptive. Cheers, C.
