[Reportbug-maint] Bug#666469: Bug#666469: reportbug: reports bug assigned to the wrong package (multi-arch problem?)

Sandro Tosi morph at debian.org
Sat Mar 31 08:24:54 UTC 2012

severity 666469 important

On Sat, Mar 31, 2012 at 02:49, Vincent Lefevre <vincent at vinc17.net> wrote:
> Package: reportbug
> Version: 6.3.1
> Severity: grave
> Justification: renders package unusable
> (well, not completely, but this is definitely a RC bug if you don't
> want a mess in the bug reports)

I'm not convinced this is RC (on reportbug) because it's not effecting
all the users: downgraded.

> I wanted to report a bug against libcairo2, but I got:
> $ reportbug libcairo2
> [...]
> Getting status for libcairo2...
> Verifying package integrity...
> There may be a problem with your installation of libcairo2;
> the following problems were detected by debsums:
> debsums: package libcairo2 is not installed

this is debsums replying, so at least you should have filed the bug
against that: reportbug here is just a interface to it.

> Do you still want to file a report [y|N|q|?]?
> So, I suspected that I should have used the complete package name:
> $ reportbug libcairo2:amd64
> [...]
> then everything seemed to be OK, as usual. The bug report was sent:
>  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666468
> However the bug was assigned to libcairo2:amd64, which doesn't
> exist for the Debian BTS (unknown maintainer, unknown source).

was it defined somewhere how bugs for m-a packages should be filed?

Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

More information about the Reportbug-maint mailing list