Updating includes for squeeze.
This commit is contained in:
Daniel Baumann
parent
2c02bc4343
commit
a5a7943b6e
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
|
|
@ -597,7 +597,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -948,7 +948,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -541,7 +541,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -357,7 +357,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -703,7 +703,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -394,7 +394,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -743,7 +743,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -438,7 +438,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -376,7 +376,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -364,7 +364,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -1110,7 +1110,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -1186,7 +1186,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -327,7 +327,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -626,7 +626,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -666,7 +666,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -623,7 +623,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -281,7 +281,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -509,7 +509,7 @@ The Debian GNU/Linux FAQ
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<address>
|
<address>
|
||||||
version 4.0.3, 6 August 2008<br>
|
version 4.0.4+nmu1, 3 January 2010<br>
|
||||||
<br>
|
<br>
|
||||||
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
Authors are listed at <a href="ch-faqinfo.en.html#s-authors">Debian FAQ Authors</a><br>
|
||||||
<br>
|
<br>
|
||||||
|
|
|
||||||
|
|
@ -1,12 +1,10 @@
|
||||||
Methods of accessing the bug tracking system logs
|
|
||||||
|
|
||||||
Accessing active bug reports
|
Accessing active bug reports
|
||||||
|
|
||||||
Each message received at or sent by the bug processing system is
|
Each message received at or sent by the bug processing system is logged
|
||||||
logged and made available in a number of ways.
|
and made available in a number of ways.
|
||||||
|
|
||||||
The primary access method is to use the web pages. See the forms on
|
The primary access method is to use the web pages. See the forms on the
|
||||||
the main BTS page at http://bugs.debian.org/
|
main BTS page at http://bugs.debian.org/
|
||||||
|
|
||||||
There is a mailserver which can send bug reports as plain text on
|
There is a mailserver which can send bug reports as plain text on
|
||||||
request. To use it send the word help as the sole contents of an email
|
request. To use it send the word help as the sole contents of an email
|
||||||
|
|
@ -18,9 +16,8 @@ Accessing archived bug reports
|
||||||
|
|
||||||
Each closed bug report is archived 28 days after the last message
|
Each closed bug report is archived 28 days after the last message
|
||||||
relating to it is received and filed. This means that it is no longer
|
relating to it is received and filed. This means that it is no longer
|
||||||
possible to access it or change anything about it using the control
|
possible to access it or change anything about it using the control and
|
||||||
and service bots. However, the reports are still accessible for
|
service bots. However, the reports are still accessible for viewing.
|
||||||
viewing.
|
|
||||||
|
|
||||||
You can search the bug report archive using the WWW forms at
|
You can search the bug report archive using the WWW forms at
|
||||||
http://bugs.debian.org/, simply select the "archived bugs" option.
|
http://bugs.debian.org/, simply select the "archived bugs" option.
|
||||||
|
|
@ -44,12 +41,12 @@ Accessing the raw bug data
|
||||||
Please do not rely on *.status files in the bug spools, as they are
|
Please do not rely on *.status files in the bug spools, as they are
|
||||||
obsolete, for compatibility purposes only, and will be removed at some
|
obsolete, for compatibility purposes only, and will be removed at some
|
||||||
point in the future. Use the *.summary files instead.
|
point in the future. Use the *.summary files instead.
|
||||||
_________________________________________________________________
|
__________________________________________________________________
|
||||||
|
|
||||||
Debian BTS administrators <owner@bugs.debian.org>
|
Debian BTS administrators <owner@bugs.debian.org>
|
||||||
|
|
||||||
Debian bug tracking system
|
Debian bug tracking system
|
||||||
Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
|
Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
|
||||||
1994-1997 Ian Jackson.
|
1994-1997 Ian Jackson.
|
||||||
_________________________________________________________________
|
__________________________________________________________________
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,32 +1,30 @@
|
||||||
Introduction to the bug system request server
|
|
||||||
|
|
||||||
There is a mailserver which can send the bug reports and indices as
|
There is a mailserver which can send the bug reports and indices as
|
||||||
plain text on request.
|
plain text on request.
|
||||||
|
|
||||||
To use it you send a mail message to request@bugs.debian.org. The
|
To use it you send a mail message to request@bugs.debian.org. The
|
||||||
Subject of the message is ignored, except for generating the Subject
|
Subject of the message is ignored, except for generating the Subject of
|
||||||
of the reply.
|
the reply.
|
||||||
|
|
||||||
The body you send should be a series of commands, one per line. You'll
|
The body you send should be a series of commands, one per line. You'll
|
||||||
receive a reply which looks like a transcript of your message being
|
receive a reply which looks like a transcript of your message being
|
||||||
interpreted, with a response to each command. No notifications are
|
interpreted, with a response to each command. No notifications are sent
|
||||||
sent to anyone for the commands listed here and the mail isn't logged
|
to anyone for the commands listed here and the mail isn't logged
|
||||||
anywhere publicly available.
|
anywhere publicly available.
|
||||||
|
|
||||||
Any text on a line starting with a hash sign # is ignored; the server
|
Any text on a line starting with a hash sign # is ignored; the server
|
||||||
will stop processing when it finds a line with a control terminator (
|
will stop processing when it finds a line with a control terminator (
|
||||||
quit, thank you, or two hyphens are common examples). It will also
|
quit, thank you, or two hyphens are common examples). It will also stop
|
||||||
stop if it encounters too many unrecognised or badly-formatted
|
if it encounters too many unrecognised or badly-formatted commands. If
|
||||||
commands. If no commands are successfully handled it will send the
|
no commands are successfully handled it will send the help text for the
|
||||||
help text for the server.
|
server.
|
||||||
|
|
||||||
Commands available
|
Commands available
|
||||||
|
|
||||||
send bugnumber
|
send bugnumber
|
||||||
send-detail bugnumber
|
send-detail bugnumber
|
||||||
Requests the transcript for the bug report in question.
|
Requests the transcript for the bug report in question.
|
||||||
send-detail sends all of the "boring" messages in the
|
send-detail sends all of the "boring" messages in the transcript
|
||||||
transcript as well, such as the various auto-acks.
|
as well, such as the various auto-acks.
|
||||||
|
|
||||||
index [full]
|
index [full]
|
||||||
index-summary by-package
|
index-summary by-package
|
||||||
|
|
@ -36,8 +34,8 @@ Commands available
|
||||||
number, respectively.
|
number, respectively.
|
||||||
|
|
||||||
index-maint
|
index-maint
|
||||||
Requests the index page giving the list of maintainers with
|
Requests the index page giving the list of maintainers with bugs
|
||||||
bugs (open and recently-closed) in the tracking system.
|
(open and recently-closed) in the tracking system.
|
||||||
|
|
||||||
index maint maintainer
|
index maint maintainer
|
||||||
Requests the index pages of bugs in the system for the
|
Requests the index pages of bugs in the system for the
|
||||||
|
|
@ -57,8 +55,8 @@ Commands available
|
||||||
send-unmatched last|-1
|
send-unmatched last|-1
|
||||||
send-unmatched old|-2
|
send-unmatched old|-2
|
||||||
Requests logs of messages not matched to a particular bug
|
Requests logs of messages not matched to a particular bug
|
||||||
report, for this week, last week and the week before. (Each
|
report, for this week, last week and the week before. (Each week
|
||||||
week ends on a Wednesday.)
|
ends on a Wednesday.)
|
||||||
|
|
||||||
getinfo filename
|
getinfo filename
|
||||||
Request a file containing information about package(s) and or
|
Request a file containing information about package(s) and or
|
||||||
|
|
@ -102,19 +100,18 @@ Commands available
|
||||||
--
|
--
|
||||||
Stops processing at this point of the message. After this you
|
Stops processing at this point of the message. After this you
|
||||||
may include any text you like, and it will be ignored. You can
|
may include any text you like, and it will be ignored. You can
|
||||||
use this to include longer comments than are suitable for #,
|
use this to include longer comments than are suitable for #, for
|
||||||
for example for the benefit of human readers of your message
|
example for the benefit of human readers of your message
|
||||||
(reading it via the tracking system logs or due to a CC or
|
(reading it via the tracking system logs or due to a CC or BCC).
|
||||||
BCC).
|
|
||||||
|
|
||||||
#...
|
#...
|
||||||
One-line comment. The # must be at the start of the line.
|
One-line comment. The # must be at the start of the line.
|
||||||
|
|
||||||
debug level
|
debug level
|
||||||
Sets the debugging level to level, which should be a
|
Sets the debugging level to level, which should be a nonnegative
|
||||||
nonnegative integer. 0 is no debugging; 1 is usually
|
integer. 0 is no debugging; 1 is usually sufficient. The
|
||||||
sufficient. The debugging output appears in the transcript. It
|
debugging output appears in the transcript. It is not likely to
|
||||||
is not likely to be useful to general users of the bug system.
|
be useful to general users of the bug system.
|
||||||
|
|
||||||
There is a reference card for the mailservers, available via the WWW,
|
There is a reference card for the mailservers, available via the WWW,
|
||||||
in bug-mailserver-refcard.txt or by email using the refcard command
|
in bug-mailserver-refcard.txt or by email using the refcard command
|
||||||
|
|
@ -122,19 +119,19 @@ Commands available
|
||||||
|
|
||||||
If you wish to manipulate bug reports you should use the
|
If you wish to manipulate bug reports you should use the
|
||||||
control@bugs.debian.org address, which understands a superset of the
|
control@bugs.debian.org address, which understands a superset of the
|
||||||
commands listed above. This is described in another document,
|
commands listed above. This is described in another document, available
|
||||||
available on the WWW, in the file bug-maint-mailcontrol.txt, or by
|
on the WWW, in the file bug-maint-mailcontrol.txt, or by sending help
|
||||||
sending help to control@bugs.
|
to control@bugs.
|
||||||
|
|
||||||
In case you are reading this as a plain text file or via email: an
|
In case you are reading this as a plain text file or via email: an HTML
|
||||||
HTML version is available via the bug system main contents page
|
version is available via the bug system main contents page
|
||||||
http://www.debian.org/Bugs/.
|
http://www.debian.org/Bugs/.
|
||||||
_________________________________________________________________
|
__________________________________________________________________
|
||||||
|
|
||||||
Debian BTS administrators <owner@bugs.debian.org>
|
Debian BTS administrators <owner@bugs.debian.org>
|
||||||
|
|
||||||
Debian bug tracking system
|
Debian bug tracking system
|
||||||
Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
|
Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
|
||||||
1994-1997 Ian Jackson.
|
1994-1997 Ian Jackson.
|
||||||
_________________________________________________________________
|
__________________________________________________________________
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,3 @@
|
||||||
Mail servers' reference card
|
|
||||||
|
|
||||||
Full documentation of the mail servers is available on the WWW, in the
|
Full documentation of the mail servers is available on the WWW, in the
|
||||||
files bug-log-mailserver.txt and bug-maint-mailcontrol.txt or by
|
files bug-log-mailserver.txt and bug-maint-mailcontrol.txt or by
|
||||||
sending the word help to each mailserver.
|
sending the word help to each mailserver.
|
||||||
|
|
@ -70,12 +68,12 @@ Synopsis of bug submission and followup addresses
|
||||||
* nnn-done
|
* nnn-done
|
||||||
* nnn-close
|
* nnn-close
|
||||||
* nnn-subscribe
|
* nnn-subscribe
|
||||||
_________________________________________________________________
|
__________________________________________________________________
|
||||||
|
|
||||||
Debian BTS administrators <owner@bugs.debian.org>
|
Debian BTS administrators <owner@bugs.debian.org>
|
||||||
|
|
||||||
Debian bug tracking system
|
Debian bug tracking system
|
||||||
Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
|
Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
|
||||||
1994-1997 Ian Jackson.
|
1994-1997 Ian Jackson.
|
||||||
_________________________________________________________________
|
__________________________________________________________________
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,15 +1,12 @@
|
||||||
Developers' information regarding the bug processing system
|
|
||||||
|
|
||||||
Initially, a bug report is submitted by a user as an ordinary mail
|
Initially, a bug report is submitted by a user as an ordinary mail
|
||||||
message to submit@bugs.debian.org. This will then be given a number,
|
message to submit@bugs.debian.org. This will then be given a number,
|
||||||
acknowledged to the user, and forwarded to debian-bugs-dist. If the
|
acknowledged to the user, and forwarded to debian-bugs-dist. If the
|
||||||
submitter included a Package line listing a package with a known
|
submitter included a Package line listing a package with a known
|
||||||
maintainer the maintainer will get a copy too.
|
maintainer the maintainer will get a copy too.
|
||||||
|
|
||||||
The Subject line will have Bug#nnn: added, and the Reply-To will be
|
The Subject line will have Bug#nnn: added, and the Reply-To will be set
|
||||||
set to include both the submitter of the report and
|
to include both the submitter of the report and nnn@bugs.debian.org.
|
||||||
nnn@bugs.debian.org.
|
__________________________________________________________________
|
||||||
_________________________________________________________________
|
|
||||||
|
|
||||||
* Closing bug reports
|
* Closing bug reports
|
||||||
* Followup messages
|
* Followup messages
|
||||||
|
|
@ -22,20 +19,20 @@ Developers' information regarding the bug processing system
|
||||||
* Subscribing to bugs
|
* Subscribing to bugs
|
||||||
* More-or-less obsolete subject-scanning feature
|
* More-or-less obsolete subject-scanning feature
|
||||||
* Obsolete X-Debian-PR: quiet feature
|
* Obsolete X-Debian-PR: quiet feature
|
||||||
_________________________________________________________________
|
__________________________________________________________________
|
||||||
|
|
||||||
Closing bug reports
|
Closing bug reports
|
||||||
|
|
||||||
Debian bug reports should be closed when the problem is fixed.
|
Debian bug reports should be closed when the problem is fixed. Problems
|
||||||
Problems in packages can only be considered fixed once a package that
|
in packages can only be considered fixed once a package that includes
|
||||||
includes the bug fix enters the Debian archive.
|
the bug fix enters the Debian archive.
|
||||||
|
|
||||||
Normally, the only people that should close a bug report are the
|
Normally, the only people that should close a bug report are the
|
||||||
submitter of the bug and the maintainer(s) of the package against
|
submitter of the bug and the maintainer(s) of the package against which
|
||||||
which the bug is filed. There are exceptions to this rule, for
|
the bug is filed. There are exceptions to this rule, for example, the
|
||||||
example, the bugs filed against unknown packages or certain generic
|
bugs filed against unknown packages or certain generic pseudo-packages.
|
||||||
pseudo-packages. When in doubt, don't close bugs, first ask for advice
|
When in doubt, don't close bugs, first ask for advice on the
|
||||||
on the debian-devel mailing list.
|
debian-devel mailing list.
|
||||||
|
|
||||||
Bug reports should be closed by sending email to
|
Bug reports should be closed by sending email to
|
||||||
nnn-done@bugs.debian.org. The message body needs to contain an
|
nnn-done@bugs.debian.org. The message body needs to contain an
|
||||||
|
|
@ -52,8 +49,8 @@ Closing bug reports
|
||||||
|
|
||||||
The person closing the bug, the person who submitted it and the
|
The person closing the bug, the person who submitted it and the
|
||||||
debian-bugs-closed mailing list will each get a notification about the
|
debian-bugs-closed mailing list will each get a notification about the
|
||||||
change in status of the report. The submitter and the mailing list
|
change in status of the report. The submitter and the mailing list will
|
||||||
will also receive the contents of the message sent to nnn-done.
|
also receive the contents of the message sent to nnn-done.
|
||||||
|
|
||||||
Followup messages
|
Followup messages
|
||||||
|
|
||||||
|
|
@ -62,9 +59,9 @@ Followup messages
|
||||||
forwarding the bug report. Please note that these are two distinct
|
forwarding the bug report. Please note that these are two distinct
|
||||||
addresses.
|
addresses.
|
||||||
|
|
||||||
If a developer wishes to reply to a bug report they should simply
|
If a developer wishes to reply to a bug report they should simply reply
|
||||||
reply to the message, respecting the Reply-To header. This will not
|
to the message, respecting the Reply-To header. This will not close the
|
||||||
close the bug.
|
bug.
|
||||||
|
|
||||||
The bug tracking system will receive the message at
|
The bug tracking system will receive the message at
|
||||||
nnn@bugs.debian.org, pass it on to the package maintainer, file the
|
nnn@bugs.debian.org, pass it on to the package maintainer, file the
|
||||||
|
|
@ -97,8 +94,8 @@ Severity levels
|
||||||
The bug system records a severity level with each bug report. This is
|
The bug system records a severity level with each bug report. This is
|
||||||
set to normal by default, but can be overridden either by supplying a
|
set to normal by default, but can be overridden either by supplying a
|
||||||
Severity line in the pseudo-header when the bug is submitted (see the
|
Severity line in the pseudo-header when the bug is submitted (see the
|
||||||
instructions for reporting bugs), or by using the severity command
|
instructions for reporting bugs), or by using the severity command with
|
||||||
with the control request server.
|
the control request server.
|
||||||
|
|
||||||
The severity levels are:
|
The severity levels are:
|
||||||
|
|
||||||
|
|
@ -114,9 +111,9 @@ Severity levels
|
||||||
|
|
||||||
serious
|
serious
|
||||||
is a severe violation of Debian policy (roughly, it violates a
|
is a severe violation of Debian policy (roughly, it violates a
|
||||||
"must" or "required" directive), or, in the package
|
"must" or "required" directive), or, in the package maintainer's
|
||||||
maintainer's or release manager's opinion, makes the package
|
or release manager's opinion, makes the package unsuitable for
|
||||||
unsuitable for release.
|
release.
|
||||||
|
|
||||||
important
|
important
|
||||||
a bug which has a major effect on the usability of a package,
|
a bug which has a major effect on the usability of a package,
|
||||||
|
|
@ -134,10 +131,10 @@ Severity levels
|
||||||
difficult to fix due to major design considerations.
|
difficult to fix due to major design considerations.
|
||||||
|
|
||||||
Certain severities are considered release-critical, meaning the bug
|
Certain severities are considered release-critical, meaning the bug
|
||||||
will have an impact on releasing the package with the stable release
|
will have an impact on releasing the package with the stable release of
|
||||||
of Debian. Currently, these are critical, grave and serious. For
|
Debian. Currently, these are critical, grave and serious. For complete
|
||||||
complete and canonical rules on what issues merit these severities,
|
and canonical rules on what issues merit these severities, see the list
|
||||||
see the list of Release-Critical Issues for Lenny.
|
of Release-Critical Issues for Lenny.
|
||||||
|
|
||||||
Tags for bug reports
|
Tags for bug reports
|
||||||
|
|
||||||
|
|
@ -146,9 +143,9 @@ Tags for bug reports
|
||||||
when you look at the full bug log.
|
when you look at the full bug log.
|
||||||
|
|
||||||
Tags can be set by supplying a Tags line in the pseudo-header when the
|
Tags can be set by supplying a Tags line in the pseudo-header when the
|
||||||
bug is submitted (see the instructions for reporting bugs), or by
|
bug is submitted (see the instructions for reporting bugs), or by using
|
||||||
using the tags command with the control request server. Separate
|
the tags command with the control request server. Separate multiple
|
||||||
multiple tags with commas, spaces, or both.
|
tags with commas, spaces, or both.
|
||||||
|
|
||||||
The current bug tags are:
|
The current bug tags are:
|
||||||
|
|
||||||
|
|
@ -162,15 +159,15 @@ Tags for bug reports
|
||||||
This bug won't be fixed. Possibly because this is a choice
|
This bug won't be fixed. Possibly because this is a choice
|
||||||
between two arbitrary ways of doing things and the maintainer
|
between two arbitrary ways of doing things and the maintainer
|
||||||
and submitter prefer different ways of doing things, possibly
|
and submitter prefer different ways of doing things, possibly
|
||||||
because changing the behaviour will cause other, worse,
|
because changing the behaviour will cause other, worse, problems
|
||||||
problems for others, or possibly for other reasons.
|
for others, or possibly for other reasons.
|
||||||
|
|
||||||
moreinfo
|
moreinfo
|
||||||
This bug can't be addressed until more information is provided
|
This bug can't be addressed until more information is provided
|
||||||
by the submitter. The bug will be closed if the submitter
|
by the submitter. The bug will be closed if the submitter
|
||||||
doesn't provide more information in a reasonable (few months)
|
doesn't provide more information in a reasonable (few months)
|
||||||
timeframe. This is for bugs like "It doesn't work". What
|
timeframe. This is for bugs like "It doesn't work". What doesn't
|
||||||
doesn't work?
|
work?
|
||||||
|
|
||||||
unreproducible
|
unreproducible
|
||||||
This bug can't be reproduced on the maintainer's system.
|
This bug can't be reproduced on the maintainer's system.
|
||||||
|
|
@ -181,8 +178,8 @@ Tags for bug reports
|
||||||
The maintainer is requesting help with dealing with this bug.
|
The maintainer is requesting help with dealing with this bug.
|
||||||
|
|
||||||
pending
|
pending
|
||||||
A solution to this bug has been found and an upload will be
|
A solution to this bug has been found and an upload will be made
|
||||||
made soon.
|
soon.
|
||||||
|
|
||||||
fixed
|
fixed
|
||||||
This bug is fixed or worked around (by a non-maintainer upload,
|
This bug is fixed or worked around (by a non-maintainer upload,
|
||||||
|
|
@ -238,8 +235,8 @@ Tags for bug reports
|
||||||
This bug particularly applies to the woody distribution.
|
This bug particularly applies to the woody distribution.
|
||||||
|
|
||||||
sarge
|
sarge
|
||||||
This is a distribution tag, which has two effects. When set on
|
This is a distribution tag, which has two effects. When set on a
|
||||||
a bug, the bug can only affect sarge (though it may also affect
|
bug, the bug can only affect sarge (though it may also affect
|
||||||
other distributions if other distribution tags are set) but
|
other distributions if other distribution tags are set) but
|
||||||
otherwise normal buggy/fixed/absent rules apply. The bug also
|
otherwise normal buggy/fixed/absent rules apply. The bug also
|
||||||
should not be archived until it is fixed in sarge.
|
should not be archived until it is fixed in sarge.
|
||||||
|
|
@ -251,8 +248,8 @@ Tags for bug reports
|
||||||
from them.
|
from them.
|
||||||
|
|
||||||
etch
|
etch
|
||||||
This is a distribution tag, which has two effects. When set on
|
This is a distribution tag, which has two effects. When set on a
|
||||||
a bug, the bug can only affect etch (though it may also affect
|
bug, the bug can only affect etch (though it may also affect
|
||||||
other distributions if other distribution tags are set) but
|
other distributions if other distribution tags are set) but
|
||||||
otherwise normal buggy/fixed/absent rules apply. The bug also
|
otherwise normal buggy/fixed/absent rules apply. The bug also
|
||||||
should not be archived until it is fixed in etch.
|
should not be archived until it is fixed in etch.
|
||||||
|
|
@ -264,11 +261,11 @@ Tags for bug reports
|
||||||
from them.
|
from them.
|
||||||
|
|
||||||
lenny
|
lenny
|
||||||
This is a release tag, which has two effects. When set on a
|
This is a release tag, which has two effects. When set on a bug,
|
||||||
bug, the bug can only affect lenny (though it may also affect
|
the bug can only affect lenny (though it may also affect other
|
||||||
other releases if other release tags are set) but otherwise
|
releases if other release tags are set) but otherwise normal
|
||||||
normal buggy/fixed/absent rules apply. The bug also should not
|
buggy/fixed/absent rules apply. The bug also should not be
|
||||||
be archived until it is fixed in lenny.
|
archived until it is fixed in lenny.
|
||||||
|
|
||||||
lenny-ignore
|
lenny-ignore
|
||||||
This release-critical bug is to be ignored for the purposes of
|
This release-critical bug is to be ignored for the purposes of
|
||||||
|
|
@ -277,11 +274,11 @@ Tags for bug reports
|
||||||
authorization from them.
|
authorization from them.
|
||||||
|
|
||||||
squeeze
|
squeeze
|
||||||
This is a release tag, which has two effects. When set on a
|
This is a release tag, which has two effects. When set on a bug,
|
||||||
bug, the bug can only affect squeeze (though it may also affect
|
the bug can only affect squeeze (though it may also affect other
|
||||||
other releases if other release tags are set) but otherwise
|
releases if other release tags are set) but otherwise normal
|
||||||
normal buggy/fixed/absent rules apply. The bug also should not
|
buggy/fixed/absent rules apply. The bug also should not be
|
||||||
be archived until it is fixed in squeeze.
|
archived until it is fixed in squeeze.
|
||||||
|
|
||||||
squeeze-ignore
|
squeeze-ignore
|
||||||
This release-critical bug is to be ignored for the purposes of
|
This release-critical bug is to be ignored for the purposes of
|
||||||
|
|
@ -290,40 +287,48 @@ Tags for bug reports
|
||||||
authorization from them.
|
authorization from them.
|
||||||
|
|
||||||
sid
|
sid
|
||||||
This is a release tag, which has two effects. When set on a
|
This is a release tag, which has two effects. When set on a bug,
|
||||||
bug, the bug can only affect sid (though it may also affect
|
the bug can only affect sid (though it may also affect other
|
||||||
other releases if other release tags are set) but otherwise
|
releases if other release tags are set) but otherwise normal
|
||||||
normal buggy/fixed/absent rules apply. The bug also should not
|
buggy/fixed/absent rules apply. The bug also should not be
|
||||||
be archived until it is fixed in sid.
|
archived until it is fixed in sid.
|
||||||
|
|
||||||
experimental
|
experimental
|
||||||
This is a release tag, which has two effects. When set on a
|
This is a release tag, which has two effects. When set on a bug,
|
||||||
bug, the bug can only affect experimental (though it may also
|
the bug can only affect experimental (though it may also affect
|
||||||
affect other releases if other release tags are set) but
|
other releases if other release tags are set) but otherwise
|
||||||
otherwise normal buggy/fixed/absent rules apply. The bug also
|
normal buggy/fixed/absent rules apply. The bug also should not
|
||||||
should not be archived until it is fixed in experimental.
|
be archived until it is fixed in experimental.
|
||||||
|
|
||||||
The meanings of the latter 8 tags have changed recently; the ignore
|
The meanings of the latter 8 distribution-specific tags have changed
|
||||||
tags ignore the bug for the purpose of a testing propagation. The
|
recently; the -ignore tags ignore the bug for the purposes of testing
|
||||||
release tags, which used to only indicate which bugs affected a
|
propagation. The release tags indicate that the bug in question should
|
||||||
specific release, now indicate when a bug can be archived and the set
|
not be archived until it is fixed in the set of releases specified. The
|
||||||
of releases for which a bug can be considered to be found or fixed.
|
release tags also indicate that a bug should only be considered buggy
|
||||||
|
in the set of releases specified. [In other words, the bug is absent in
|
||||||
|
any release whose corresponding release tag is not set if any release
|
||||||
|
tags are set; otherwise the normal found/fixed rules apply.]
|
||||||
|
|
||||||
|
Release tags should not be used if proper versioning of the bug would
|
||||||
|
achieve the desired effect, as they require manual addition and
|
||||||
|
removal. If you are unsure if a release tag is required, contact the
|
||||||
|
Debian BTS Administrators (owner@bugs.debian.org) or the release team
|
||||||
|
for advice.
|
||||||
|
|
||||||
Recording that you have passed on a bug report
|
Recording that you have passed on a bug report
|
||||||
|
|
||||||
When a developer forwards a bug report to the developer of the
|
When a developer forwards a bug report to the developer of the upstream
|
||||||
upstream source package from which the Debian package is derived, they
|
source package from which the Debian package is derived, they should
|
||||||
should note this in the bug tracking system as follows:
|
note this in the bug tracking system as follows:
|
||||||
|
|
||||||
Make sure that the To field of your message to the author has only the
|
Make sure that the To field of your message to the author has only the
|
||||||
author(s) address(es) in it; put the person who reported the bug,
|
author(s) address(es) in it; put the person who reported the bug,
|
||||||
nnn-forwarded@bugs.debian.org and nnn@bugs.debian.org in the CC field.
|
nnn-forwarded@bugs.debian.org and nnn@bugs.debian.org in the CC field.
|
||||||
|
|
||||||
Ask the author to preserve the CC to nnn-forwarded@bugs.debian.org
|
Ask the author to preserve the CC to nnn-forwarded@bugs.debian.org when
|
||||||
when they reply, so that the bug tracking system will file their reply
|
they reply, so that the bug tracking system will file their reply with
|
||||||
with the original report. These messages are only filed and are not
|
the original report. These messages are only filed and are not sent on;
|
||||||
sent on; to send a message as normal, send them to nnn@bugs.debian.org
|
to send a message as normal, send them to nnn@bugs.debian.org as well.
|
||||||
as well.
|
|
||||||
|
|
||||||
When the bug tracking system gets a message at nnn-forwarded it will
|
When the bug tracking system gets a message at nnn-forwarded it will
|
||||||
mark the relevant bug as having been forwarded to the address(es) in
|
mark the relevant bug as having been forwarded to the address(es) in
|
||||||
|
|
@ -342,8 +347,8 @@ Changing bug ownership
|
||||||
have an owner.
|
have an owner.
|
||||||
|
|
||||||
The owner can be set by supplying an Owner line in the pseudo-header
|
The owner can be set by supplying an Owner line in the pseudo-header
|
||||||
when the bug is submitted (see the instructions for reporting bugs),
|
when the bug is submitted (see the instructions for reporting bugs), or
|
||||||
or by using the owner and noowner commands with the control request
|
by using the owner and noowner commands with the control request
|
||||||
server.
|
server.
|
||||||
|
|
||||||
Incorrectly listed package maintainers
|
Incorrectly listed package maintainers
|
||||||
|
|
@ -361,24 +366,24 @@ Reopening, reassigning and manipulating bugs
|
||||||
|
|
||||||
It is possible to reassign bug reports to other packages, to reopen
|
It is possible to reassign bug reports to other packages, to reopen
|
||||||
erroneously-closed ones, to modify the information saying to where, if
|
erroneously-closed ones, to modify the information saying to where, if
|
||||||
anywhere, a bug report has been forwarded, to change the severities
|
anywhere, a bug report has been forwarded, to change the severities and
|
||||||
and titles of reports, to set the ownership of bugs, to merge and
|
titles of reports, to set the ownership of bugs, to merge and unmerge
|
||||||
unmerge bug reports, and to record the versions of packages in which
|
bug reports, and to record the versions of packages in which bugs were
|
||||||
bugs were found and in which they were fixed. This is done by sending
|
found and in which they were fixed. This is done by sending mail to
|
||||||
mail to control@bugs.debian.org.
|
control@bugs.debian.org.
|
||||||
|
|
||||||
The format of these messages is described in another document
|
The format of these messages is described in another document available
|
||||||
available on the World Wide Web or in the file
|
on the World Wide Web or in the file bug-maint-mailcontrol.txt. A plain
|
||||||
bug-maint-mailcontrol.txt. A plain text version can also be obtained
|
text version can also be obtained by mailing the word help to the
|
||||||
by mailing the word help to the server at the address above.
|
server at the address above.
|
||||||
|
|
||||||
Subscribing to bugs
|
Subscribing to bugs
|
||||||
|
|
||||||
The bug tracking system also allows bug submitters, developers and
|
The bug tracking system also allows bug submitters, developers and
|
||||||
other interested third parties to subscribe to individual bugs. This
|
other interested third parties to subscribe to individual bugs. This
|
||||||
feature can be used by those wishing to keep an eye on a bug, without
|
feature can be used by those wishing to keep an eye on a bug, without
|
||||||
having to subscribe to a package through the PTS. All messages that
|
having to subscribe to a package through the PTS. All messages that are
|
||||||
are received at nnn@bugs.debian.org, are sent to subscribers.
|
received at nnn@bugs.debian.org, are sent to subscribers.
|
||||||
|
|
||||||
Subscribing to a bug can be done by sending an email to
|
Subscribing to a bug can be done by sending an email to
|
||||||
nnn-subscribe@bugs.debian.org. The subject and body of the email are
|
nnn-subscribe@bugs.debian.org. The subject and body of the email are
|
||||||
|
|
@ -389,17 +394,16 @@ Subscribing to bugs
|
||||||
It is also possible to unsubscribe from a bug. Unsubscribing can be
|
It is also possible to unsubscribe from a bug. Unsubscribing can be
|
||||||
done by sending an email to nnn-unsubscribe@bugs.debian.org. The
|
done by sending an email to nnn-unsubscribe@bugs.debian.org. The
|
||||||
subject and body of the email are again ignored by the BTS. Users will
|
subject and body of the email are again ignored by the BTS. Users will
|
||||||
be sent a confirmation message which they must reply to if they wish
|
be sent a confirmation message which they must reply to if they wish to
|
||||||
to be unsubscribed from the bug.
|
be unsubscribed from the bug.
|
||||||
|
|
||||||
By default, the address subscribed is the one found in the From
|
By default, the address subscribed is the one found in the From header.
|
||||||
header. If you wish to subscribe another address to a bug, you will
|
If you wish to subscribe another address to a bug, you will need to
|
||||||
need to encode the address to be subscribed into the subscription
|
encode the address to be subscribed into the subscription message. This
|
||||||
message. This takes the form of:
|
takes the form of: nnn-subscribe-localpart=example.com@bugs.debian.org.
|
||||||
nnn-subscribe-localpart=example.com@bugs.debian.org. That example
|
That example would send localpart@example.com a subscription message
|
||||||
would send localpart@example.com a subscription message for bug nnn.
|
for bug nnn. The @ sign must be encoded by changing it to an = sign.
|
||||||
The @ sign must be encoded by changing it to an = sign. Similarly, an
|
Similarly, an unsubscription takes the form
|
||||||
unsubscription takes the form
|
|
||||||
nnn-unsubscribe-localpart=example.com@bugs.debian.org. In both cases,
|
nnn-unsubscribe-localpart=example.com@bugs.debian.org. In both cases,
|
||||||
the subject and body of the email will be forwarded to the email
|
the subject and body of the email will be forwarded to the email
|
||||||
address within the request for confirmation.
|
address within the request for confirmation.
|
||||||
|
|
@ -413,13 +417,12 @@ More-or-less obsolete subject-scanning feature
|
||||||
example, by using reply to all recipients).
|
example, by using reply to all recipients).
|
||||||
|
|
||||||
A similar scheme operates for maintonly, done, quiet and forwarded,
|
A similar scheme operates for maintonly, done, quiet and forwarded,
|
||||||
which treat mail arriving with a Subject tag as having been sent to
|
which treat mail arriving with a Subject tag as having been sent to the
|
||||||
the corresponding nnn-whatever@bugs.debian.org address.
|
corresponding nnn-whatever@bugs.debian.org address.
|
||||||
|
|
||||||
Messages arriving at plain forwarded and done -- ie, with no bug
|
Messages arriving at plain forwarded and done -- ie, with no bug report
|
||||||
report number in the address -- and without a bug number in the
|
number in the address -- and without a bug number in the Subject will
|
||||||
Subject will be filed under "junk" and kept for a few weeks, but
|
be filed under "junk" and kept for a few weeks, but otherwise ignored.
|
||||||
otherwise ignored.
|
|
||||||
|
|
||||||
Obsolete X-Debian-PR: quiet feature
|
Obsolete X-Debian-PR: quiet feature
|
||||||
|
|
||||||
|
|
@ -427,14 +430,14 @@ Obsolete X-Debian-PR: quiet feature
|
||||||
forwarding anywhere messages it received at debian-bugs, by putting an
|
forwarding anywhere messages it received at debian-bugs, by putting an
|
||||||
X-Debian-PR: quiet line in the actual mail header.
|
X-Debian-PR: quiet line in the actual mail header.
|
||||||
|
|
||||||
This header line is now ignored. Instead, send your message to quiet
|
This header line is now ignored. Instead, send your message to quiet or
|
||||||
or nnn-quiet (or maintonly or nnn-maintonly).
|
nnn-quiet (or maintonly or nnn-maintonly).
|
||||||
_________________________________________________________________
|
__________________________________________________________________
|
||||||
|
|
||||||
Debian BTS administrators <owner@bugs.debian.org>
|
Debian BTS administrators <owner@bugs.debian.org>
|
||||||
|
|
||||||
Debian bug tracking system
|
Debian bug tracking system
|
||||||
Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
|
Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
|
||||||
1994-1997 Ian Jackson.
|
1994-1997 Ian Jackson.
|
||||||
_________________________________________________________________
|
__________________________________________________________________
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,13 +1,11 @@
|
||||||
Introduction to the bug control and manipulation mailserver
|
|
||||||
|
|
||||||
Just as request@bugs.debian.org allows the retrieval of bug data and
|
Just as request@bugs.debian.org allows the retrieval of bug data and
|
||||||
documentation by email, control@bugs.debian.org allows bug reports to
|
documentation by email, control@bugs.debian.org allows bug reports to
|
||||||
be manipulated in various ways.
|
be manipulated in various ways.
|
||||||
|
|
||||||
The control server works just like the request server, except that it
|
The control server works just like the request server, except that it
|
||||||
has some additional commands; in fact, it's the same program. The two
|
has some additional commands; in fact, it's the same program. The two
|
||||||
addresses are only separated to avoid users making mistakes and
|
addresses are only separated to avoid users making mistakes and causing
|
||||||
causing problems while merely trying to request information.
|
problems while merely trying to request information.
|
||||||
|
|
||||||
Since the commands specific to the control server actually change the
|
Since the commands specific to the control server actually change the
|
||||||
status of a bug, a notification about processing the commands is sent
|
status of a bug, a notification about processing the commands is sent
|
||||||
|
|
@ -26,34 +24,36 @@ Introduction to the bug control and manipulation mailserver
|
||||||
|
|
||||||
Commands available at the control mailserver
|
Commands available at the control mailserver
|
||||||
|
|
||||||
General Versioning Duplicates Misc.
|
General Versioning Duplicates Misc.
|
||||||
|
|
||||||
reassign
|
reassign
|
||||||
severity
|
severity
|
||||||
tag
|
tag
|
||||||
retitle
|
retitle
|
||||||
submitter
|
submitter
|
||||||
|
affects
|
||||||
|
summary
|
||||||
|
|
||||||
found | notfound
|
found | notfound
|
||||||
fixed | notfixed
|
fixed | notfixed
|
||||||
reopen
|
reopen
|
||||||
|
|
||||||
merge | unmerge
|
merge | unmerge
|
||||||
forcemerge
|
forcemerge
|
||||||
clone
|
clone
|
||||||
|
|
||||||
thanks
|
thanks
|
||||||
#
|
#
|
||||||
forwarded | notforwarded
|
forwarded | notforwarded
|
||||||
owner | noowner
|
owner | noowner
|
||||||
block | unblock
|
block | unblock
|
||||||
archive | unarchive
|
archive | unarchive
|
||||||
|
|
||||||
reassign bugnumber package [ version ]
|
reassign bugnumber package [ version ]
|
||||||
Records that bug #bugnumber is a bug in package. This can be
|
Records that bug #bugnumber is a bug in package. This can be
|
||||||
used to set the package if the user forgot the pseudo-header,
|
used to set the package if the user forgot the pseudo-header, or
|
||||||
or to change an earlier assignment. No notifications are sent
|
to change an earlier assignment. No notifications are sent to
|
||||||
to anyone (other than the usual information in the processing
|
anyone (other than the usual information in the processing
|
||||||
transcript).
|
transcript).
|
||||||
|
|
||||||
If you supply a version, the bug tracking system will note that
|
If you supply a version, the bug tracking system will note that
|
||||||
|
|
@ -62,52 +62,55 @@ Commands available at the control mailserver
|
||||||
You can assign a bug to two packages at once by separating the
|
You can assign a bug to two packages at once by separating the
|
||||||
package names with a comma. However, you should only do this if
|
package names with a comma. However, you should only do this if
|
||||||
the bug can be fixed by a change to either package. If this is
|
the bug can be fixed by a change to either package. If this is
|
||||||
not the case, you should clone the bug and reassign the clone
|
not the case, you should clone the bug and reassign the clone to
|
||||||
to the other package.
|
the other package.
|
||||||
|
|
||||||
reopen bugnumber [ originator-address | = | ! ]
|
reopen bugnumber [ originator-address | = | ! ]
|
||||||
Reopens #bugnumber if it is closed.
|
Reopens #bugnumber if it is closed.
|
||||||
|
|
||||||
By default, or if you specify =, the original submitter is
|
By default, or if you specify =, the original submitter is still
|
||||||
still as the originator of the report, so that they will get
|
as the originator of the report, so that they will get the ack
|
||||||
the ack when it is closed again.
|
when it is closed again.
|
||||||
|
|
||||||
If you supply an originator-address the originator will be set
|
If you supply an originator-address the originator will be set
|
||||||
to the address you supply. If you wish to become the new
|
to the address you supply. If you wish to become the new
|
||||||
originator of the reopened report you can use the ! shorthand
|
originator of the reopened report you can use the ! shorthand or
|
||||||
or specify your own email address.
|
specify your own email address.
|
||||||
|
|
||||||
It is usually a good idea to tell the person who is about to be
|
It is usually a good idea to tell the person who is about to be
|
||||||
recorded as the originator that you're reopening the report, so
|
recorded as the originator that you're reopening the report, so
|
||||||
that they will know to expect the ack which they'll get when it
|
that they will know to expect the ack which they'll get when it
|
||||||
is closed again.
|
is closed again.
|
||||||
|
|
||||||
If the bug is not closed then reopen won't do anything, not
|
If the bug is not closed then reopen won't do anything, not even
|
||||||
even change the originator. To change the originator of an open
|
change the originator. To change the originator of an open bug
|
||||||
bug report, use the submitter command; note that this will
|
report, use the submitter command; note that this will inform
|
||||||
inform the original submitter of the change.
|
the original submitter of the change.
|
||||||
|
|
||||||
If the bug was recorded as being closed in a particular version
|
If the bug was recorded as being closed in a particular version
|
||||||
of a package but recurred in a later version, it is better to
|
of a package but recurred in a later version, it is better to
|
||||||
use the found command instead.
|
use the found command instead.
|
||||||
|
|
||||||
found bugnumber [ version ]
|
found bugnumber [ version ]
|
||||||
Record that #bugnumber has been encountered in the given
|
Record that #bugnumber has been encountered in the given version
|
||||||
version of the package to which it is assigned.
|
of the package to which it is assigned. version may be a fully
|
||||||
|
qualified version, of the form sourcepackagename/version.
|
||||||
|
|
||||||
The bug tracking system uses this information, in conjunction
|
The bug tracking system uses this information, in conjunction
|
||||||
with fixed versions recorded when closing bugs, to display
|
with fixed versions recorded when closing bugs, to display lists
|
||||||
lists of bugs open in various versions of each package. It
|
of bugs open in various versions of each package. It considers a
|
||||||
considers a bug to be open when it has no fixed version, or
|
bug to be open when it has no fixed version, or when it has been
|
||||||
when it has been found more recently than it has been fixed.
|
found more recently than it has been fixed.
|
||||||
|
|
||||||
If no version is given, then the list of fixed versions for the
|
If no version is given, then the list of fixed versions for the
|
||||||
bug is cleared. This is identical to the behaviour of reopen.
|
bug is cleared. This is identical to the behaviour of reopen.
|
||||||
|
version may be a fully qualified version, of the form
|
||||||
|
sourcepackagename/version.
|
||||||
|
|
||||||
This command will only cause a bug to be marked as not done if
|
This command will only cause a bug to be marked as not done if
|
||||||
no version is specified, or if the version being marked found
|
no version is specified, or if the version being marked found is
|
||||||
is equal to the version which was last marked fixed. (If you
|
equal to or greater than the highest version marked fixed. (If
|
||||||
are certain that you want the bug marked as not done, use
|
you are certain that you want the bug marked as not done, use
|
||||||
reopen in conjunction with found.)
|
reopen in conjunction with found.)
|
||||||
|
|
||||||
This command was introduced in preference to reopen because it
|
This command was introduced in preference to reopen because it
|
||||||
|
|
@ -116,16 +119,18 @@ Commands available at the control mailserver
|
||||||
|
|
||||||
notfound bugnumber version
|
notfound bugnumber version
|
||||||
Remove the record that #bugnumber was encountered in the given
|
Remove the record that #bugnumber was encountered in the given
|
||||||
version of the package to which it is assigned.
|
version of the package to which it is assigned. version may be a
|
||||||
|
fully qualified version, of the form sourcepackagename/version.
|
||||||
|
|
||||||
This differs from closing the bug at that version in that the
|
This differs from closing the bug at that version in that the
|
||||||
bug is not listed as fixed in that version either; no
|
bug is not listed as fixed in that version either; no
|
||||||
information about that version will be known. It is intended
|
information about that version will be known. It is intended for
|
||||||
for fixing mistakes in the record of when a bug was found.
|
fixing mistakes in the record of when a bug was found.
|
||||||
|
|
||||||
fixed bugnumber version
|
fixed bugnumber version
|
||||||
Indicate that bug #bugnumber was fixed in the given version of
|
Indicate that bug #bugnumber was fixed in the given version of
|
||||||
the package to which it is assigned.
|
the package to which it is assigned. version may be a fully
|
||||||
|
qualified version, of the form sourcepackagename/version.
|
||||||
|
|
||||||
This does not cause the bug to be marked as closed, it merely
|
This does not cause the bug to be marked as closed, it merely
|
||||||
adds another version in which the bug was fixed. Use the
|
adds another version in which the bug was fixed. Use the
|
||||||
|
|
@ -134,11 +139,16 @@ Commands available at the control mailserver
|
||||||
|
|
||||||
notfixed bugnumber version
|
notfixed bugnumber version
|
||||||
Remove the record that bug #bugnumber has been fixed in the
|
Remove the record that bug #bugnumber has been fixed in the
|
||||||
given version.
|
given version. version may be a fully qualified version, of the
|
||||||
|
form sourcepackagename/version.
|
||||||
|
|
||||||
This command is equivalent to found followed by notfound (the
|
This command is equivalent to found followed by notfound (the
|
||||||
found removes the fixed at a particular version, and notfound
|
found removes the fixed at a particular version, and notfound
|
||||||
removes the found.)
|
removes the found) with the exception that the bug is not
|
||||||
|
reopened if the found version is greater than any existing fixed
|
||||||
|
version. It is intended for fixing mistakes in the record of
|
||||||
|
when a bug was fixed; in most cases, you actually want found,
|
||||||
|
not notfixed.
|
||||||
|
|
||||||
submitter bugnumber originator-address | !
|
submitter bugnumber originator-address | !
|
||||||
Changes the originator of #bugnumber to originator-address.
|
Changes the originator of #bugnumber to originator-address.
|
||||||
|
|
@ -155,7 +165,14 @@ Commands available at the control mailserver
|
||||||
maintainer at address. This does not actually forward the
|
maintainer at address. This does not actually forward the
|
||||||
report. This can be used to change an existing incorrect
|
report. This can be used to change an existing incorrect
|
||||||
forwarded-to address, or to record a new one for a bug that
|
forwarded-to address, or to record a new one for a bug that
|
||||||
wasn't previously noted as having been forwarded.
|
wasn't previously noted as having been forwarded. address should
|
||||||
|
generally be a URI, or possibly an email address. Using a URI
|
||||||
|
where possible allows tools to query a remote bug tracking
|
||||||
|
system (such as bugzilla) for a bug's status.
|
||||||
|
|
||||||
|
Example usage:
|
||||||
|
|
||||||
|
forwarded 12345 http://bugz.illa.foo/cgi/54321
|
||||||
|
|
||||||
notforwarded bugnumber
|
notforwarded bugnumber
|
||||||
Forgets any idea that bugnumber has been forwarded to any
|
Forgets any idea that bugnumber has been forwarded to any
|
||||||
|
|
@ -163,17 +180,14 @@ Commands available at the control mailserver
|
||||||
forwarded then this will do nothing.
|
forwarded then this will do nothing.
|
||||||
|
|
||||||
retitle bugnumber new-title
|
retitle bugnumber new-title
|
||||||
Changes the title of a bug report to that specified (the
|
Changes the title of a bug report to that specified (the default
|
||||||
default is the Subject mail header from the original report).
|
is the Subject mail header from the original report). Will also
|
||||||
|
change the titles of all bug reports which this bug is merged
|
||||||
Unlike most of the other bug-manipulation commands when used on
|
with.
|
||||||
one of a set of merged reports this will change the title of
|
|
||||||
only the individual bug requested, and not all those with which
|
|
||||||
it is merged.
|
|
||||||
|
|
||||||
severity bugnumber severity
|
severity bugnumber severity
|
||||||
Set the severity level for bug report #bugnumber to severity.
|
Set the severity level for bug report #bugnumber to severity. No
|
||||||
No notification is sent to the user who reported the bug.
|
notification is sent to the user who reported the bug.
|
||||||
|
|
||||||
Severities are critical, grave, serious, important, normal,
|
Severities are critical, grave, serious, important, normal,
|
||||||
minor, and wishlist.
|
minor, and wishlist.
|
||||||
|
|
@ -181,6 +195,27 @@ Commands available at the control mailserver
|
||||||
For their meanings please consult the general developers'
|
For their meanings please consult the general developers'
|
||||||
documentation for the bug system.
|
documentation for the bug system.
|
||||||
|
|
||||||
|
affects bugnumber [ + | - | = ] package [ package ... ]
|
||||||
|
Indicates that a bug affects another package. In the case where
|
||||||
|
bugnumber causes breakage in package even though the bug is
|
||||||
|
actually present in the package to which it is assigned, this
|
||||||
|
causes the bug to be listed by default in the package list of
|
||||||
|
package. This should generally be used where the bug is severe
|
||||||
|
enough to cause multiple reports from users to be assigned to
|
||||||
|
the wrong package.
|
||||||
|
|
||||||
|
summary bugnumber [message number]
|
||||||
|
Selects a message to use as a summary of a bug. The first
|
||||||
|
non-pseudoheader paragraph of that message is parsed and set as
|
||||||
|
the summary of the bug which is displayed on the top of the bug
|
||||||
|
report page. This is useful in cases where the original report
|
||||||
|
doesn't correctly describe the problem or the bug has many
|
||||||
|
messages which make it difficult to identify the actual problem.
|
||||||
|
|
||||||
|
If message number is not given, clears the summary. message
|
||||||
|
number is the message number as listed in the bugreport cgi
|
||||||
|
script output.
|
||||||
|
|
||||||
clone bugnumber NewID [ new IDs ... ]
|
clone bugnumber NewID [ new IDs ... ]
|
||||||
The clone control command allows you to duplicate a bug report.
|
The clone control command allows you to duplicate a bug report.
|
||||||
It is useful in the case where a single report actually
|
It is useful in the case where a single report actually
|
||||||
|
|
@ -203,21 +238,21 @@ Commands available at the control mailserver
|
||||||
merge -1 -3
|
merge -1 -3
|
||||||
|
|
||||||
merge bugnumber bugnumber ...
|
merge bugnumber bugnumber ...
|
||||||
Merges two or more bug reports. When reports are merged
|
Merges two or more bug reports. When reports are merged opening,
|
||||||
opening, closing, marking or unmarking as forwarded and
|
closing, marking or unmarking as forwarded and reassigning any
|
||||||
reassigning any of the bugs to a new package will have an
|
of the bugs to a new package will have an identical effect on
|
||||||
identical effect on all of the merged reports.
|
all of the merged reports.
|
||||||
|
|
||||||
Before bugs can be merged they must be in exactly the same
|
Before bugs can be merged they must be in exactly the same
|
||||||
state: either all open or all closed, with the same
|
state: either all open or all closed, with the same forwarded-to
|
||||||
forwarded-to upstream author address or all not marked as
|
upstream author address or all not marked as forwarded, all
|
||||||
forwarded, all assigned to the same package or package(s) (an
|
assigned to the same package or package(s) (an exact string
|
||||||
exact string comparison is done on the package to which the bug
|
comparison is done on the package to which the bug is assigned),
|
||||||
is assigned), and all of the same severity. If they don't start
|
and all of the same severity. If they don't start out in the
|
||||||
out in the same state you should use reassign, reopen and so
|
same state you should use reassign, reopen and so forth to make
|
||||||
forth to make sure that they are before using merge. Titles are
|
sure that they are before using merge. Titles are not required
|
||||||
not required to match, and will not be affected by the merge.
|
to match, and will not be affected by the merge. Tags are not
|
||||||
Tags are not required to match, either, they will be joined.
|
required to match, either, they will be joined.
|
||||||
|
|
||||||
If any of the bugs listed in a merge command is already merged
|
If any of the bugs listed in a merge command is already merged
|
||||||
with another bug then all the reports merged with any of the
|
with another bug then all the reports merged with any of the
|
||||||
|
|
@ -227,17 +262,15 @@ Commands available at the control mailserver
|
||||||
Merging reports causes a note to appear on each report's logs;
|
Merging reports causes a note to appear on each report's logs;
|
||||||
on the WWW pages this is includes links to the other bugs.
|
on the WWW pages this is includes links to the other bugs.
|
||||||
|
|
||||||
Merged reports are all expired simultaneously, and only when
|
Merged reports are all expired simultaneously, and only when all
|
||||||
all of the reports each separately meet the criteria for
|
of the reports each separately meet the criteria for expiry.
|
||||||
expiry.
|
|
||||||
|
|
||||||
forcemerge bugnumber bugnumber ...
|
forcemerge bugnumber bugnumber ...
|
||||||
Forcibly merges two or more bug reports. The first bug listed
|
Forcibly merges two or more bug reports. The settings of the
|
||||||
is the master bug, and its settings (the settings which must be
|
first bug listed which must be equal in a normal merge are
|
||||||
equal in a normal merge) are assigned to the bugs listed next.
|
assigned to the bugs listed next. To avoid typos erroneously
|
||||||
To avoid typos erroneously merging bugs, bugs must be in the
|
merging bugs, bugs must be in the same package. See the text
|
||||||
same package. See the text above for a description of what
|
above for a description of what merging means.
|
||||||
merging means.
|
|
||||||
|
|
||||||
Note that this makes it possible to close bugs by merging; you
|
Note that this makes it possible to close bugs by merging; you
|
||||||
are responsible for notifying submitters with an appropriate
|
are responsible for notifying submitters with an appropriate
|
||||||
|
|
@ -259,12 +292,13 @@ Commands available at the control mailserver
|
||||||
you want to disconnect more than one bug simply include several
|
you want to disconnect more than one bug simply include several
|
||||||
unmerge commands in your message.
|
unmerge commands in your message.
|
||||||
|
|
||||||
tags bugnumber [ + | - | = ] tag [ tag ... ]
|
tags bugnumber [ + | - | = ] tag [ tag ... ] [ + | - | = tag ... ] ]
|
||||||
Sets tags for the bug report #bugnumber. No notification is
|
Sets tags for the bug report #bugnumber. No notification is sent
|
||||||
sent to the user who reported the bug. Setting the action to +
|
to the user who reported the bug. Setting the action to + means
|
||||||
means to add each given tag, - means to remove each given tag,
|
to add each tag following, - means to remove each tag following,
|
||||||
and = means to ignore the current tags and set them afresh to
|
and = means to set the following tags to the list provided.
|
||||||
the list provided. The default action is adding.
|
Intervening +, -, or = change the action for the tags following.
|
||||||
|
The default action is adding.
|
||||||
|
|
||||||
Example usage:
|
Example usage:
|
||||||
|
|
||||||
|
|
@ -283,6 +317,9 @@ Commands available at the control mailserver
|
||||||
# set tags to exactly 'moreinfo' and 'unreproducible'
|
# set tags to exactly 'moreinfo' and 'unreproducible'
|
||||||
tags 123456 = moreinfo unreproducible
|
tags 123456 = moreinfo unreproducible
|
||||||
|
|
||||||
|
# remove the moreinfo tag and add a patch tag
|
||||||
|
tags 123456 - moreinfo + patch
|
||||||
|
|
||||||
Available tags currently include patch, wontfix, moreinfo,
|
Available tags currently include patch, wontfix, moreinfo,
|
||||||
unreproducible, help, pending, fixed, fixed-in-experimental,
|
unreproducible, help, pending, fixed, fixed-in-experimental,
|
||||||
fixed-upstream, security, upstream, confirmed, d-i, ipv6, lfs,
|
fixed-upstream, security, upstream, confirmed, d-i, ipv6, lfs,
|
||||||
|
|
@ -304,24 +341,24 @@ Commands available at the control mailserver
|
||||||
close bugnumber [ fixed-version ] (deprecated)
|
close bugnumber [ fixed-version ] (deprecated)
|
||||||
Close bug report #bugnumber.
|
Close bug report #bugnumber.
|
||||||
|
|
||||||
A notification is sent to the user who reported the bug, but
|
A notification is sent to the user who reported the bug, but (in
|
||||||
(in contrast to mailing bugnumber-done@bugs.debian.org) the
|
contrast to mailing bugnumber-done@bugs.debian.org) the text of
|
||||||
text of the mail which caused the bug to be closed is not
|
the mail which caused the bug to be closed is not included in
|
||||||
included in that notification. The maintainer who closes a
|
that notification. The maintainer who closes a report needs to
|
||||||
report needs to ensure, probably by sending a separate message,
|
ensure, probably by sending a separate message, that the user
|
||||||
that the user who reported the bug knows why it is being
|
who reported the bug knows why it is being closed. The use of
|
||||||
closed. The use of this command is therefore deprecated. See
|
this command is therefore deprecated. See the developer's
|
||||||
the developer's information about how to close a bug properly.
|
information about how to close a bug properly.
|
||||||
|
|
||||||
If you supply a fixed-version, the bug tracking system will
|
If you supply a fixed-version, the bug tracking system will note
|
||||||
note that the bug was fixed in that version of the package.
|
that the bug was fixed in that version of the package.
|
||||||
|
|
||||||
package [ packagename ... ]
|
package [ packagename ... ]
|
||||||
Limits the following commands so that they will only apply to
|
Limits the following commands so that they will only apply to
|
||||||
bugs filed against the listed packages. You can list one or
|
bugs filed against the listed packages. You can list one or more
|
||||||
more packages. If you don't list any packages, the following
|
packages. If you don't list any packages, the following commands
|
||||||
commands will apply to all bugs. You're encouraged to use this
|
will apply to all bugs. You're encouraged to use this as a
|
||||||
as a safety feature in case you accidentally use the wrong bug
|
safety feature in case you accidentally use the wrong bug
|
||||||
numbers.
|
numbers.
|
||||||
|
|
||||||
Example usage:
|
Example usage:
|
||||||
|
|
@ -337,13 +374,12 @@ Commands available at the control mailserver
|
||||||
severity 234567 wishlist
|
severity 234567 wishlist
|
||||||
|
|
||||||
owner bugnumber address | !
|
owner bugnumber address | !
|
||||||
Sets address to be the "owner" of #bugnumber. The owner of a
|
Sets address to be the "owner" of #bugnumber. The owner of a bug
|
||||||
bug claims responsibility for fixing it. This is useful to
|
claims responsibility for fixing it. This is useful to share out
|
||||||
share out work in cases where a package has a team of
|
work in cases where a package has a team of maintainers.
|
||||||
maintainers.
|
|
||||||
|
|
||||||
If you wish to become the owner of the bug yourself, you can
|
If you wish to become the owner of the bug yourself, you can use
|
||||||
use the ! shorthand or specify your own email address.
|
the ! shorthand or specify your own email address.
|
||||||
|
|
||||||
noowner bugnumber
|
noowner bugnumber
|
||||||
Forgets any idea that the bug has an owner other than the usual
|
Forgets any idea that the bug has an owner other than the usual
|
||||||
|
|
@ -356,17 +392,20 @@ Commands available at the control mailserver
|
||||||
requirements for archival, ignoring time.
|
requirements for archival, ignoring time.
|
||||||
|
|
||||||
unarchive bugnumber
|
unarchive bugnumber
|
||||||
Unarchives a bug that was previously archived. Unarchival
|
Unarchives a bug that was previously archived. Unarchival should
|
||||||
should generally be coupled with reopen and found/fixed as
|
generally be coupled with reopen and found/fixed as appropriate.
|
||||||
appropriate. Bugs that have been unarchived can be archived
|
Bugs that have been unarchived can be archived using archive
|
||||||
using archive assuming the non-time based archival requirements
|
assuming the non-time based archival requirements are met. You
|
||||||
are met.
|
should not be using unarchive to make trivial changes to
|
||||||
|
archived bugs, such as changing the submitter; its primary
|
||||||
|
purpose is to allow for the reopening of bugs which have been
|
||||||
|
archived without the intervention of BTS administrators.
|
||||||
|
|
||||||
#...
|
#...
|
||||||
One-line comment. The # must be at the start of the line. The
|
One-line comment. The # must be at the start of the line. The
|
||||||
text of comments will be included in the acknowledgement sent
|
text of comments will be included in the acknowledgement sent to
|
||||||
to the sender and to affected maintainers, so you can use this
|
the sender and to affected maintainers, so you can use this to
|
||||||
to document the reasons for your commands.
|
document the reasons for your commands.
|
||||||
|
|
||||||
quit
|
quit
|
||||||
stop
|
stop
|
||||||
|
|
@ -380,12 +419,12 @@ Commands available at the control mailserver
|
||||||
message; the remainder of the message can include explanations,
|
message; the remainder of the message can include explanations,
|
||||||
signatures or anything else, none of it will be detected by the
|
signatures or anything else, none of it will be detected by the
|
||||||
control server.
|
control server.
|
||||||
_________________________________________________________________
|
__________________________________________________________________
|
||||||
|
|
||||||
Debian BTS administrators <owner@bugs.debian.org>
|
Debian BTS administrators <owner@bugs.debian.org>
|
||||||
|
|
||||||
Debian bug tracking system
|
Debian bug tracking system
|
||||||
Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
|
Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
|
||||||
1994-1997 Ian Jackson.
|
1994-1997 Ian Jackson.
|
||||||
_________________________________________________________________
|
__________________________________________________________________
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -1,9 +1,8 @@
|
||||||
How to report a bug in Debian using reportbug
|
|
||||||
|
|
||||||
We strongly recommend that you report bugs in Debian using the
|
We strongly recommend that you report bugs in Debian using the
|
||||||
reportbug program. To install and start it, simply run:
|
reportbug program. To install and start it, simply run:
|
||||||
|
|
||||||
aptitude install reportbug; reportbug
|
# aptitude install reportbug
|
||||||
|
$ reportbug
|
||||||
|
|
||||||
It will guide you through the bug reporting process step by step.
|
It will guide you through the bug reporting process step by step.
|
||||||
|
|
||||||
|
|
@ -27,8 +26,8 @@ What package does your bug report belong to?
|
||||||
asking for advice.
|
asking for advice.
|
||||||
|
|
||||||
If your problem doesn't relate just to one package but some general
|
If your problem doesn't relate just to one package but some general
|
||||||
Debian service, there are several pseudo-packages or even mailing
|
Debian service, there are several pseudo-packages or even mailing lists
|
||||||
lists that you can use to relay your message to us instead.
|
that you can use to relay your message to us instead.
|
||||||
|
|
||||||
Has your bug report been filed already?
|
Has your bug report been filed already?
|
||||||
|
|
||||||
|
|
@ -46,24 +45,22 @@ Send multiple reports for multiple bugs
|
||||||
|
|
||||||
Don't file bugs upstream
|
Don't file bugs upstream
|
||||||
|
|
||||||
If you file a bug in Debian, don't send a copy to the upstream
|
If you file a bug in Debian, don't send a copy to the upstream software
|
||||||
software maintainers yourself, as it is possible that the bug exists
|
maintainers yourself, as it is possible that the bug exists only in
|
||||||
only in Debian. If necessary, the maintainer of the package will
|
Debian. If necessary, the maintainer of the package will forward the
|
||||||
forward the bug upstream.
|
bug upstream.
|
||||||
|
|
||||||
Sending the bug report via e-mail
|
Sending the bug report via e-mail
|
||||||
|
|
||||||
You can report bugs in Debian by sending an e-mail to
|
You can report bugs in Debian by sending an e-mail to
|
||||||
submit@bugs.debian.org with a special format described below.
|
submit@bugs.debian.org with a special format described below. reportbug
|
||||||
reportbug (see above) will properly format the e-mails for you; please
|
(see above) will properly format the e-mails for you; please use it!
|
||||||
use it!
|
|
||||||
|
|
||||||
Headers
|
Headers
|
||||||
|
|
||||||
Like any e-mail you should include a clear, descriptive Subject line
|
Like any e-mail you should include a clear, descriptive Subject line in
|
||||||
in your main mail header. The subject you give will be used as the
|
your main mail header. The subject you give will be used as the initial
|
||||||
initial bug title in the tracking system, so please try to make it
|
bug title in the tracking system, so please try to make it informative!
|
||||||
informative!
|
|
||||||
|
|
||||||
If you'd like to send a copy of your bug report to additional
|
If you'd like to send a copy of your bug report to additional
|
||||||
recipients (such as mailing lists), you shouldn't use the usual e-mail
|
recipients (such as mailing lists), you shouldn't use the usual e-mail
|
||||||
|
|
@ -87,10 +84,10 @@ Version: <packageversion>
|
||||||
tracking system relies on this field to work out which releases are
|
tracking system relies on this field to work out which releases are
|
||||||
affected by the bug.
|
affected by the bug.
|
||||||
|
|
||||||
You need to supply a correct Package line in the pseudo-header in
|
You need to supply a correct Package line in the pseudo-header in order
|
||||||
order for the bug tracking system to deliver the message to the
|
for the bug tracking system to deliver the message to the package's
|
||||||
package's maintainer. See this example for information on how to find
|
maintainer. See this example for information on how to find this
|
||||||
this information.
|
information.
|
||||||
|
|
||||||
For other valid pseudo-headers, see Additional pseudo-headers
|
For other valid pseudo-headers, see Additional pseudo-headers
|
||||||
|
|
||||||
|
|
@ -118,16 +115,15 @@ The body of the report
|
||||||
hardware in your system, as problems are often caused by IRQ and
|
hardware in your system, as problems are often caused by IRQ and
|
||||||
I/O address conflicts.
|
I/O address conflicts.
|
||||||
* If you have reportbug installed the output of reportbug -q
|
* If you have reportbug installed the output of reportbug -q
|
||||||
--template -T none -s none -S normal -b --list-cc none -q
|
--template -T none -s none -S normal -b --list-cc none -q <package>
|
||||||
<package> will also be useful, as it contains the output of
|
will also be useful, as it contains the output of maintainer
|
||||||
maintainer specific scripts and version information.
|
specific scripts and version information.
|
||||||
|
|
||||||
Include any detail that seems relevant -- you are in very little
|
Include any detail that seems relevant -- you are in very little danger
|
||||||
danger of making your report too long by including too much
|
of making your report too long by including too much information. If
|
||||||
information. If they are small, please include in your report any
|
they are small, please include in your report any files you were using
|
||||||
files you were using to reproduce the problem. (If they are large,
|
to reproduce the problem. (If they are large, consider making them
|
||||||
consider making them available on a publicly available website if
|
available on a publicly available website if possible.)
|
||||||
possible.)
|
|
||||||
|
|
||||||
For more advice on how to help the developers solve your problem,
|
For more advice on how to help the developers solve your problem,
|
||||||
please read How to Report Bugs Effectively.
|
please read How to Report Bugs Effectively.
|
||||||
|
|
@ -165,10 +161,10 @@ Sending copies of bug reports to other addresses
|
||||||
|
|
||||||
You could do this by CC'ing your bug report to the other address(es),
|
You could do this by CC'ing your bug report to the other address(es),
|
||||||
but then the other copies would not have the bug report number put in
|
but then the other copies would not have the bug report number put in
|
||||||
the Reply-To field and the Subject line. When the recipients reply
|
the Reply-To field and the Subject line. When the recipients reply they
|
||||||
they will probably preserve the submit@bugs.debian.org entry in the
|
will probably preserve the submit@bugs.debian.org entry in the header
|
||||||
header and have their message filed as a new bug report. This leads to
|
and have their message filed as a new bug report. This leads to many
|
||||||
many duplicated reports.
|
duplicated reports.
|
||||||
|
|
||||||
The right way to do this is to use the X-Debbugs-CC header. Add a line
|
The right way to do this is to use the X-Debbugs-CC header. Add a line
|
||||||
like this to your message's mail header:
|
like this to your message's mail header:
|
||||||
|
|
@ -193,9 +189,9 @@ Severity levels
|
||||||
|
|
||||||
If a report is of a particularly serious bug, or is merely a feature
|
If a report is of a particularly serious bug, or is merely a feature
|
||||||
request, you can set the severity level of the bug as you report it.
|
request, you can set the severity level of the bug as you report it.
|
||||||
This is not required however, and the package maintainer will assign
|
This is not required however, and the package maintainer will assign an
|
||||||
an appropriate severity level to your report even if you do not (or
|
appropriate severity level to your report even if you do not (or pick
|
||||||
pick the wrong severity).
|
the wrong severity).
|
||||||
|
|
||||||
To assign a severity level, put a line like this one in the
|
To assign a severity level, put a line like this one in the
|
||||||
pseudo-header:
|
pseudo-header:
|
||||||
|
|
@ -215,8 +211,8 @@ Assigning tags
|
||||||
Tags: <tags>
|
Tags: <tags>
|
||||||
|
|
||||||
Replace <tags> with one or more of the available tags, as described in
|
Replace <tags> with one or more of the available tags, as described in
|
||||||
the advanced documentation. Separate multiple tags with commas,
|
the advanced documentation. Separate multiple tags with commas, spaces,
|
||||||
spaces, or both.
|
or both.
|
||||||
User: <username>
|
User: <username>
|
||||||
Usertags: <usertags>
|
Usertags: <usertags>
|
||||||
|
|
||||||
|
|
@ -240,8 +236,8 @@ Source: foopackage
|
||||||
foopackage; for most bugs in most packages you don't want to use this
|
foopackage; for most bugs in most packages you don't want to use this
|
||||||
option.
|
option.
|
||||||
|
|
||||||
Finally, if your MUA doesn't allow you to edit the headers, you can
|
Finally, if your MUA doesn't allow you to edit the headers, you can set
|
||||||
set the various X-Debbugs- headers in the pseudo-headers.
|
the various X-Debbugs- headers in the pseudo-headers.
|
||||||
|
|
||||||
Additional information
|
Additional information
|
||||||
|
|
||||||
|
|
@ -249,9 +245,9 @@ Different submission addresses (minor or mass bug reports)
|
||||||
|
|
||||||
If a bug report is minor, for example, a documentation typo or a
|
If a bug report is minor, for example, a documentation typo or a
|
||||||
trivial build problem, please adjust the severity appropriately and
|
trivial build problem, please adjust the severity appropriately and
|
||||||
send it to maintonly@bugs.debian.org instead of
|
send it to maintonly@bugs.debian.org instead of submit@bugs.debian.org.
|
||||||
submit@bugs.debian.org. maintonly will forward the report to the
|
maintonly will forward the report to the package maintainer only, it
|
||||||
package maintainer only, it won't forward it to the BTS mailing lists.
|
won't forward it to the BTS mailing lists.
|
||||||
|
|
||||||
If you're submitting many reports at once, you should definitely use
|
If you're submitting many reports at once, you should definitely use
|
||||||
maintonly@bugs.debian.org so that you don't cause too much redundant
|
maintonly@bugs.debian.org so that you don't cause too much redundant
|
||||||
|
|
@ -259,49 +255,60 @@ Different submission addresses (minor or mass bug reports)
|
||||||
you may also want to post a summary on debian-bugs-dist.
|
you may also want to post a summary on debian-bugs-dist.
|
||||||
|
|
||||||
If wish to report a bug to the bug tracking system that's already been
|
If wish to report a bug to the bug tracking system that's already been
|
||||||
sent to the maintainer, you can use quiet@bugs.debian.org. Bugs sent
|
sent to the maintainer, you can use quiet@bugs.debian.org. Bugs sent to
|
||||||
to quiet@bugs.debian.org will not be forwarded anywhere, only filed.
|
quiet@bugs.debian.org will not be forwarded anywhere, only filed.
|
||||||
|
|
||||||
When you use different submission addresses, the bug tracking system
|
When you use different submission addresses, the bug tracking system
|
||||||
will set the Reply-To of any forwarded message so that the replies
|
will set the Reply-To of any forwarded message so that the replies will
|
||||||
will by default be processed in the same way as the original report.
|
by default be processed in the same way as the original report. That
|
||||||
That means that, for example, replies to maintonly will go to
|
means that, for example, replies to maintonly will go to
|
||||||
nnn-maintonly@bugs.debian.org instead of nnn@bugs.debian.org, unless
|
nnn-maintonly@bugs.debian.org instead of nnn@bugs.debian.org, unless of
|
||||||
of course one overrides this manually.
|
course one overrides this manually.
|
||||||
|
|
||||||
Acknowledgements
|
Acknowledgements
|
||||||
|
|
||||||
Normally, the bug tracking system will return an acknowledgement to
|
Normally, the bug tracking system will return an acknowledgement to you
|
||||||
you by e-mail when you report a new bug or submit additional
|
by e-mail when you report a new bug or submit additional information to
|
||||||
information to an existing bug. If you want to suppress this
|
an existing bug. If you want to suppress this acknowledgement, include
|
||||||
acknowledgement, include an X-Debbugs-No-Ack header in your e-mail
|
an X-Debbugs-No-Ack header or pseudoheader in your e-mail (the contents
|
||||||
(the contents of this header do not matter; however, it must be in the
|
of this header do not matter). If you report a new bug with this
|
||||||
mail header and not in the pseudo-header with the Package field). If
|
header, you will need to check the web interface yourself to find the
|
||||||
you report a new bug with this header, you will need to check the web
|
bug number.
|
||||||
interface yourself to find the bug number.
|
|
||||||
|
|
||||||
Note that this header will not suppress acknowledgements from the
|
Note that this header will not suppress acknowledgements from the
|
||||||
control@bugs.debian.org mailserver, since those acknowledgements may
|
control@bugs.debian.org mailserver, since those acknowledgements may
|
||||||
contain error messages which should be read and acted upon.
|
contain error messages which should be read and acted upon.
|
||||||
|
|
||||||
|
Spamfighting and missing mail
|
||||||
|
|
||||||
|
The bug tracking system implements a rather extensive set of rules
|
||||||
|
designed to make sure that spam does not make it through the BTS. While
|
||||||
|
we try to minimize the number of false positives, they do occur. If you
|
||||||
|
suspect your mail has triggered a false positive, feel free to contact
|
||||||
|
owner@bugs.debian.org for assistance. Another common cause of mail not
|
||||||
|
making it through to the BTS is utilizing addresses which match
|
||||||
|
procmail's FROM_DAEMON, which includes mail from addresses like
|
||||||
|
mail@foobar.com. If you suspect your mail matches FROM_DAEMON, see
|
||||||
|
procmailrc(5) to verify, and then resend the mail using an address
|
||||||
|
which does not match FROM_DAEMON.
|
||||||
|
|
||||||
Bug reports against unknown packages
|
Bug reports against unknown packages
|
||||||
|
|
||||||
If the bug tracking system doesn't know who the maintainer of the
|
If the bug tracking system doesn't know who the maintainer of the
|
||||||
relevant package is it will forward the report to debian-bugs-dist
|
relevant package is it will forward the report to debian-bugs-dist even
|
||||||
even if maintonly was used.
|
if maintonly was used.
|
||||||
|
|
||||||
When sending to maintonly@bugs.debian.org or
|
When sending to maintonly@bugs.debian.org or
|
||||||
nnn-maintonly@bugs.debian.org you should make sure that the bug report
|
nnn-maintonly@bugs.debian.org you should make sure that the bug report
|
||||||
is assigned to the right package, by putting a correct Package at the
|
is assigned to the right package, by putting a correct Package at the
|
||||||
top of an original submission of a report, or by using the
|
top of an original submission of a report, or by using the
|
||||||
control@bugs.debian.org service to (re)assign the report
|
control@bugs.debian.org service to (re)assign the report appropriately.
|
||||||
appropriately.
|
|
||||||
|
|
||||||
Using dpkg to find the package and version for the report
|
Using dpkg to find the package and version for the report
|
||||||
|
|
||||||
When using reportbug to report a bug in a command, say grep, the
|
When using reportbug to report a bug in a command, say grep, the
|
||||||
following will automatically select the right package and let you
|
following will automatically select the right package and let you write
|
||||||
write the report right away: reportbug --file $(which grep)
|
the report right away: reportbug --file $(which grep)
|
||||||
|
|
||||||
You can also find out which package installed it by using dpkg
|
You can also find out which package installed it by using dpkg
|
||||||
--search. You can find out which version of a package you have
|
--search. You can find out which version of a package you have
|
||||||
|
|
@ -349,14 +356,14 @@ Other useful commands and packages
|
||||||
provides a convenient text-based interface to the bug tracking system.
|
provides a convenient text-based interface to the bug tracking system.
|
||||||
|
|
||||||
Emacs users can also use the debian-bug command provided by the
|
Emacs users can also use the debian-bug command provided by the
|
||||||
debian-el package. When called with M-x debian-bug, it will ask for
|
debian-el package. When called with M-x debian-bug, it will ask for all
|
||||||
all necessary information in a similar way to reportbug.
|
necessary information in a similar way to reportbug.
|
||||||
_________________________________________________________________
|
__________________________________________________________________
|
||||||
|
|
||||||
Debian BTS administrators <owner@bugs.debian.org>
|
Debian BTS administrators <owner@bugs.debian.org>
|
||||||
|
|
||||||
Debian bug tracking system
|
Debian bug tracking system
|
||||||
Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
|
Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
|
||||||
1994-1997 Ian Jackson.
|
1994-1997 Ian Jackson.
|
||||||
_________________________________________________________________
|
__________________________________________________________________
|
||||||
|
|
||||||
|
|
|
||||||
File diff suppressed because it is too large
Load Diff
|
|
@ -57,7 +57,7 @@
|
||||||
|
|
||||||
<p id="breadcrumbs">
|
<p id="breadcrumbs">
|
||||||
<span class="alt">(<a href= "README.txt">Text version</a>)</span>
|
<span class="alt">(<a href= "README.txt">Text version</a>)</span>
|
||||||
Debian GNU/Linux 5.0.0 "Lenny" - Official i386 NETINST Binary-1 20090214-14:36
|
Debian GNU/Linux squeeze-di-rc2 "Squeeze" - Official Snapshot i386 NETINST Binary-1 20110121-20:12
|
||||||
</p>
|
</p>
|
||||||
</div><!-- end header -->
|
</div><!-- end header -->
|
||||||
|
|
||||||
|
|
@ -104,15 +104,12 @@
|
||||||
</h2>
|
</h2>
|
||||||
|
|
||||||
<p>This disc is labeled
|
<p>This disc is labeled
|
||||||
<small><strong>Debian GNU/Linux 5.0.0 "Lenny" - Official i386 NETINST Binary-1 20090214-14:36</strong></small>
|
<small><strong>Debian GNU/Linux squeeze-di-rc2 "Squeeze" - Official Snapshot i386 NETINST Binary-1 20110121-20:12</strong></small>
|
||||||
.
|
.
|
||||||
It contains programs ("binaries") for `i386' computers.</p>
|
It contains programs ("binaries") for `i386' computers.</p>
|
||||||
<p>This disc is a <em>netinst</em> image. It contains the installer and
|
<p>This disc is a <em>netinst</em> image. It contains the installer and
|
||||||
a very basic system. Any other packages you might want to install will
|
a very basic system. Any other packages you might want to install will
|
||||||
be downloaded from the network.</p>
|
be downloaded from the network.</p>
|
||||||
<p>The Release Notes for "lenny" are available on the
|
|
||||||
<a href="http://www.debian.org/releases/lenny/releasenotes">Debian web
|
|
||||||
site</a>.</p>
|
|
||||||
|
|
||||||
<h2 id="install">
|
<h2 id="install">
|
||||||
Installing
|
Installing
|
||||||
|
|
@ -122,9 +119,12 @@
|
||||||
installation procedure may seem a bit unusual. You can install
|
installation procedure may seem a bit unusual. You can install
|
||||||
Debian GNU/Linux either <em>alongside</em> your current OS, or as
|
Debian GNU/Linux either <em>alongside</em> your current OS, or as
|
||||||
the <em>only</em> OS on your computer.</p>
|
the <em>only</em> OS on your computer.</p>
|
||||||
<p>An <b>Installation Guide</b> for this disc is available from
|
<p>As this is not an official squeeze release disc, then the
|
||||||
<a href="http://www.debian.org/releases/lenny/installmanual">the
|
installation guide many not be released yet. It will appear on <a
|
||||||
Debian web site</a>.</p>
|
href="http://www.debian.org/releases/squeeze/installmanual">the
|
||||||
|
Debian web site</a> when ready, but before then you could try <a
|
||||||
|
href="http://d-i.alioth.debian.org/manual/">the development
|
||||||
|
version of the manual</a>.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<p>For the impatient ones: you can start the installation program easily by
|
<p>For the impatient ones: you can start the installation program easily by
|
||||||
|
|
@ -146,10 +146,9 @@
|
||||||
bugs may be present anywhere in the system. Please report any bugs you
|
bugs may be present anywhere in the system. Please report any bugs you
|
||||||
find in the Debian Bug Tracking System; details at <a
|
find in the Debian Bug Tracking System; details at <a
|
||||||
href="http://bugs.debian.org/">bugs.debian.org</a>.</li>
|
href="http://bugs.debian.org/">bugs.debian.org</a>.</li>
|
||||||
|
<li>If you're reporting bugs against this disc or the installation
|
||||||
<li>If you're reporting bugs against this disc or the installation
|
system, please also mention the version of this disc; this can be found
|
||||||
system, please also mention the version of this disc; this can be found
|
in the file <tt><a href=".disk/info">/.disk/info</a></tt>.</li>
|
||||||
in the file <tt><a href="/.disk/info">/.disk/info</a></tt>.</li>
|
|
||||||
|
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
|
|
|
||||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
|
|
@ -0,0 +1,11 @@
|
||||||
|
Creation of this disk image included extracting files from some Debian
|
||||||
|
packages. In case you do not have those packages already, both the
|
||||||
|
binary and source packages are archived at
|
||||||
|
|
||||||
|
http://cdimage.debian.org/cdimage/cd-sources/
|
||||||
|
|
||||||
|
The following binary/source packages were used:
|
||||||
|
syslinux-common_4.02+dfsg-7_all.deb
|
||||||
|
syslinux_4.02+dfsg-7.dsc
|
||||||
|
syslinux_4.02+dfsg-7.diff.gz
|
||||||
|
syslinux_4.02+dfsg.orig.tar.gz
|
||||||
|
|
@ -1,16 +1,15 @@
|
||||||
|
Debian GNU/Linux squeeze-di-rc2 "Squeeze" - Official Snapshot i386
|
||||||
|
NETINST Binary-1 20110121-20:12
|
||||||
|
|
||||||
Debian GNU/Linux 5.0.0 "Lenny" - Official i386 NETINST Binary-1
|
(HTML version in README.html)
|
||||||
20090214-14:36
|
|
||||||
|
|
||||||
(HTML version in README.html)
|
|
||||||
|
|
||||||
Welcome to the exciting world of
|
Welcome to the exciting world of
|
||||||
Debian GNU/Linux
|
Debian GNU/Linux
|
||||||
|
|
||||||
This disc contains the installer for the Debian GNU/Linux
|
This disc contains the installer for the Debian GNU/Linux distribution.
|
||||||
distribution. Debian is a very extensive collection of software. But
|
Debian is a very extensive collection of software. But it is more. It
|
||||||
it is more. It is a complete Operating System (OS) for your computer.
|
is a complete Operating System (OS) for your computer. And it is free
|
||||||
And it is free (as in "freedom").
|
(as in "freedom").
|
||||||
|
|
||||||
CONTENTS:
|
CONTENTS:
|
||||||
* Introduction
|
* Introduction
|
||||||
|
|
@ -48,8 +47,8 @@ About This Disc
|
||||||
|
|
||||||
This disc is labeled
|
This disc is labeled
|
||||||
|
|
||||||
Debian GNU/Linux 5.0.0 "Lenny" - Official i386 NETINST Binary-1
|
Debian GNU/Linux squeeze-di-rc2 "Squeeze" - Official Snapshot i386
|
||||||
20090214-14:36
|
NETINST Binary-1 20110121-20:12
|
||||||
|
|
||||||
It contains programs ("binaries") for `i386' computers.
|
It contains programs ("binaries") for `i386' computers.
|
||||||
|
|
||||||
|
|
@ -57,8 +56,6 @@ About This Disc
|
||||||
basic system. Any other packages you might want to install will be
|
basic system. Any other packages you might want to install will be
|
||||||
downloaded from the network.
|
downloaded from the network.
|
||||||
|
|
||||||
The Release Notes for "lenny" are available on the Debian web site.
|
|
||||||
|
|
||||||
Installing
|
Installing
|
||||||
==========
|
==========
|
||||||
|
|
||||||
|
|
@ -66,8 +63,10 @@ Installing
|
||||||
procedure may seem a bit unusual. You can install Debian GNU/Linux
|
procedure may seem a bit unusual. You can install Debian GNU/Linux
|
||||||
either alongside your current OS, or as the only OS on your computer.
|
either alongside your current OS, or as the only OS on your computer.
|
||||||
|
|
||||||
An Installation Guide for this disc is available from the Debian web
|
As this is not an official squeeze release disc, then the installation
|
||||||
site.
|
guide many not be released yet. It will appear on the Debian web site
|
||||||
|
when ready, but before then you could try the development version of
|
||||||
|
the manual.
|
||||||
|
|
||||||
For the impatient ones: you can start the installation program easily
|
For the impatient ones: you can start the installation program easily
|
||||||
by booting off this disc. Note that not all (esp. older) systems
|
by booting off this disc. Note that not all (esp. older) systems
|
||||||
|
|
@ -80,9 +79,9 @@ Last-Minute Notes
|
||||||
=================
|
=================
|
||||||
|
|
||||||
* You should keep in mind that this is a beta disc of the current
|
* You should keep in mind that this is a beta disc of the current
|
||||||
development version of the Debian system. This means that all
|
development version of the Debian system. This means that all sorts
|
||||||
sorts of bugs may be present anywhere in the system. Please report
|
of bugs may be present anywhere in the system. Please report any
|
||||||
any bugs you find in the Debian Bug Tracking System; details at
|
bugs you find in the Debian Bug Tracking System; details at
|
||||||
bugs.debian.org.
|
bugs.debian.org.
|
||||||
* If you're reporting bugs against this disc or the installation
|
* If you're reporting bugs against this disc or the installation
|
||||||
system, please also mention the version of this disc; this can be
|
system, please also mention the version of this disc; this can be
|
||||||
|
|
@ -140,5 +139,5 @@ More Information
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
See the Debian contact page (http://www.debian.org/contact) for
|
See the Debian contact page (http://www.debian.org/contact) for
|
||||||
information on contacting us.
|
information on contacting us.
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue