Hi Reuben, On Mon, Jun 8, 2009 at 13:37, Reuben Thomas<[email protected]> wrote: > 2009/6/8 Sandro Tosi <[email protected]>: >> please next time report the complete transcript of what reportbug >> outputs, for example: > > Thanks. Could this be in the instructions (i.e. in the file shown just > before you enter the bug report which currently starts "Common > problems with reportbug")?
It makes sense: I've just added a notice about it. >> The same happens (as seen above) on a sid machine. This is because >> libc6 is now provided by eglibc, while before it was provided by glibc >> package (As seen in the line "Querying Debian BTS for reports on glibc >> (source)"). > > This is all very well, but it's particularly confusing to a lenny > user, where there is no eglibc package. We are qureying live data (the BTS) that evolves faster than stable releases. Sadly, there's nothing we can do about it. >> This is not a bug in reportbug, but it's due to the evolving nature of >> packages & bugs. > > Nonetheless, is there some way of fixing it, e.g. having reportbug try > by falling back to the binary package if it finds no bugs? At first sight I don't consider this a valid solution, but I'll think about it. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
