submit@bugs.linux-mandrake.com. This will then be
given a number, acknowledged to the user, and forwarded to a mailing
list (if configured). If the submitter included a Package
line listing a package with a known maintainer the maintainer will get
a copy too.
The Subject line will have
bug#nnn: added, and the
Reply-To will be set to include both the submitter of the
report and nnn@bugs.linux-mandrake.com.
To field to say
nnn-done@bugs.linux-mandrake.com instead of
nnn@bugs.linux-mandrake.com
(nnn-close is provided as an alias for
nnn-done).
The address of the original submitter of the bug report will be
included in the default To field, because the bug system
included it in the Reply-To.
`Done' messages are forwarded to a mailing list if the mailing list has been set up.
The person closing the bug and the person who submitted it will each get a notification about the change in status of the report.
@bugs.linux-mandrake.com and to the original
submitter of the bug report. The bug tracking system will file the
reply with the rest of the logs for that bug report and forward it to
a designated mailing list. The bug will not be marked as done.
If you wish to send a followup message which is not appropriate for
any mailing list you can do so by sending it to
nnn-quiet@bugs.linux-mandrake.com or
nnn-maintonly@bugs.linux-mandrake.com, which only file it (not
forwarding it anywhere) and send it on only to the maintainer of the
package in question, respectively.
Do not use the `reply to all recipients' or `followup'
feature of your mailer unless you intend to edit down the recipients
substantially. In particular, don't send a followup message both to
nnn@bugs.linux-mandrake.com and to
submit@bugs.linux-mandrake.com, because the bug system will then
get two copies of it and each one will be forwarded to the designated
mailing list separately.
normal by default, but can be overridden either by
supplying a Severity line in the psuedo-header when the
bug is submitted (see the
instructions for reporting
bugs), or by using the severity command with the
control request server.
The severity levels are:
critical
grave
normal
wishlist
Make sure that the To field of your message to the author
to has only the author(s) address(es) in it; put both the person who
reported the bug and
nnn-forwarded@bugs.linux-mandrake.com in the
CC field.
Ask the author to preserve the CC to
nnn-forwarded@bugs.linux-mandrake.com when they reply, so that
the bug tracking system will file their reply with the original
report.
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 the To field
of the message it gets.
You can also manipulate the `forwarded to' information by sending messages to
control@bugs.linux-mandrake.com.
control@bugs.linux-mandrake.com.
The format of these messages is
described in another document available on the World Wide Web or in
the file bug-maint-mailcontrol.txt. A plain text version
can also be obtained by mailing the word help to the
server at the address above.
submit or bugs whose
Subject starts Bug#nnn will be treated as
having been sent to nnn@bugs.linux-mandrake.com. This is both
for backwards compatibility with mail forwarded from the old
addresses, and to catch followup mail sent to submit by
mistake (for example, by using reply to all recipients).
A similar scheme operates for maintonly,
done, quiet and forwarded,
which treat mail arriving with a Subject tag as having been sent to
the corresponding nnn-whatever@bugs.linux-mandrake.com address.
Messages arriving at plain forwarded and
done - ie, with no bug report number in the address - and
without a bug number in the Subject will be filed under `junk' and
kept for a few weeks, but otherwise ignored.
Package: secondary header field may
become mandatory - at the moment omitting it just produces a warning
message.
Debian bug tracking system
copyright 1997 nCipher Corporation Ltd,
copyright 1994-1997 Ian Jackson,
copyright 1995 Steven Brenner.
Available under the GPL.