From: joy <> Date: Sun, 8 Oct 2000 22:11:45 +0000 (-0800) Subject: [project @ 2000-10-08 15:11:45 by joy] X-Git-Tag: release/2.6.0~1220 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=92f20f5069013354e5e42d498e1332cd2a44b554;p=debbugs.git [project @ 2000-10-08 15:11:45 by joy] synced with docs on www.d.o/Bugs; fixed all HTML issues (nsgmls, tidy and weblint :); various fixes --- diff --git a/html/Access.html.in b/html/Access.html.in index aa28c60e..ec1b747d 100644 --- a/html/Access.html.in +++ b/html/Access.html.in @@ -1,40 +1,38 @@ $gAccessHtml = < - - $gProject $gBugs - Accessing the logs - - - - -

Accessing $gBug reports in the tracking system logs

- - -Each message received at or sent by the $gBug processing system is + + + + $gProject $gBugs - Accessing the logs + + + + +

Accessing $gBug reports in the tracking system +logs

+ +

Each message received at or sent by the $gBug processing system is logged and made available in a number of ways. -

$gHTMLCopies -There is a mailserver which can send +

There is a mailserver which can send $gBug reports as plain text on request. To use it send the word -help as the sole contents of an email to -request (the Subject of the +help as the sole contents of an email to +request (the Subject of the message is ignored), or read the instructions on the World Wide Web or -in the file bug-log-mailserver.txt. - -

- -Other pages: -

$gBug tracking system main contents page. -
Instructions for reporting $gBugs. -
Developers' information regarding the $gBug processing system. -
Full list of outstanding and recent $gBug reports. -
Packages with $gBug reports. -

Maintainers of packages with $gBug reports. - +in the file bug-log-mailserver.txt. + +

+ +

Other pages: +

$gHTMLTail diff --git a/html/Developer.html.in b/html/Developer.html.in index bb3f184c..32629278 100644 --- a/html/Developer.html.in +++ b/html/Developer.html.in @@ -1,29 +1,29 @@ $gDeveloperHtml = < - - $gProject - Developers' information - + + + + $gProject - Developers' information + -

Developers' information regarding the $gBug processing system

-Initially, a $gBug report is submitted by a user as an ordinary mail +

Developers' information regarding the $gBug processing system

+ +

Initially, a $gBug report is submitted by a user as an ordinary mail message to submit\@$gEmailDomain. 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 +

The Subject line will have $gBug#nnn: added, and the Reply-To will be set to include both the submitter of the report and nnn\@$gEmailDomain. -

Closing $gBug reports

-A developer who receives a $gBug from the tracking system, or sees it on +

A developer who receives a $gBug 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 @@ -31,161 +31,147 @@ and then edit the To field to say nnn\@$gEmailDomain (nnn-close is provided as an alias for nnn-done). -

-The address of the original submitter of the $gBug report will be +

The address of the original submitter of the $gBug report will be included in the default To field, because the $gBug system included it in the Reply-To. -

-`Done' messages are forwarded to a mailing list if the mailing list has been -set up. -

`Done' messages are automatically forwarded to the $gDoneList +mailing list, if the mailing list has been set up. -The person closing the $gBug and the person who submitted it will each +

The person closing the $gBug and the person who submitted it will each get a notification about the change in status of the report.

Followup messages

-If a developer wishes to reply to a $gBug report without marking the $gBug -as done they may simply reply to the message. Their reply will (by -default) go to nnn\@$gEmailDomain and to the original -submitter of the $gBug report. The $gBug tracking system will file the -reply with the rest of the logs for that $gBug report and forward it to -a designated mailing list. The $gBug will not be marked as done. -

If a developer wishes to reply to a $gBug 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 +nnn\@$gEmailDomain, and to the original submitter of +the $gBug report (note: this is two distinct addresses). The $gBug tracking +system will receive the message at nnn\@$gEmailDomain, +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 +($gSubmitList\@$gEmailDomain). + +

A developer may explicitly mail the bug's submitter with an email to +nnn-submitter\@$gEmailDomain. -If you wish to send a followup message which is not appropriate for +

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\@$gEmailDomain or -nnn-maintonly\@$gEmailDomain, 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' +nnn-maintonly\@$gEmailDomain. +Mail to nnn-quiet\@$gEmailDomain is filed in the +$gBug Tracking System but is not delivered to any individuals or mailing +lists. Mail to nnn-maintonly\@$gEmailDomain is +filed in the $gBug 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, don't send a followup message both to -nnn\@$gEmailDomain and to +substantially. In particular, see that you don't send followup messages +both to nnn\@$gEmailDomain and to submit\@$gEmailDomain, because the $gBug system will then get two copies of it and each one will be forwarded to the designated mailing list separately. -

- -

Severity levels

-The $gBug system records a severity level with each $gBug report. This is -set to $gDefaultSeverity by default, but can be overridden either by -supplying a Severity line in the pseudo-header when the -$gBug is submitted (see the -instructions for reporting -$gBugs), or by using the severity command with the -control request server. +

Severity levels

The $gBug system records a severity level with each $gBug report. This +is set to $gDefaultSeverity by default, but can be overridden +either by supplying a Severity line in the pseudo-header when +the $gBug is submitted (see the +instructions for reporting $gBugs), +or by using the severity command with the +control request server. -The severity levels are: +

The severity levels are:

$gHTMLSeverityDesc -

Recording that you have passed on a $gBug report

-When a developer forwards a $gBug report to the developer of the +

When a developer forwards a $gBug report to the developer of the upstream source package from which the $gProject package is derived, they should note this in the $gBug tracking system as follows: -

-Make sure that the To field of your message to the author +

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 $gBug and nnn-forwarded\@$gEmailDomain in the CC field. -

-Ask the author to preserve the CC to +

Ask the author to preserve the CC to nnn-forwarded\@$gEmailDomain when they reply, so that the $gBug tracking system will file their reply with the original report. -

-When the $gBug tracking system gets a message at +

When the $gBug tracking system gets a message at nnn-forwarded it will mark the relevant $gBug 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\@$gEmailDomain. +

You can also manipulate the `forwarded to' information by sending +messages to control\@$gEmailDomain.

Summary postings

-Every Friday, a list of outstanding $gBug reports is posted to a summary mailing -list (if set up), sorted by age of report. -Every Tuesday, a list of $gBug reports that have gone unanswered too long is -posted, sorted by package maintainer. -

Every Friday, a list of outstanding $gBug reports is posted to a summary +mailing list (if set up), sorted by age of report. Every Tuesday, a list of +$gBug reports that have gone unanswered too long is posted, sorted by +package maintainer. $gBadMaintHtml -

Reopening, reassigning and manipulating $gBugs

-It is possible to reassign $gBug reports to other packages, to reopen +

It is possible to reassign $gBug reports to other packages, to reopen erroneously-closed ones, to modify the information saying to where, if anywhere, a $gBug report has been forwarded, to change the severities and titles of reports and to merge and unmerge $gBug reports. This is done by sending mail to control\@$gEmailDomain. -

-The format of these messages is +

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.

More-or-less obsolete subject-scanning feature

-(this is likely to be removed the next version)
-Messages that arrive at submit or $gBugs whose + + + +

Messages that arrive at submit or $gBugs whose Subject starts Bug#nnn will be treated as having been sent to nnn\@$gEmailDomain. 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, +

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\@$gEmailDomain address. -

- -Messages arriving at plain forwarded and +

Messages arriving at plain forwarded and done - ie, with no $gBug report number in the address - and without a $gBug number in the Subject will be filed under `junk' and kept for a few weeks, but otherwise ignored. -

Future plans

- -At some point the Package: secondary header field may -become mandatory - at the moment omitting it just produces a warning -message. -

-Other pages: -

$gBug tracking system main contents page. -
Instructions for reporting $gBugs. -
Accessing the $gBug tracking logs other than by WWW. -
Mailservers' reference card. -
Full list of outstanding and recent $gBug reports. -
Packages with $gBug reports. -

Maintainers of packages with $gBug reports. +

Other pages: +

$gHTMLTail diff --git a/html/Reporting.html.in b/html/Reporting.html.in index 50d216e8..39f962f9 100644 --- a/html/Reporting.html.in +++ b/html/Reporting.html.in @@ -1,27 +1,29 @@ $gReportingHtml = <$gProject $gBugs - how to report a $gBug - - + + + + $gProject $gBugs - how to report a $gBug + + + +

How to report a $gBug in $gProject

-Send mail to -submit\@$gEmailDomain, +

Send mail to +submit\@$gEmailDomain, as described below. -

-Please don't report several unrelated $gBugs - especially ones in +

Please don't report several unrelated $gBugs - especially ones in different packages - in one message. Also, please don't mail your $gBug report to any mailing lists or recipients other than submit\@$gEmailDomain (for details of how to do this right, see -below). -

+below). -Lists of currently-outstanding $gBugs are available on -the World Wide Web and elsewhere - see +

Lists of currently-outstanding $gBugs are available on +the World Wide Web and elsewhere - see other documents for details. -

-You should put a pseudo-header at the start of the body of the +

You need to put a pseudo-header at the start of the body of the message, with the Package: and Version: lines giving the name and version of the package which has the $gBug. (The pseudo-header fields should start at the very start of their lines. @@ -30,20 +32,19 @@ and may fail to recognise the pseudo-headers in such mail.) $gHTMLFindPackage -See below for further requirements. -

See below for further requirements. $gHTMLPseudoDesc -

Example

-A $gBug report, with mail header, looks something like this: +

A $gBug report, with mail header, looks something like this:

   To: submit\@$gEmailDomain
   From: diligent\@testing.linux.org
   Subject: Hello says `goodbye'
-Package: hello
-  Version: 1.3-2
+  Package: hello
+  Version: 1.3-16
 
   When I invoke `hello' without arguments from an ordinary shell
   prompt it prints `goodbye', rather than the expected `hello, world'.
@@ -57,132 +58,124 @@ A $gBug report, with mail header, looks something like this:
 
   I suggest that the output string, in hello.c, be corrected.
 
-  I am using Debian 1.1, kernel version 1.3.99.15z
-  and libc 5.2.18.3.2.1.3-beta.
+  I am using Debian GNU/Linux 2.2, kernel 2.2.17-pre-patch-13
+  and libc6 2.1.3-10.

Please include in your report:

The exact and complete text of any error -messages printed or logged. This is very important! -
Exactly what you typed or did to demonstrate the problem. -
A description of the incorrect behaviour: exactly what behaviour -you were expecting, and what you observed. A transcript of an -example session is a good way of showing this. -
A suggested fix, or even a patch, if you have one. -
Details of the configuration of the program with the problem. -Include the complete text of its configuration files. +
The exact and complete text of any error + messages printed or logged. This is very important! +
Exactly what you typed or did to demonstrate the problem. +
A description of the incorrect behaviour: exactly what behaviour + you were expecting, and what you observed. A transcript of an + example session is a good way of showing this. +
A suggested fix, or even a patch, if you have one. +
Details of the configuration of the program with the problem. + Include the complete text of its configuration files. + $gXtraBugInfo +

-Include any detail that seems relevant - you are in very little danger +

Include any detail that seems relevant - you are in very little danger of making your report too long by including too much information. If they are small please include in your report any files you were using to reproduce the problem (uuencoding them if they may contain odd characters etc.). -

- -Of course, like any email, you should include a clear, descriptive +

Of course, like any email, you should include a clear, descriptive Subject line in your main mail header. The subject you give will be used as the initial $gBug title in the tracking system, so -please try to make it informative ! +please try to make it informative! -

Sending copies of $gBug reports to other addresses

-Sometimes it is necessary to send a copy of a $gBug report to somewhere +

Sometimes it is necessary to send a copy of a $gBug report to somewhere else besides the mailing list and the package maintainer, which is where they are normally sent. -

-You could do this by CC'ing your $gBug report to the other address(es), +

You could do this by CC'ing your $gBug report to the other address(es), but then the other copies would not have the $gBug report number put in the Reply-To field and the Subject line. When the recipients reply they will probably preserve the submit\@$gEmailDomain entry in the header and have their message filed as a new $gBug report. This leads to many duplicated reports. -

-The right way to do this is to use the -X-$gProject-CC header. Add a line like this to your -message's mail header (not to the pseudo header with the -Package field): +

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 (not +to the pseudo header with the Package field):

- X-$gProject-CC: other-list\@cosmic.edu
+  X-Debbugs-CC: other-list\@cosmic.edu

This will cause the $gBug tracking system to send a copy of your report -to the address(es) in the X-$gProject-CC line as well as to +to the address(es) in the X-Debbugs-CC line as well as to any mailing list. -

-This feature can often be combined usefully with mailing +

This feature can often be combined usefully with mailing quiet - see below. -

Severity levels

-If a report is of a particularly serious $gBug, or is merely a feature +

If a report is of a particularly serious $gBug, or is merely a feature request that, you can set the severity level of the $gBug as you report it. This is not required, however, and the developers will assign an appropriate severity level to your report if you do not. -

-To assign a severity level put a +

To assign a severity level put a Severity: severity line in the pseudo-header, together with Package and Version. The severity levels available are described in the -developers' documentation. +developers' documentation.

Not forwarding to the mailing list - minor $gBug reports

-If a $gBug report is minor (for example, a documentation typo or other +

If a $gBug report is minor (for example, a documentation typo or other trivial build problem), or you're submitting many reports at once, -send them to maintonly\@$gEmailDomain or quiet\@$gEmailDomain. +send them to maintonly\@$gEmailDomain or +quiet\@$gEmailDomain. maintonly will send the report on to the package maintainer (provided you supply a correct Package line in the pseudo-header and the maintainer is known), and quiet will not forward it anywhere at all but only file it as a $gBug (useful if, for example, you are submitting many similar $gBugs and want to post only a summary). -

-If you do this the $gBug system will set the Reply-To of +

If you do this the $gBug system will set the Reply-To of any forwarded message so that replies will by default be processed in the same way as the original report. -

Unknown packages or $gBugs with no `Package` key

$gBug reports against unknown packages

-If the $gBug tracking system doesn't know who the maintainer of the +

If the $gBug tracking system doesn't know who the maintainer of the relevant package is it'll forward the report to the mailing list even if maintonly was used. -

-When sending to maintonly\@$gEmailDomain or +

When sending to maintonly\@$gEmailDomain or nnn-maintonly\@$gEmailDomain you should make sure that the $gBug report 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 -control\@$gEmailDomain service to (re)assign the report +or by using the +control\@$gEmailDomain service to (re)assign the report appropriately first if it isn't correct already. $gXtraReportingInfo

-Other pages: -

Bug tracking system main contents page. -
Developers' -information regarding the $gBug processing system. -
Accessing the $gBug tracking logs other than by WWW. -
Full list of outstanding and recent $gBug reports. -
Packages with $gBug reports. -

Maintainers of packages with $gBug reports. +

Other pages: +

$gHTMLTail diff --git a/html/index.html.in b/html/index.html.in index 6b80adbf..67de15d6 100644 --- a/html/index.html.in +++ b/html/index.html.in @@ -1,102 +1,137 @@ $gIndexHtml = < -$gProject $gBug tracking system - - + + + + $gProject $gBug tracking system + + + +

$gProject $gBug tracking system main contents page

-$gProjectTitle has a $gBug tracking system which files -details of $gBugs reported by users and developers. Each $gBug is given a -number, and is kept on file until it is marked as having been dealt -with. +

$gProjectTitle has a $gBug tracking system which files details of $gBugs +reported by users and developers. Each $gBug is given a number, and is kept +on file until it is marked as having been dealt with. $gHTMLCopies

Documentation about the $gBug tracking system

Reviewing $gBug reports on the WWW

Full list of outstanding and recent $gBug reports. -
Index of packages with $gBug reports. -
Index of maintainers of packages with $gBug reports. -
Outstanding -critical, -grave, -normal and -fixed $gBugs and -wishlist items. -
Forwarded -critical, -grave, -normal and -fixed $gBugs and -wishlist items. -
Resolved -critical, -grave, -normal and -fixed $gBugs and -wishlist items. -
Summary of outstanding reports, sorted by package. -
Summary of outstanding reports, sorted by number. -
Logs not associated with a particular $gBug report. -
Time stamp page (for checking that mirror is current). +
Full list of outstanding and recent $gBug reports. +
Index of packages with $gBug reports. +
Index of maintainers of packages with $gBug reports. +
Outstanding + critical, + grave, + normal and + fixed $gBugs and + wishlist items. +
Forwarded + critical, + grave, + normal and + fixed $gBugs and + wishlist items. +
Resolved + critical, + grave, + normal and + fixed $gBugs and + wishlist items. +
Summary of outstanding reports, sorted by package. +
Summary of outstanding reports, sorted by number. +
Logs not associated with a particular $gBug report. +
Time stamp page (for checking that mirror is current).

-Each closed $gBug report is expired from these logs $gRemoveAge days after the -last message relating to it is received and filed. - -

Find a $gBug report by reference number

- - -`Not found' means that the $gBug was closed and expired or -never existed, or that this mirror has not yet recorded that $gBug - see -also the timestamp page. - -

Find a $gBug report by package

- - -`Not found' means that that package does not exist or does not have -any outstanding or recently closed $gBug reports. - -

Find an archived bug report by reference number

- -

Find an archived bug report by package

- -or get a list of -packages +

Each closed $gBug report is expired from these logs $gRemoveAge +days after the last message relating to it is received and filed. +You can search the bug report archive through the forms below. + +

Find $gBug reports

+ + + + + + + + + + + + +

+ + + By number: + + + + + + +	+ + + By package: + + + + + + + active bugs + archived bugs + + + +
+ + + By maintainer e-mail: + + + + + + + active bugs + archived bugs + + + +	+ + + By submitter e-mail: + + + + + + + active bugs + archived bugs + + + +

$gHTMLOtherPages $gHTMLTail HTML_END - diff --git a/html/server-control.html.in b/html/server-control.html.in index 5ba35c65..69fb0661 100644 --- a/html/server-control.html.in +++ b/html/server-control.html.in @@ -1,34 +1,33 @@ $gControlHtml = < - -$gProject $gBug system - control mail server commands - - + + + + $gProject $gBug system - control mail server commands + + + +

Introduction to the $gBug control and manipulation mailserver

-In addition to the mailserver on request\@$gEmailDomain +

In addition to the mailserver on request\@$gEmailDomain which allows the retrieval of $gBug data and documentation by email, there is another server on control\@$gEmailDomain which also allows $gBug reports to 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 addresses are only separated to avoid users making mistakes and causing problems while merely trying to request information. -

-Please see the -introduction to -the request server -available on the World Wide Web, in the file +

Please see the +introduction to the request +server available on the World Wide Web, in the file bug-maint-mailcontrol.txt, or by sending help to either mailserver, for details of the basics of operating the mailservers and the common commands available when mailing either address. -

-The reference card for the +

The reference card for the mailservers is available via the WWW, in bug-mailserver-refcard.txt or by email using the refcard command). @@ -38,163 +37,140 @@ mailservers is available via the WWW, in

close bugnumber -

-Close $gBug report #bugnumber. -

Close $gBug report #bugnumber. -A notification is sent to the user who reported the $gBug, but (in -contrast to mailing bugnumber-done@$gEmailDomain) the -text of the mail which caused the $gBug to be closed is not -included in that notification. The maintainer who closes a report -should ensure, probably by sending a separate message, that the user -who reported the $gBug knows why it is being closed. +

A notification is sent to the user who reported the $gBug, but (in + contrast to mailing bugnumber-done@$gEmailDomain) the + text of the mail which caused the $gBug to be closed is not + included in that notification. The maintainer who closes a report + should ensure, probably by sending a separate message, that the user + who reported the $gBug knows why it is being closed.

reassign bugnumber package -

-Records that $gBug #$gBugnumber is a $gBug in package. -This can be used to set the package if the user forgot the -pseudo-header, or to change an earlier assignment. No notifications -are sent to anyone (other than the usual information in the processing -transcript). +

Records that $gBug #${gBug}number is a $gBug in package. + This can be used to set the package if the user forgot the + pseudo-header, or to change an earlier assignment. No notifications + are sent to anyone (other than the usual information in the processing + transcript).

reopen bugnumber [ originator-address | = | ! ] -

- -Reopens #bugnumber if it is closed. -

- -By default, or if you specify =, the original submitter is -still as the originator of the report, so that they will get the ack -when it is closed again. -

- -If you supply an originator-address the originator will be -set to the address you supply. If you wish to become the new -originator of the reopened report you can use the ! -shorthand or specify your own email address. -

- -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 that -they will know to expect the ack which they'll get when it is closed -again. -

- -If the $gBug is not closed then reopen won't do anything, not even -change the originator. There is no way to change the originator of an -open $gBug report (this is deliberate, so that you can't have a $gBug be -closed and then deleted $gRemoveAge days later without someone being told about -it). + +

Reopens #bugnumber if it is closed. + +

By default, or if you specify =, the original submitter is + still as the originator of the report, so that they will get the ack + when it is closed again. + +

If you supply an originator-address the originator will be + set to the address you supply. If you wish to become the new + originator of the reopened report you can use the ! + shorthand or specify your own email address. + +

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 that + they will know to expect the ack which they'll get when it is closed + again. + +

If the $gBug is not closed then reopen won't do anything, not even + change the originator. There is no way to change the originator of an + open $gBug report (this is deliberate, so that you can't have a $gBug be + closed and then deleted $gRemoveAge days later without someone being told about + it).

forwarded bugnumber address -

-Notes that bugnumber has been forwarded to the upstream -maintainer at address. This does not actually forward the -report. This can be used to change an existing incorrect forwarded-to -address, or to record a new one for a $gBug that wasn't previously noted -as having been forwarded. +

Notes that bugnumber has been forwarded to the upstream + maintainer at address. This does not actually forward the + report. This can be used to change an existing incorrect forwarded-to + address, or to record a new one for a $gBug that wasn't previously noted + as having been forwarded.

notforwarded bugnumber -

-Forgets any idea that bugnumber has been forwarded to any -upstream maintainer. If the $gBug was not recorded as having been -forwarded then this will do nothing. +

Forgets any idea that bugnumber has been forwarded to any + upstream maintainer. If the $gBug was not recorded as having been + forwarded then this will do nothing.

retitle bugnumber new-title -

-Changes the title of a $gBug report to that specified (the default is -the Subject mail header from the original report. -

Changes the title of a $gBug report to that specified (the default is + the Subject mail header from the original report. -Unlike most of the other $gBug-manipulation commands when used on one of -a set of merged reports this will change the title of only the -individual $gBug requested, and not all those with which it is merged. +

Unlike most of the other $gBug-manipulation commands when used on one of + a set of merged reports this will change the title of only the + individual $gBug requested, and not all those with which it is merged.

severity bugnumber severity -

-Set the severity level for $gBug report #bugnumber to -severity. No notification is sent to the user who reported -the $gBug. -

Set the severity level for $gBug report #bugnumber to + severity. No notification is sent to the user who reported + the $gBug. -For their meanings please -consult the general developers' documentation for the $gBug system. +

For their meanings please + consult the general developers' documentation for the $gBug system.

merge bugnumber bugnumber ... -

- -Merges two or more $gBug reports. When reports are merged opening, -closing, marking or unmarking as forwarded and reassigning any of the -$gBugs to a new package will have an identical effect on all of the -merged reports. -

- -Before $gBugs can be merged they must be in exactly the same state: -either all open or all closed, with the same forwarded-to upstream -author address or all not marked as forwarded, and all assigned to the -same package or package(s) (an exact string comparison is done on the -package to which the $gBug is assigned). If they don't start out in the -same state you should use reassign, reopen -and so forth to make sure that they are before using -merge. -

- -If any of the $gBugs listed in a merge command is already -merged with another $gBug then all the reports merged with any of the -ones listed will all be merged together. Merger is like equality: it -is reflexive, transitive and symmetric. -

- -Merging reports causes a note to appear on each report's logs; on the -WWW pages this is includes links to the other $gBugs. -

- -Merged reports are all expired simultaneously, and only when all of -the reports each separately meet the criteria for expiry. + +

Merges two or more $gBug reports. When reports are merged opening, + closing, marking or unmarking as forwarded and reassigning any of the + $gBugs to a new package will have an identical effect on all of the + merged reports. + +

Before $gBugs can be merged they must be in exactly the same state: + either all open or all closed, with the same forwarded-to upstream + author address or all not marked as forwarded, and all assigned to the + same package or package(s) (an exact string comparison is done on the + package to which the $gBug is assigned). If they don't start out in the + same state you should use reassign, reopen + and so forth to make sure that they are before using + merge. + +

If any of the $gBugs listed in a merge command is already + merged with another $gBug then all the reports merged with any of the + ones listed will all be merged together. Merger is like equality: it + is reflexive, transitive and symmetric. + +

Merging reports causes a note to appear on each report's logs; on the + WWW pages this is includes links to the other $gBugs. + +

Merged reports are all expired simultaneously, and only when all of + the reports each separately meet the criteria for expiry.

unmerge bugnumber -

-Disconnects a $gBug report from any other reports with which it may have -been merged. If the report listed is merged with several others then -they are all left merged with each other; only their associations with -the $gBug explicitly named are removed. -

Disconnects a $gBug report from any other reports with which it may have + been merged. If the report listed is merged with several others then + they are all left merged with each other; only their associations with + the $gBug explicitly named are removed. -If many $gBug reports are merged and you wish to split them into two -separate groups of merged reports you must unmerge each report in one -of the new groups separately and then merge them into the required new -group. -

If many $gBug reports are merged and you wish to split them into two + separate groups of merged reports you must unmerge each report in one + of the new groups separately and then merge them into the required new + group. -You can only unmerge one report with each unmerge -command; if you want to disconnect more than one $gBug simply include -several unmerge commands in your message. +

You can only unmerge one report with each unmerge + command; if you want to disconnect more than one $gBug simply include + several unmerge commands in your message.

-Other pages: + +

Other pages:

$gHTMLTail diff --git a/html/server-refcard.html.in b/html/server-refcard.html.in index 892e2e6d..4cb3e4eb 100644 --- a/html/server-refcard.html.in +++ b/html/server-refcard.html.in @@ -1,87 +1,93 @@ $gRefcardHtml = < -$gProject $gBug system - mail servers' reference card - - + + + + $gProject $gBug system - mail servers' reference card + + + +

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 +bug-log-mailserver.txt and +bug-maint-mailcontrol.txt or by sending the word help to each mailserver.

Synopsis of commands available at `request@$gEmailDomain`

send bugnumber -
send-detail bugnumber -
index [full] -
index-summary by-package -
index-summary by-number -
index-maint -
index maint maintainer-substring -
index-packages -
index packages package-substring -
send-unmatched [this|0] -
send-unmatched last|-1 -
send-unmatched old|-2 -
getinfo filename (see below) -
help -
refcard -
quit|stop|thank...|--... -
#... (comment) -
debug level +
send bugnumber +
send-detail bugnumber +
index [full] +
index-summary by-package +
index-summary by-number +
index-maint +
index maint maintainer-substring +
index-packages +
index packages package-substring +
send-unmatched [this|0] +
send-unmatched last|-1 +
send-unmatched old|-2 +
getinfo filename (see below) +
help +
refcard +
quit|stop|thank...|--... +
#... (comment) +
debug level

List of info files for `getinfo`

maintainers -
override.stable -
override.development -
override.contrib -
override.non-free -
override.experimental -
override.codeword -
pseudo-packages.description -
pseudo-packages.maintainers +
maintainers +
override.stable +
override.development +
override.contrib +
override.non-free +
override.experimental +
override.codeword +
pseudo-packages.description +
pseudo-packages.maintainers

Synopsis of extra commands available at control mailserver

close bugnumber - (you must separately tell originator why) -
reassign bugnumber package -
severity bugnumber severity -
reopen bugnumber - [ originator-address | = | ! ] -
forwarded bugnumber address -
notforwarded bugnumber -
retitle bugnumber new-title -
merge bugnumber bugnumber ... -
unmerge bugnumber +
close bugnumber + (you must separately tell originator why) +
reassign bugnumber package +
severity bugnumber severity +
reopen bugnumber + [ originator-address | = | ! ] +
forwarded bugnumber address +
notforwarded bugnumber +
retitle bugnumber new-title +
merge bugnumber bugnumber ... +
unmerge bugnumber

-reopen with = or no originator address leaves + +

reopen with = or no originator address leaves the originator as the original submitter; ! sets it to you, the person doing the reopen. -

$gHTMLSeverityDesc +

-Other pages: + +

Other pages:

diff --git a/html/server-request.html.in b/html/server-request.html.in index 7136cb38..9f4e023f 100644 --- a/html/server-request.html.in +++ b/html/server-request.html.in @@ -1,30 +1,29 @@ $gRequestHtml = < -$gProject $gBug system - $gBug logs by mail server - - - -

Introduction to the $gBug system request server

- - -There is a mailserver which can send the $gBug reports and + + + + $gProject $gBug system - $gBug logs by mail server + + + + +

Introduction to the $gBug system request server

+ +

There is a mailserver which can send the $gBug reports and indices as plain text on request. -

-To use it you send a mail message to -request\@$gEmailDomain. +

To use it you send a mail message to +request\@$gEmailDomain. The Subject of the message is ignored, except for generating the Subject of the reply. -

-The body you send should be a series of commands, one per line. +

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 interpreted, with a response to each command. No notifications are sent to anyone for most commands; however, the messages are logged and made available in the WWW pages. -

-Any text on a line starting with a hash sign # is +

Any text on a line starting with a hash sign # is ignored; the server will stop processing when it finds a line starting with quit, stop, thank or two hyphens (to avoid parsing a signature). It will also stop if it @@ -37,151 +36,137 @@ server.

send bugnumber

send-detail bugnumber -

-Requests the transcript for the $gBug report in question. -send-detail sends all of the `boring' messages in the -transcript, such as the various auto-acks (you should usually use -send as well, as the interesting messages are not sent by -send-detail). +

Requests the transcript for the $gBug report in question. + send-detail sends all of the `boring' messages in the + transcript, such as the various auto-acks (you should usually use + send as well, as the interesting messages are not sent by + send-detail).

index [full]

index-summary by-package

index-summary by-number -

-Request the full index (with full details, and including done and -forwarded reports), or the summary sorted by package or by number, -respectively. +

Request the full index (with full details, and including done and + forwarded reports), or the summary sorted by package or by number, + respectively.

index-maint -

-Requests the index page giving the list of maintainers with $gBugs (open -and recently-closed) in the tracking sytem. +

Requests the index page giving the list of maintainers with $gBugs + (open and recently-closed) in the tracking sytem.

index maint maintainer -

-Requests the index pages of $gBugs in the system for all maintainers -containing the string maintainer. The search term is a -case insensitive substring. The $gBug index for each matching -maintainer will be sent in a separate message. +

Requests the index pages of $gBugs in the system for all maintainers + containing the string maintainer. The search term is a + case insensitive substring. The $gBug index for each matching + maintainer will be sent in a separate message.

index-packages -

-Requests the index page giving the list of packages with $gBugs (open -and recently-closed) in the tracking sytem. +

Requests the index page giving the list of packages with $gBugs (open + and recently-closed) in the tracking sytem.

index packages package -

-Requests the index pages of $gBugs in the system for all packages -containing the string package. The search term is a case -insensitive substring. The $gBug index for each matching package will -be sent in a separate message. +

Requests the index pages of $gBugs in the system for all packages + containing the string package. The search term is a case + insensitive substring. The $gBug index for each matching package will + be sent in a separate message.

send-unmatched [this|0]

send-unmatched last|-1

send-unmatched old|-2 -

-Requests logs of messages not matched to a particular $gBug report, for -this week, last week and the week before. (Each week ends on a -Wednesday.) +

Requests logs of messages not matched to a particular $gBug report, + for this week, last week and the week before. (Each week ends on a + Wednesday.)

getinfo filename -

-Request a file containing information about package(s) and or -maintainer(s) - the files available are: -

maintainers -

-The unified list of packages' maintainers, as used by the tracking -system. +

Request a file containing information about package(s) and or + maintainer(s) - the files available are: -$gCreateMaintainers +

maintainers +: The unified list of packages' maintainers, as used by the tracking + system. - + $gCreateMaintainers -
pseudo-packages.description -
pseudo-packages.maintainers -: -List of descriptions and maintainers respectively for pseudo-packages. -

+ + +

pseudo-packages.description +

pseudo-packages.maintainers +

List of descriptions and maintainers respectively for + pseudo-packages. +

refcards -

-Requests that the mailservers' reference card be sent in plain ASCII. +

refcard + +

Requests that the mailservers' reference card be sent in plain ASCII.

help -

-Requests that this help document be sent by email in plain ASCII. + +

Requests that this help document be sent by email in plain ASCII.

quit

stop

thank...

--... -

-Stops processing at this point of the message. After this you may -include any text you like, and it will be ignored. You can use this -to include longer comments than are suitable for #, for -example for the benefit of human readers of your message (reading it -via the tracking system logs or due to a CC or -BCC). +

Stops processing at this point of the message. After this you may + include any text you like, and it will be ignored. You can use this + to include longer comments than are suitable for #, for + example for the benefit of human readers of your message (reading it + via the tracking system logs or due to a CC or + 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 -

-Sets the debugging level to level, which should be a -nonnegative integer. 0 is no debugging; 1 is usually sufficient. The -debugging output appears in the transcript. It is not likely to be -useful to general users of the $gBug system. +

Sets the debugging level to level, which should be a + nonnegative integer. 0 is no debugging; 1 is usually sufficient. The + debugging output appears in the transcript. It is not likely to be + useful to general users of the $gBug system.

-There is a reference card for the +

There is a reference card for the mailservers, available via the WWW, in bug-mailserver-refcard.txt or by email using the refcard command (see above). -

-If you wish to manipulate $gBug reports you should use the +

If you wish to manipulate $gBug reports you should use the control\@gEmailDomain address, which understands a -superset of the commands listed -above. This is described in another document, available on the -WWW, in the file bug-maint-mailcontrol.txt, or by +superset of the commands listed +above. This is described in another document, available on the +WWW, in the file +bug-maint-mailcontrol.txt, or by sending help to control\@$gEmailDomain. -

-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 version is available via the $gBug system main contents page http://$gWebDomain/. -

-Other pages: + +

Other pages:

Accessing $gBug reports in the tracking system logs

Closing $gBug reports

Followup messages

Summary postings

More-or-less obsolete subject-scanning feature

How to report a $gBug in $gProject

Not forwarding to the mailing list - minor $gBug reports

Unknown packages or $gBugs with no Package key

$gBug reports against unknown packages

$gProject $gBug tracking system main contents page

Documentation about the $gBug tracking system

Reviewing $gBug reports on the WWW

Find a $gBug report by reference number

Find a $gBug report by package

Find an archived bug report by reference number

Find an archived bug report by package

Find $gBug reports

Introduction to the $gBug control and manipulation mailserver

Mail servers' reference card

Synopsis of commands available at request@$gEmailDomain

List of info files for getinfo

Synopsis of extra commands available at control mailserver

Introduction to the $gBug system request server

Unknown packages or $gBugs with no `Package` key

Synopsis of commands available at `request@$gEmailDomain`

List of info files for `getinfo`