Most packages have bugs in Debian's BTS (Bug Tracking System). This page describes some ways that anyone can help maintainers to deal with them.
You can also read this excellent introduction : How to use BTS
First read this document on working on bug reports
- Read this document with a good pinch of common sense; use your own judgement in cases you're not sure about or ask someone who is more experienced. (apologies for being patronising but some of this stuff you just get a feel for)
- You don't have to do everything this page says; do as much as you are comfortable with but don't be put off helping. Even small contributions can be valuable.
- Look at the source package bug page on the BTS or look at all that maintainer's bugs in order to get a better overview and to spot duplicate bugs.
Mails to <bugnumber>@bugs.debian.org go to the relevant maintainer(s) automatically but not the submitters or others who may be interested. Be sure to include the bug submitter in the To: or Cc: if you want them to see it.
Most of the time, put <bugnumber>@bugs.debian.org in the Reply-To: so that people know where to follow up to.
Don't be afraid of email@example.com; it's a public interface and anyone can help maintainers by helping them to triage bugs.
- Do listen to maintainers if they notice you triaging bugs and email you separately giving you advice or guidelines.
Send the mail in text format and not html. (for icedove it's in Account settings > Composition & addressing)
Read the Guide to bug control on the BTS so that you know what is possible when talking to firstname.lastname@example.org
Help Debian out by triaging bugs!
Ways you can help
Trying to reproduce bugs
Try reproducing old bug reports or any recent bug report which isn't tagged confirmed or pending.
If you can reproduce the problem then you should send a message to <bugnumber>@bugs.debian.org saying so and a message to email@example.com which says:
found <bugnumber> <versionnumber> tags <bugnumber> +confirmed thanks
Tagging unreproducible bugs
If you can't reproduce it but you're not sure it's fixed you could tag the bug as unreproducible and/or moreinfo and mail <bugnumber>@bugs.debian.org and the submitter (and anyone else who has the problem) for more information in order to try to reproduce it.
Closing unreproducible bugs
If you are sure that the bug does not exist in the current version of the package then you should close the bug by mailing <bugnumber>-firstname.lastname@example.org with an explanation of why this bug is now fixed (or how you couldn't reproduce it in the current version though be careful as you may just have a different setup to the submitter). Add as the first line of that message:
Version: <current version of the package you tested it under>
so the BTS knows which version it was fixed in and add a blank line under that before your message.
If a bug is filed against a generic or meta-package but actually concerns a different package then please reassign it to the correct package with a message to email@example.com which says:
reassign <bugnumber> <correct package> thanks
To find the correct package if you don't know you might use dpkg -S <some file> to find which package actually ships a particular file or use the interface to search the contents of packages (at the bottom of that page).
You might find when it is reassigned to the correct package that there is another bug for the same issue in which case please merge them (see below).
If you find two bugs for the same issue then they should be merged together. To be merged bugs must be on the same package and with the same severity and state. You can manipulate the packages, severity and tags with a message to firstname.lastname@example.org and at the end to merge the bugs add:
merge <bugnumber for one of the bugs> <bugnumber for the other bug> thanks
Forwarding reports upstream
Many bugs in Debian packages are bugs in the upstream package which have affected Debian users. If the package has an upstream bug tracker (see the upstream webpage for reference) then searching it for similar reports can be useful and may yield either a work around or in some cases the fact that the upstream author doesn't consider it a bug or doesn't want to fix it.
Both of these are useful information so post to the bug <bugnumber>@bugs.debian.org cc'ing the submitter and let them know. You might like to tell the BTS that the bug exists in upstream's bugtracker by sending the following to email@example.com:
forwarded <bugnumber> <URL of the bug in upstream's bugtracker> thanks
If you can't find a report upstream but it looks like a bug in upstream's software and you can reproduce it then you should file the bug in the upstream bugtracker with all the information necessary to reproduce it. You should also tell the BTS that you have done so with the forwarded command as above.
If you find a report that upstream claim it's fixed you could tag the bug fixed-upstream but be sure to mail the bug and explain why and which version it's fixed in which may persuade the maintainer to upload the new version.
If you find a bug in upstream's bugtracker has a patch then reviewing and/or testing it and mailing the bug to give the results is useful. If you find a patch that does indeed fix the bug then you could include it in the mail and tag the bug patch.
Other bug manipulation
There are many commands that the control interface to the BTS accepts and you might want to read the Guide to bug control on the BTS mentioned earlier to find out more about them.
If you have triaged bugs in anyway whatsoever then thank you for your contribution to Debian.
Don't stop there though! There are always more bugs and maintainers are always grateful for all the help you can give them.