Bug#577986: Bug#578296: closed by Sandro Tosi (Re: Bug#577986: reportbug: Crash after current bugs list)

2010-04-21 Thread Sandro Tosi
Hello Klaus, On Wed, Apr 21, 2010 at 17:34, Klaus Ethgen wrote: > I hope I do reply to the right bug now. There is a big mess with this > bug. I agree > The problem did occur after the update today. However I cannot exclude > that the bug was happen earlier as I did not try to report a bug the

Bug#577986: Bug#578296: closed by Sandro Tosi (Re: Bug#577986: reportbug: Crash after current bugs list)

2010-04-21 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, I hope I do reply to the right bug now. There is a big mess with this bug. The problem did occur after the update today. However I cannot exclude that the bug was happen earlier as I did not try to report a bug the last days. Am Mo den 19. Apr

Bug#578296: closed by Sandro Tosi (Re: Bug#577986: reportbug: Crash after current bugs list)

2010-04-21 Thread Sandro Tosi
On Wed, Apr 21, 2010 at 05:50, Joey Hess wrote: > Sandro Tosi wrote: >> This problem only occurs to testing users, so hardly a wide-spread bug >> (else it would have spotted also in sid and in many other packages). > > Thus, we mqay potentially release a stable Debian in which reportbug > doesn't

Bug#578296: closed by Sandro Tosi (Re: Bug#577986: reportbug: Crash after current bugs list)

2010-04-20 Thread Joey Hess
Sandro Tosi wrote: > This problem only occurs to testing users, so hardly a wide-spread bug > (else it would have spotted also in sid and in many other packages). Thus, we mqay potentially release a stable Debian in which reportbug doesn't work? -- see shy jo signature.asc Description: Digital

Bug#578296: closed by Sandro Tosi (Re: Bug#577986: reportbug: Crash after current bugs list)

2010-04-19 Thread Sandro Tosi
Hi Joey, On Mon, Apr 19, 2010 at 21:38, Joey Hess wrote: > A few facts: thanks for the lecture ;) > 1. Closing a bug "because it is a bug in another package" is always a >   misuse  of the Debian BTS, which allows reassigning bugs to the package >   that is really at fault. it's not a bug in "

Bug#577986: reportbug: Crash after current bugs list

2010-04-19 Thread Elias Gabriel Amaral da Silva
2010/4/19 Sandro Tosi : > On Sun, Apr 18, 2010 at 08:45, Elias Gabriel Amaral da Silva > wrote: >> I was reporting a bug using the gtk interface, and it crashed. > > and so you commented the first reportbug bug to notify this?! I didn't > check earlier, and so I close a VALID bug (now already reop

Bug#578296: closed by Sandro Tosi (Re: Bug#577986: reportbug: Crash after current bugs list)

2010-04-19 Thread Joey Hess
A few facts: 1. Closing a bug "because it is a bug in another package" is always a misuse of the Debian BTS, which allows reassigning bugs to the package that is really at fault. It pisses users off, and prevents them from filing bug reports in the future. Getting users to file bug repor

Bug#577986: reportbug: Crash after current bugs list

2010-04-19 Thread Sandro Tosi
Elias, WTF?! On Sun, Apr 18, 2010 at 08:45, Elias Gabriel Amaral da Silva wrote: > Package: reportbug > Version: 4.11 > Severity: normal > > I was reporting a bug using the gtk interface, and it crashed. and so you commented the first reportbug bug to notify this?! I didn't check earlier, and so

Bug#577986: reportbug: Crash after current bugs list

2010-04-17 Thread Elias Gabriel Amaral da Silva
Package: reportbug Version: 4.11 Severity: normal I was reporting a bug using the gtk interface, and it crashed. I was at the "view a tree of already reported bugs" part, and my bug was already reported (Against ruby package). I never used this interface, so I was trying to figure out how to se