Differences between revisions 55 and 56
Revision 55 as of 2022-04-08 16:47:58
Size: 5128
Editor: nodiscc
Comment: fix syntax
Revision 56 as of 2022-04-08 16:49:47
Size: 5286
Editor: nodiscc
Comment: merge info from HowtoUseBTS, link to DebianTesting
Deletions are marked like this. Additions are marked like this.
Line 74: Line 74:
 * A package upload that contains a `closes: #12345` in the changelog. When the package is accepted into the archive this triggers a mail to `12345-done@bugs.debian.org` with `Version: 1.2.3` in the first line of the mail.  * A package upload that contains a `closes: #12345` in the changelog. When the package is accepted into the archive this triggers a mail to `12345-done@bugs.debian.org` 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).

Translation(s): English - español - Français - Italiano - 한국어 - Português (Brasil) - Українська


Portal/IDB/icon-wiki-portal.png

Debian wiki bugs portal. This portal covers all aspects of reporting and working on bugs in Debian.

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
  • Can be 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.)
  • User-defined tags

  • Many more



Reporting bugs

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

reportbug will automatically add relevant parts of your system configuration to bug reports.

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.

Documentation

Usage

Page refactoring in progress below this point

Closing bugs

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 12345-done@bugs.debian.org 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 bugnumber-done@bugs.debian.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).

See also

Wiki pages

All wiki pages about working with bugs in Debian:


CategoryBugs | CategoryPortal