Initially, a bug report is submitted by a user as an ordinary mail
firstname.lastname@example.org. This will then be
given a number, acknowledged to the user, and forwarded to a mailing
list (if configured). If the submitter included a
line listing a package with a known maintainer the maintainer will get
a copy too.
Subject line will have
: added, and the
Reply-To will be set to include both the submitter of the
report and nnn
A developer who receives a bug from the tracking system, or sees it on
the mailing list, and takes responsibility for it should hit Reply in
their favourite mailreader,
and then edit the
To field to say
-email@example.com instead of
-close is provided as an alias for
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
Where applicable, please supply a
Version line in the
pseudo-header of your message when
closing a bug, so that the bug tracking system knows which releases of the
package contain the fix.
`Done' messages are automatically forwarded to the
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.
If a developer wishes to reply to a bug report they may simply reply
to the message (that will not mark the bug as done). Their reply will
(by default, if they respect the Reply-To: header) go to
@bugs.devuan.org, and to the original submitter of
the bug report (note: this is two distinct addresses). The bug tracking
system will receive the message at nnn
pass it on to the package maintainer, file the reply with the rest of the
logs for that bug report and forward it to a designated mailing list
A developer may explicitly mail the bug's submitter with an email to
If you wish to send a followup message which is not appropriate for
any mailing list you can do so by sending it to
Mail to nnn
-firstname.lastname@example.org is filed in the
bug Tracking System but is not delivered to any individuals or mailing
lists. Mail to nnn
filed in the bug Tracking System and is delivered only to the maintainer
of the package in question.
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, see that you don't send followup messages
both to nnn
@bugs.devuan.org and to
email@example.com, because the bug system will then
get two copies of it and each one will be forwarded to the designated
mailing list separately.
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
Severity line in the pseudo-header when
the bug is submitted (see the
instructions for reporting bugs),
or by using the
severity command with the
control request server.
Separate multiple tags with commas, spaces, or both.
The severity levels are:
Each bug can have zero or more of a set of given tags. These tags are displayed in the list of bugs when you look at a package's page, and when you look at the full bug log.
The current bug tags are:
When a developer forwards a bug report to the developer of the upstream source package from which the Devuan package is derived, they should note this in the bug tracking system as follows:
Make sure that the
To field of your message to the author
has only the author(s) address(es) in it; put both the person who
reported the bug,
@bugs.devuan.org in the
Ask the author to preserve the
@bugs.devuan.org when they reply, so
that the bug tracking system will file their reply with the original
report. These messages are only filed and are not sent on; to send a
message as normal, send them
@bugs.devuan.org as well.
When the bug tracking system gets a message at
-forwarded it will mark the relevant bug as
having been forwarded to the address(es) in the
of the message it gets, if the bug is not already marked as forwarded.
You can also manipulate the `forwarded to' information by sending
In cases where the person responsible for fixing a bug is not the assigned maintainer for the associated package (for example, when the package is maintained by a team), it may be useful to record this fact in the bug tracking system. To help with this, each bug may optionally have an owner.
The owner can be set by supplying an
Owner line in the
pseudo-header when the bug is submitted (see the
instructions for reporting
or by using the
with the control request server.
Every Friday, a list of outstanding bug reports is posted to a summary mailing list (if set up), sorted by age of report. Every Tuesday, a list of bug reports that have gone unanswered too long is posted, sorted by package maintainer.
It is possible to reassign bug reports to other packages, to reopen
erroneously-closed ones, to modify the information saying to where, if
anywhere, a bug report has been forwarded, to change the severities
and titles of reports, to set the ownership of bugs, to merge and unmerge
bug reports, and to record the versions of packages in which bugs were
found and in which they were fixed. This is done by sending mail to
The format of these messages is
described in another document available on the World Wide Web or in
bug-maint-mailcontrol.txt. A plain text version
can also be obtained by mailing the word
help to the
server at the address above.
Messages that arrive at
Bug#nnn will be treated as
having been sent to nnn
@bugs.devuan.org. This is both
for backwards compatibility with mail forwarded from the old
addresses, and to catch followup mail sent to
mistake (for example, by using reply to all recipients).
A similar scheme operates for
which treat mail arriving with a Subject tag as having been sent to
the corresponding nnn-whatever
Messages arriving at plain
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.