I checked the Debian firefox bugs page and noticed a new bug was reported against firefox. Checking the bug report showed the bug is new as it reported against version 3.0b5. As there’s now firefox package in debian testing/unstable that was weired enough.
Reading the bug report revealed these details:
Debian Release: lenny/sid
500 hardy-updates us.archive.ubuntu.com
500 hardy-security security.ubuntu.com
500 hardy us.archive.ubuntu.com
I mailed the user to see why does he reports Ubuntu’s bugs to Debian. He replied that he’s using the reportbug-ng program and wasn’t aware that his bug have been sent to Debian.
I check the reportbug and reportbug-ng in Ubuntu and found that reportbug has the needed patch for Ubuntu:
diff -pruN 3.39/reportbug.conf 3.39ubuntu3/reportbug.conf
--- 3.39/reportbug.conf 2004-12-06 13:59:04.000000000 +0000
+++ 3.39ubuntu3/reportbug.conf 2007-10-25 07:22:47.000000000 +0100
@@ -6,7 +6,7 @@
# severity normal
# BTS to use
# See ‘reportbug –bts help’ for a current list of supported BTSes
# Submission address: default is ‘submit’
but since hardy reportbug-ng package in Ubuntu is identical to the one in Debian.
$ rmadison -u ubuntu reportbug-ng
reportbug-ng | 0.2007.10.30~feisty1 | feisty-backports/universe | source, all
reportbug-ng | 0.2007.06.27 | gutsy/universe | source, amd64, i386, powerpc
reportbug-ng | 0.2007.10.30~gutsy1 | gutsy-backports/universe | source, all
reportbug-ng | 0.2007.10.30 | hardy/universe | source, all
reportbug-ng | 0.2008.03.28 | intrepid/universe | source, all
Doing more checks reveals that this is a known problem in Ubuntu and is already reported at Bug #175508. This was also discussed three weeks ago on “Ubuntu Open Week – Reporting Bugs“.
A quick look at the reportbug-ng code makes it clear that reportbug-ng will require more work to support the Ubuntu BTS. There were also some comments about the configuration for Ubuntu in reportbug, as it just send the reports to ubuntu-users mailing list and not to the real BTS at https://bugs.launchpad.net/ubuntu/.
I’m still not sure what to do about the bug. On one hand, that package originates in Debian, and the bug is probably relevant. On the other hand, the cause might be a change from Ubuntu. In any case, I
don’t see the user following our BTS, and I don’t way to fixed package (if and when created) to propagate to Ubuntu.