Translation(s): English - español - Français - Italiano - 한국어 - Português (Brasil) - Українська
Debian wiki bugs portal. This portal covers all aspects of reporting and working on bugs in Debian.
Debian bug tracking system
Debian GNU/Linux FAQ - How do I report a bug in Debian?
How to report a bug in Debian (using reportbug or email)
BTS (for Bug Tracking System) is a software created by the Debian Project for its own needs. It provides the following functionality:
- Web interface for viewing and browsing bugs and wishlist reports
- Can be fully controlled via email
- Users do not need to authenticate in order to report issues
- Filters to show different classes of bugs (ex.: having patches, with solution pending, already fixed, fixed in upstream, regarding localisation issues, etc.)
- Many more
When reporting a bug, please include the following information:
- What are you trying to do?
- How can the problem be reproduced (actions, commands...)
- What is the expected behavior?
- What happens instead?
- Version of the software
- Debian version/release
See also How to Report Bugs Effectively
If the bug affects all users of the software (not exclusively Debian), it is sometimes better to report it to Debian and directly to the upstream program developers/maintainers. Consult the official upstream website of the software for information on how to report bugs.
reportbug will automatically add relevant parts of your system configuration to bug reports.
reportbug - a tool for easy reporting of bugs in Debian
BSP - Bug Squashing Parties
Page refactoring in progress below this point
Bug reports can get closed in several ways:
A package upload that contains a closes: #12345 in the changelog. When the package is accepted into the archive this triggers a mail to email@example.com with Version: 1.2.3 in the first line of the mail. This will only start when the package in that version is in sync in unstable on all architectures and also in DebianTesting (if the bug affects testing).
Manually, by sending a mail to firstname.lastname@example.org with a Version: header field that claims the bug report to be fixed in that version. If the bug report is a non-issue (like, a false report) then the Version: line should not be added to the mail (this is needed for the BTS to be able to distinguish bugs fixed in a specific version and bugs that aren't really bugs).
Use https://bugs.debian.org/PACKAGENAME to list bugs for a specific package
Use https://bugs.debian.org/BUGNUMBER to access a specific bug report
Advanced bug search using UDD (the CGI script source can be a template for a customized local script, to be run against a public UDD instance)
Mail interface: commands reference, control messages, request commands
Bugs affecting the BTS : bugs.debian.org and debbugs
Teams/Debbugs - the team responsible for the BTS
debbugs - Tips, Tricks and Hacks, Anthony Towns 15th June, 2005 (video, slides)
Secret debian internals, Enrico Zini, 2007 at Fosdem : (video,slide)
All wiki pages about working with bugs in Debian: