Translation(s): English - español - Italiano - Português (Brasil)

The BTS can keep track of the bug's versions. It's possible to state in which version a bug was found and in which version it was fixed.

Information on manipulating bugs by email

The complete documentation is found at:

found, notfound, close

Branches and NMU

The new system reads the Changelogs of the packages, so if a bug is fixed in a branch that is not in the debian/changelog of the current sid version (for example, if it appeared in a security update for stable, or similar), you can just state that the bug is found in that version and the system will realize that this version is not applicable to the current version in sid.

Also, if a bug is fixed in a NMU but the version of the NMU that fixed it is not incorporated when the next upload happens, the bug will remain open until the changes of the NMU are incorporated.

Closing invalid bugs

If a bug that is not really a bug gets reported (this is to say, a user failing to understand how the program actually works, or similar), it can still be closed sending a mail to without the pseudo-header, or using close 123456 without versioning.


If you need to reopen a bug that was closed as invalid, you would use the old reopen command. But if you are going to reopen a bug, because it's still present in the current version, you should send a mail to

found 123456 2.3-4


If in need of reassigning it would be a nice gesture to include the affected version of the package. In your mail to do:

reassign 123456 bar 2.0-1

Distribution specific tags

The sarge tag now means "don't archive this bug until it has been fixed in a version in sarge".

CategoryBugs | CategoryRedundant: merge with BTS