1
Introduction to the bug system request server
3
There is a mailserver which can send the bug reports and indices as
6
To use it you send a mail message to request@bugs.debian.org. The
7
Subject of the message is ignored, except for generating the Subject
10
The body you send should be a series of commands, one per line. You'll
11
receive a reply which looks like a transcript of your message being
12
interpreted, with a response to each command. No notifications are
13
sent to anyone for the commands listed here and the mail isn't logged
14
anywhere publicly available.
16
Any text on a line starting with a hash sign # is ignored; the server
17
will stop processing when it finds a line starting with quit, stop,
18
thank or two hyphens (to avoid parsing a signature). It will also stop
19
if it encounters too many unrecognised or badly-formatted commands. If
20
no commands are successfully handled it will send the help text for
27
Requests the transcript for the bug report in question.
28
send-detail sends all of the `boring' messages in the
29
transcript as well, such as the various auto-acks.
32
index-summary by-package
33
index-summary by-number
34
Request the full index (with full details, and including done
35
and forwarded reports), or the summary sorted by package or by
39
Requests the index page giving the list of maintainers with
40
bugs (open and recently-closed) in the tracking system.
42
index maint maintainer
43
Requests the index pages of bugs in the system for the
44
maintainer maintainer. The search term is an exact match. The
45
bug index will be sent in a separate message.
48
Requests the index page giving the list of packages with bugs
49
(open and recently-closed) in the tracking system.
51
index packages package
52
Requests the index pages of bugs in the system for the package
53
package. The search term is an exact match. The bug index will
54
be sent in a separate message.
56
send-unmatched [this|0]
57
send-unmatched last|-1
59
Requests logs of messages not matched to a particular bug
60
report, for this week, last week and the week before. (Each
61
week ends on a Wednesday.)
64
Request a file containing information about package(s) and or
65
maintainer(s) - the files available are:
68
The unified list of packages' maintainers, as used by the
69
tracking system. This is derived from information in the
70
Packages files, override files and pseudo-packages files.
73
override.distribution.non-free
74
override.distribution.contrib
76
Information about the priorities and sections of packages
77
and overriding values for the maintainers. This
78
information is used by the process which generates the
79
Packages files in the FTP archive. Information is
80
available for each of the main distribution trees
81
available, by their codewords.
83
pseudo-packages.description
84
pseudo-packages.maintainers
85
List of descriptions and maintainers respectively for
89
Requests that the mailservers' reference card be sent in plain
93
Requests that this help document be sent by email in plain
100
Stops processing at this point of the message. After this you
101
may include any text you like, and it will be ignored. You can
102
use this to include longer comments than are suitable for #,
103
for example for the benefit of human readers of your message
104
(reading it via the tracking system logs or due to a CC or
108
One-line comment. The # must be at the start of the line.
111
Sets the debugging level to level, which should be a
112
nonnegative integer. 0 is no debugging; 1 is usually
113
sufficient. The debugging output appears in the transcript. It
114
is not likely to be useful to general users of the bug system.
116
There is a reference card for the mailservers, available via the WWW,
117
in bug-mailserver-refcard.txt or by email using the refcard command
120
If you wish to manipulate bug reports you should use the
121
control@bugs.debian.org address, which understands a superset of the
122
commands listed above. This is described in another document,
123
available on the WWW, in the file bug-maint-mailcontrol.txt, or by
124
sending help to control@bugs.
126
In case you are reading this as a plain text file or via email: an
127
HTML version is available via the bug system main contents page
128
http://www.debian.org/Bugs/.
129
_________________________________________________________________
131
Debian BTS administrators <owner@bugs.debian.org>
133
Debian bug tracking system
134
Copyright � 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
135
1994-1997 Ian Jackson.
136
_________________________________________________________________