Thanks for Your answer, Sandro: > >>>Well, I'm not that sure the current behavior of reportbug is wrong: >>>you're using an outdated version, from an archive point of view, so >>>the suggestion is trying to install it, if possible, and verify if >>>the problem you're facing is still replicable or not. >> >> Seems it is not the case: >> >> $ apt-cache policy cups >> cups: >> Installed: 1.5.0-8 >> Candidate: 1.5.0-8 >> Version table: >> 1.5.0-10 0 >> 700 http://mirror.yandex.ru/debian/ unstable/main amd64 >> Packages *** 1.5.0-8 0 >> 990 http://mirror.yandex.ru/debian/ wheezy/main amd64 Packages >> 100 /var/lib/dpkg/status >> 1.4.4-7 0 >> 900 http://mirror.yandex.ru/debian/ squeeze/main amd64 >> Packages >> >> ? >> > >one thing is what apt can install, the other what reportbug is saying: >there's a new release of the package you're about to report a bug, >maybe your bug is fixed there?
May be, but I use testing. And what You suggest is to use from Sid. Or You suggest to drop the bug reports for testing packages? In any way, I disagree w/ such policy - if in testing was a newer version - no question, but You suggest me to move to unstable at all! What will You recommend for the stable users?! Therefore, I suppose reportbug misleads users telling them about outdated packages when it is not so. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org