Differences between revisions 1 and 2
Revision 1 as of 2006-06-13 00:47:30
Size: 3203
Editor: anonymous
Comment:
Revision 2 as of 2007-03-26 05:36:35
Size: 6108
Editor: ?ShontaWhelehan
Comment:
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
 * If you want to say that the bug 123456 was '''fixed''' in the version 1.2-3 of the package, you have two ways of doing it.    * If you want to say that the bug 123456 was '''fixed''' in the version 1.2-3 of the package, you have two ways of doing it.
Line 24: Line 24:
        Package: foo          Package: foo
Line 63: Line 63:
 [http://homepage.mac.com/revelation4/ las vegas webcam] | [http://forfend.freecities.com/34.html hot webcam mature] | [http://isotherms.741.com/83.html up the skirt] | [http://roguish.bravepages.com/89.html asian webcam sex] | [http://homepage.mac.com/valuably/87.html adult live webcams] | [http://wingspan.9cy.com/26.html real squirting videos] | [http://adagios.ibnsites.com/12.html bondage domination gallery] | [http://homepage.mac.com/platoon1/42.html webcam model tm-505] | [http://homepage.mac.com/richard129/38.html webcam archive girls] | [http://toenail.150m.com/83.html perfect facial asian] | [http://opart.100freemb.com/19.html female sex domination] | [http://haricot.kogaryu.com/26.html moby dick blogs] | [http://homepage.mac.com/pkwy1/92.html webcam cute girls] | [http://karaoke.1accesshost.com/86.html before us transsexual] | [http://magritte.freecities.com/81.html killing piss ants] | [http://indued.9cy.com/50.html hot beaver porn] | [http://toothsome.envy.nu/65.html drunk anal] | [http://estival.exactpages.com/9.html pissing vaginas] | [http://homepage.mac.com/impacted/57.html xxx webcam] | [http://warming.ibnsites.com/4.html actresses indian hot] | [http://roguish.bravepages.com/18.html chat webcam software] | [http://precinct.100freemb.com/96.html nude man celebrity] | [http://chipolata.exactpages.com/92.html erotic exotic ball] | [http://touchy.freewebpages.org/36.html sleeping panties] | [http://homepage.mac.com/sassiest/26.html collage girls webcam] | [http://couplings.g0g.net/3.html colleen milf] | [http://homepage.mac.com/lily21/3.html webcam girls capture] | [http://glamorous.9cy.com/21.html new panty peeing] | [http://fed.fcpages.com/76.html young clit closeup] | [http://toenail.150m.com/39.html teenage breast torture] | [http://homepage.mac.com/preface1/70.html software willing webcam] | [http://propellent.fcpages.com/18.html upskirt men] | [http://voyageur.exactpages.com/81.html reality porn reviews] | [http://homepage.mac.com/nite1/7.html webcam tetas] | [http://homepage.mac.com/congas1/50.html webcam teen sexy] | [http://homepage.mac.com/cryogenic1/89.html webcam stripping girl] | [http://cowgirls.o-f.com/10.html gang bang reality] | [http://randy.fcpages.com/17.html bethany interacial] | [http://voyageur.exactpages.com/6.html matures pantyhose] | [http://homepage.mac.com/lifeblood/70.html teen webcam] | [http://unpile.1sweethost.com/33.html hardcore lesbo orgies] | [http://homepage.mac.com/impasto1/57.html sophmore webcam nude] | [http://homepage.mac.com/platoon1/ fingering webcam 03] | [http://av.dreamstation.com/83.html freeones web cams] | [http://redeposit.angelcities.com/8.html gay anal clip] | [http://homepage.mac.com/defectives/6.html webcam flash boob] | [http://mephitical.kogaryu.com/65.html mmf clit] | [http://homepage.mac.com/kibbutz1/62.html naked webcam weekend] | [http://chorister.o-f.com/37.html webcam young teen]

?Include(English/SideBar)

The BTS has changed quite a lot due to the new feature of keeping track of the bug's versions. It's now possible to state in which version a bug was found and in which version it was fixed.

The complete BTS documentation is found at: http://www.debian.org/Bugs/server-control.en.html

found, notfound, close

  • If you want to state that the bug 123456 is present in the version 1.2-3 of the package, you have to mail control@bugs.debian.org with:

  found 123456 1.2-3

-->The version might be older or newer than the one the bug has been reported for. It's just a way of stating that you know the bug is present in it.

  • If you want to say that the bug 123456 is not present in the version 1.2-3 of the package, you have to mail control@bugs.debian.org with:

  notfound 123456 1.2-3
  • If you want to say that the bug 123456 was fixed in the version 1.2-3 of the package, you have two ways of doing it.

    • You can send a mail to 123456-done@bugs.debian.org, that starts with the pseudo-header:

        Package: foo
        Version: 1.2-3

---> The Source-Version pseudo-header is also available.

  • Or you can send a mail to control@bugs.debian.org with:

        close 123456 1.2-3

--->In this last case, it's probably is a good idea to CC: 123456-submitter@bugs.debian.org, so that the bug submitter knows that the bug was fixed in that version).

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 an 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 123456-done@bugs.debian.org without the pseudo-header, or using close 123456 without versioning.

Reopening

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 control@bugs.debian.org:

  found 123456 2.3-4

Reassigning

If in need of reassigning it would be a nice gesture to include the affected version of the package. In your mail to control@bugs.debian.org 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".