Introduction to Debian’s Bug Tracking System (BTS)
I assume you all know that Ubuntu is based on Debian, and that a lot of the packages available in the repositories are directly “copied” from Debian. Some of this packages, however, have been patched by Ubuntu developers and thus have diverged from those in Debian: such packages have to be merged (i.e., the same changes, if they are still necessary, have to be applied again to each new version of them that gets into Ubuntu). Hence, since a) we are very good people and want Debian to enjoy those patched too, and b) such packages represent an unneeded maintenance overheat, as the same changes have to be applied again and again, it’s obvious that they have to be forwarded to Debian for their inclusion there.
So, why am I writing this? You all know our friend Launchpad, right? Now let’s have a look at Debian’s BTS… One word, intimidating. At least this was what I thought the first time I saw it, so I decided that I would write this post to introduce you to it’s basic use (it doesn’t make much sense, as there’s a big link to the help on the start page, but well… perhaps if you read it here you’ll fell more like reading it… or not :P).
Reporting a bug
How does it work? Just send an e-mail to submit@bugs.debian.org, with the following content:
Package: <package name>
Version: <package version>
<Bug description here>
Easy, isn’t it? The mail subject will be the title for the bug, and the version field can even be omitted if you don’t know it… Now, there’s something more you should know as an Ubuntu user: if you want to recognize a bug as coming from Ubuntu (for example if you are forwarding it from Launchpad), add the two following lines after the package name:
User: ubuntu-devel@lists.ubuntu.com
Usertags: origin-ubuntu hardy
OK. Now this is all. Just send such a mail and after some minutes you will receive a message telling you the bug number it got. If you want to send additional information just mail to <bug number>@bugs.debian.org. You won’t need much time to feel comfortable with it ;).
Searching bugs
Searching for bugs can still be somewhat unfriendly. If you think so, this might help a bit: «sudo aptitude install reportbug-ng». Now look on Applications -> System Tools. Now you are ready to rock on forwarding bugs to Debian!
Related posts:
- One week with Debian Jaunty was a great experience, until around a month (or perhaps a bit more) ago, when my nice ext4 file...
If one uses reportbug for reporting a bug, it even handholds you through the process and adds the version number on your behalf. I so prefer using reportbug over Launchpad for reporting.
Debian’s BTS sucks:
- it can’t search for bugreport’s text
- it can’t be used thru the webinterface (only poor search and viewing)
- you have to type all commands manually (ie. for merging a bug)
That’s why Launchpad’s Malone pwnz DebBugs.
I agree with you, but well, if the Debian guys like it…
I agree about all the minus parts Mr. Nightwalker mentioned, however when one compares the reporting bugs, Malone unfortunately has it’s own downsides:
- you don’t get prompted for a version number of the package
- there is no consistent way to mark what package version the bug affects
- having to be registered and logged in
- absolutely no way for user to indicate their opinion on severity, meaning even stuff that the user themself thinks is wishlist needs to sorted through with the same urgency as everything else.
I think it would be just glorious if the best sides of both were combined.
However, the thing I most miss in Ubuntu’s bug tracking is the human response. It feels a bit frustrating to report bugs when confirmed bug reports sit there untriaged for months. I’d gladly help, but alas, one seems to need to be MOTU or something for that.
Well, of course everything has it’s good and it’s bad sides… And Launchpad is still under active development, so I hope it’ll get a *lot* better.
- you don’t get prompted for a version number of the package
Well, you’re expected to indicate it on the description.
- there is no consistent way to mark what package version the bug affects
True… However, bugs should only be about problems that are present in the development release; and for those few that need to be fixed in “stable” releases, there is to possibility to mark them for a specific Ubuntu release.
- having to be registered and logged in
There’s also a mail interface, if you prefer that. And having to be registered also has it’s good things.
- absolutely no way for user to indicate their opinion on severity
You’re right on this. Personal tags is another feature I miss…
And I fully agree with you that there aren’t enough triagers. If you want to help have a look at https://wiki.ubuntu.com/HelpingWithBugs and join us in #ubuntu-bugs (server: irc.freenode.net); you don’t need to be MOTU for that, just join the open Launchpad team https://launchpad.net/~bugsquad and start contributing. Once you feel somewhat familiar with it you can apply to https://launchpad.net/~ubuntu-bugcontrol in order to be allowed to set the importance and see private bugs.
Thanks for your comments!