On Mon, Oct 31, 2011 at 17:19, Sthu Deus <sthu.d...@yandex.ru> wrote: > Thanks for Your answer, Sandro: > >>first of all, please always the bug in the loop, so others can see >>what's happening. > > Now, is it OK?
yep >>>>Could you please try with 6.2.2 with a similar case? >>>> >>> >>> Same thing: >>> >>> Getting status for cups... >>> Checking for newer versions at packages.debian.org... >>> >>> Your version (1.5.0-8) of cups appears to be out of date. >>> The following newer release(s) are available in the Debian archive: >>> unstable: 1.5.0-10 >>> Do you still want to file a report [y|N|q|?]? >>> Newer released version; stopping. >>> >>> $ dpkg -l |grep reportb >>> ii reportbug 6.2.2 >> >>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? -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
