synced with docs on www.d.o/Bugs; fixed all HTML issues (nsgmls, tidy and weblint :); various fixes
$gAccessHtml = <<HTML_END
-<HTML>
-<HEAD>
- <TITLE>$gProject $gBugs - Accessing the logs</TITLE>
- <LINK REV="made" HREF="mailto:$gMaintainerEmail">
-</HEAD>
-<BODY>
-<A NAME="developers">
- <H1>Accessing $gBug reports in the tracking system logs</H1>
-</A>
-
-Each message received at or sent by the $gBug processing system is
+<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+ <title>$gProject $gBugs - Accessing the logs</title>
+ <link rev="made" href="mailto:$gMaintainerEmail">
+</head>
+<body>
+
+<h1><a name="developers">Accessing $gBug reports in the tracking system
+logs</a></h1>
+
+<p>Each message received at or sent by the $gBug processing system is
logged and made available in a number of ways.
-<P>
$gHTMLCopies
-There is a <A HREF="server-request.html">mailserver</A> which can send
+<p>There is a <a href="server-request.html">mailserver</a> which can send
$gBug reports as plain text on request. To use it send the word
-<CODE>help</CODE> as the sole contents of an email to
-<CODE>request</CODE> (the <CODE>Subject</CODE> of the
+<code>help</code> as the sole contents of an email to
+<code>request</code> (the <code>Subject</code> of the
message is ignored), or read the instructions on the World Wide Web or
-in the file <CODE>bug-log-mailserver.txt</CODE>.
-
-<HR>
-
-Other pages:
-<UL>
- <LI><A href="./">$gBug tracking system main contents page.</A>
- <LI><A href="Reporting.html">Instructions for reporting $gBugs.</A>
- <LI><A href="Developer.html">Developers' information regarding the $gBug processing system.</A>
- <LI><A href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</A>
- <LI><A href="db/ix/packages.html">Packages with $gBug reports.</A>
- <LI><A href="db/ix/maintainers.html">Maintainers of packages with $gBug reports.</A>
-
+in the file <code>bug-log-mailserver.txt</code>.
+
+<hr>
+
+<p>Other pages:
+<ul>
+ <li><a href="./">$gBug tracking system main contents page.</a>
+ <li><a href="Reporting.html">Instructions for reporting $gBugs.</a>
+ <li><a href="Developer.html">Developers' information regarding the $gBug processing system.</a>
+ <li><a href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</a>
+ <li><a href="db/ix/packages.html">Packages with $gBug reports.</a>
+ <li><a href="db/ix/maintainers.html">Maintainers of packages with $gBug reports.</a>
$gHTMLOtherPageList
-
</ul>
$gHTMLTail
$gDeveloperHtml = <<HTML_END
-<HTML>
-<HEAD>
- <title>$gProject - Developers' information</title>
- <link rev="made" href="mailto:$gMaintainerEmail">
+<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+ <title>$gProject - Developers' information</title>
+ <link rev="made" href="mailto:$gMaintainerEmail">
</head>
<body>
- <h1><A name="developers">Developers' information regarding the $gBug processing system</A></h1>
-Initially, a $gBug report is submitted by a user as an ordinary mail
+<h1><A name="developers">Developers' information regarding the $gBug processing system</a></h1>
+
+<p>Initially, a $gBug report is submitted by a user as an ordinary mail
message to <code>submit\@$gEmailDomain</code>. This will then be
given a number, acknowledged to the user, and forwarded to a mailing
list (if configured). If the submitter included a <code>Package</code>
line listing a package with a known maintainer the maintainer will get
a copy too.
-<p>
-The <code>Subject</code> line will have
+<p>The <code>Subject</code> line will have
<code>$gBug#</code><var>nnn</var><code>:</code> added, and the
<code>Reply-To</code> will be set to include both the submitter of the
report and <var>nnn</var><code>\@$gEmailDomain</code>.
-<p>
<h2>Closing $gBug reports</h2>
-A developer who receives a $gBug from the tracking system, or sees it on
+<p>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 <code>To</code> field to say
<var>nnn</var><code>\@$gEmailDomain</code>
(<var>nnn</var><code>-close</code> is provided as an alias for
<var>nnn</var><code>-done</code>).
-<p>
-The address of the original submitter of the $gBug report will be
+<p>The address of the original submitter of the $gBug report will be
included in the default <code>To</code> field, because the $gBug system
included it in the <code>Reply-To</code>.
-<p>
-`Done' messages are forwarded to a mailing list if the mailing list has been
-set up.
-<P>
+<p>`Done' messages are automatically forwarded to the <code>$gDoneList</code>
+mailing list, if the mailing list has been set up.
-The person closing the $gBug and the person who submitted it will each
+<p>The person closing the $gBug and the person who submitted it will each
get a notification about the change in status of the report.
<h2>Followup messages</h2>
-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 <var>nnn</var><code>\@$gEmailDomain</code> 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.
-<p>
+<p>If a developer wishes to reply to a $gBug report they may simply reply
+to the message (that will <b>not</b> mark the bug as done). Their reply will
+(by default, if they respect the Reply-To: header) go to
+<var>nnn</var><code>\@$gEmailDomain</code>, and to the original submitter of
+the $gBug report (note: this is two distinct addresses). The $gBug tracking
+system will receive the message at <var>nnn</var><code>\@$gEmailDomain</code>,
+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
+(<code>$gSubmitList\@$gEmailDomain</code>).
+
+<p>A developer may explicitly mail the bug's submitter with an email to
+<var>nnn</var><code>-submitter\@$gEmailDomain</code>.
-If you wish to send a followup message which is not appropriate for
+<p>If you wish to send a followup message which is not appropriate for
any mailing list you can do so by sending it to
<var>nnn</var><code>-quiet\@$gEmailDomain</code> or
-<var>nnn</var><code>-maintonly\@$gEmailDomain</code>, which only file it (not
-forwarding it anywhere) and send it on only to the maintainer of the
-package in question, respectively.
-<p>
-
-Do <em>not</em> use the `reply to all recipients' or `followup'
+<var>nnn</var><code>-maintonly\@$gEmailDomain</code>.
+Mail to <var>nnn</var><code>-quiet\@$gEmailDomain</code> is filed in the
+$gBug Tracking System but is not delivered to any individuals or mailing
+lists. Mail to <var>nnn</var><code>-maintonly\@$gEmailDomain</code> is
+filed in the $gBug Tracking System and is delivered only to the maintainer
+of the package in question.
+
+<p>Do <em>not</em> 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
-<var>nnn</var><code>\@$gEmailDomain</code> and to
+substantially. In particular, see that you don't send followup messages
+both to <var>nnn</var><code>\@$gEmailDomain</code> and to
<code>submit\@$gEmailDomain</code>, because the $gBug system will then
get two copies of it and each one will be forwarded to the designated
mailing list separately.
-<p>
-
-<h2><A name="severities">Severity levels</A></h2>
-The $gBug system records a severity level with each $gBug report. This is
-set to <code>$gDefaultSeverity</code> by default, but can be overridden either by
-supplying a <code>Severity</code> line in the pseudo-header when the
-$gBug is submitted (see the
-<A href="Reporting.html#pseudoheader">instructions for reporting
-$gBugs</A>), or by using the <code>severity</code> command with the
-<A href="#requestserv">control request server</A>.
+<h2><A name="severities">Severity levels</a></h2>
-<p>
+<p>The $gBug system records a severity level with each $gBug report. This
+is set to <code>$gDefaultSeverity</code> by default, but can be overridden
+either by supplying a <code>Severity</code> line in the pseudo-header when
+the $gBug is submitted (see the
+<a href="Reporting.html#pseudoheader">instructions for reporting $gBugs</a>),
+or by using the <code>severity</code> command with the
+<a href="#requestserv">control request server</a>.
-The severity levels are:
+<p>The severity levels are:
<dl>
$gHTMLSeverityDesc
</dl>
-<h2><A name="forward">Recording that you have passed on a $gBug report</A></h2>
+<h2><A name="forward">Recording that you have passed on a $gBug report</a></h2>
-When a developer forwards a $gBug report to the developer of the
+<p>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:
-<p>
-Make sure that the <code>To</code> field of your message to the author
+<p>Make sure that the <code>To</code> 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
<var>nnn</var><code>-forwarded\@$gEmailDomain</code> in the
<code>CC</code> field.
-<p>
-Ask the author to preserve the <code>CC</code> to
+<p>Ask the author to preserve the <code>CC</code> to
<var>nnn</var><code>-forwarded\@$gEmailDomain</code> when they reply, so that
the $gBug tracking system will file their reply with the original
report.
-<p>
-When the $gBug tracking system gets a message at
+<p>When the $gBug tracking system gets a message at
<var>nnn</var><code>-forwarded</code> it will mark the relevant $gBug as
having been forwarded to the address(es) in the <code>To</code> field
of the message it gets.
-<p>
-You can also manipulate the `forwarded to' information by sending messages to
-<A href="server-control.html"><code>control\@$gEmailDomain</code></A>.
+<p>You can also manipulate the `forwarded to' information by sending
+messages to <a href="server-control.html"><code>control\@$gEmailDomain</code></a>.
<h2>Summary postings</h2>
-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.
-<p>
+<p>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
-<h2><A name="requestserv">Reopening, reassigning and manipulating $gBugs</A></h2>
+<h2><A name="requestserv">Reopening, reassigning and manipulating $gBugs</a></h2>
-It is possible to reassign $gBug reports to other packages, to reopen
+<p>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 <code>control\@$gEmailDomain</code>.
-<p>
-The <A href="server-control.html">format of these messages</A> is
+<p>The <a href="server-control.html">format of these messages</a> is
described in another document available on the World Wide Web or in
the file <code>bug-maint-mailcontrol.txt</code>. A plain text version
can also be obtained by mailing the word <code>help</code> to the
server at the address above.
<h2>More-or-less obsolete subject-scanning feature</h2>
-(this is likely to be removed the next version)<BR>
-Messages that arrive at <code>submit</code> or <code>$gBugs</code> whose
+
+<!-- (this is likely to be removed the next version?) -->
+
+<p>Messages that arrive at <code>submit</code> or <code>$gBugs</code> whose
Subject starts <code>Bug#</code><var>nnn</var> will be treated as
having been sent to <var>nnn</var><code>\@$gEmailDomain</code>. This is both
for backwards compatibility with mail forwarded from the old
addresses, and to catch followup mail sent to <code>submit</code> by
mistake (for example, by using reply to all recipients).
-<p>
-
-A similar scheme operates for <code>maintonly</code>,
+<p>A similar scheme operates for <code>maintonly</code>,
<code>done</code>, <code>quiet</code> and <code>forwarded</code>,
which treat mail arriving with a Subject tag as having been sent to
the corresponding <var>nnn-whatever</var><code>\@$gEmailDomain</code> address.
-<p>
-
-Messages arriving at plain <code>forwarded</code> and
+<p>Messages arriving at plain <code>forwarded</code> and
<code>done</code> - 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.
-<h2><A name="future">Future plans</A></h2>
-
-At some point the <code>Package:</code> secondary header field may
-become mandatory - at the moment omitting it just produces a warning
-message.
-
<hr>
-Other pages:
-<ul>
-<li><A href="./">$gBug tracking system main contents page.</A>
-<li><A href="Reporting.html">Instructions for reporting $gBugs.</A>
-<li><A href="Access.html">Accessing the $gBug tracking logs other than by WWW.</A>
-<li><A href="server-refcard.html">Mailservers' reference card.</A>
-<li><A href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</A>
-<li><A href="db/ix/packages.html">Packages with $gBug reports.</A>
-<li><A href="db/ix/maintainers.html">Maintainers of packages with $gBug reports.</A>
+<p>Other pages:
+<ul>
+ <li><a href="./">$gBug tracking system main contents page.</a>
+ <li><a href="Reporting.html">Instructions for reporting $gBugs.</a>
+ <li><a href="Access.html">Accessing the $gBug tracking logs other than by WWW.</a>
+ <li><a href="server-refcard.html">Mailservers' reference card.</a>
+ <li><a href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</a>
+ <li><a href="db/ix/packages.html">Packages with $gBug reports.</a>
+ <li><a href="db/ix/maintainers.html">Maintainers of packages with $gBug reports.</a>
$gHTMLOtherPageList
-
</ul>
$gHTMLTail
$gReportingHtml = <<HTML_END
-<html><head><title>$gProject $gBugs - how to report a $gBug</title>
-<link rev="made" href="mailto:$gMaintainerEmail">
-</head><body>
+<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+ <title>$gProject $gBugs - how to report a $gBug</title>
+ <link rev="made" href="mailto:$gMaintainerEmail">
+</head>
+<body>
+
<h1>How to report a $gBug in $gProject</h1>
-Send mail to
-<A href="mailto:submit\@$gEmailDomain"><code>submit\@$gEmailDomain</code></A>,
+<p>Send mail to
+<a href="mailto:submit\@$gEmailDomain"><code>submit\@$gEmailDomain</code></a>,
as described below.
-<p>
-Please don't report several unrelated $gBugs - especially ones in
+<p>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
<code>submit\@$gEmailDomain</code> (for details of how to do this right, see
-<A href="#xcc">below</A>).
-<p>
+<a href="#xcc">below</a>).
-Lists of currently-outstanding $gBugs are available <A href="./">on
-the World Wide Web</A> and <A href="Access.html">elsewhere</A> - see
+<p>Lists of currently-outstanding $gBugs are available <a href="./">on
+the World Wide Web</a> and <a href="Access.html">elsewhere</a> - see
other documents for details.
-<p>
-You should put a pseudo-header at the start of the body of the
+<p>You need to put a pseudo-header at the start of the body of the
message, with the <code>Package:</code> and <code>Version:</code>
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.
$gHTMLFindPackage
-<em>See below for <A href="#details">further requirements</A></em>.
-<p>
+<p><em>See below for <a href="#details">further requirements</a></em>.
$gHTMLPseudoDesc
-<h2><A name="example">Example</A></h2>
+<h2><A name="example">Example</a></h2>
-A $gBug report, with mail header, looks something like this:
+<p>A $gBug report, with mail header, looks something like this:
<pre>
To: submit\@$gEmailDomain
From: diligent\@testing.linux.org
Subject: Hello says `goodbye'
-<A name="pseudoheader">Package: hello</A>
- Version: 1.3-2
+ <A name="pseudoheader">Package: hello</a>
+ Version: 1.3-16
When I invoke `hello' without arguments from an ordinary shell
prompt it prints `goodbye', rather than the expected `hello, world'.
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.
</pre>
-<h2><A name="details">Please include in your report:</A></h2>
+<h2><A name="details">Please include in your report:</a></h2>
<ul>
-<li>The <em>exact</em> and <em>complete</em> text of any error
-messages printed or logged. This is very important!
-<li>Exactly what you typed or did to demonstrate the problem.
-<li>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.
-<li>A suggested fix, or even a patch, if you have one.
-<li>Details of the configuration of the program with the problem.
-Include the complete text of its configuration files.
+ <li>The <em>exact</em> and <em>complete</em> text of any error
+ messages printed or logged. This is very important!
+ <li>Exactly what you typed or did to demonstrate the problem.
+ <li>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.
+ <li>A suggested fix, or even a patch, if you have one.
+ <li>Details of the configuration of the program with the problem.
+ Include the complete text of its configuration files.
+
$gXtraBugInfo
+
</ul>
-Include any detail that seems relevant - you are in very little danger
+<p>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.).
-<p>
-
-Of course, like any email, you should include a clear, descriptive
+<p>Of course, like any email, you should include a clear, descriptive
<code>Subject</code> 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!
-<h2><A name="xcc">Sending copies of $gBug reports to other addresses</A></h2>
+<h2><A name="xcc">Sending copies of $gBug reports to other addresses</a></h2>
-Sometimes it is necessary to send a copy of a $gBug report to somewhere
+<p>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.
-<p>
-You could do this by CC'ing your $gBug report to the other address(es),
+<p>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 <code>Reply-To</code> field and the <code>Subject</code> line.
When the recipients reply they will probably preserve the
<code>submit\@$gEmailDomain</code> entry in the header and have their
message filed as a new $gBug report. This leads to many duplicated
reports.
-<p>
-The <em>right</em> way to do this is to use the
-<code>X-$gProject-CC</code> header. Add a line like this to your
-message's mail header (not to the pseudo header with the
-<code>Package</code> field):
+<p>The <em>right</em> way to do this is to use the <code>X-Debbugs-CC</code>
+header. Add a line like this to your message's mail header (<em>not</em>
+to the pseudo header with the <code>Package</code> field):
<pre>
- X-$gProject-CC: other-list\@cosmic.edu
+ X-Debbugs-CC: other-list\@cosmic.edu
</pre>
This will cause the $gBug tracking system to send a copy of your report
-to the address(es) in the <code>X-$gProject-CC</code> line as well as to
+to the address(es) in the <code>X-Debbugs-CC</code> line as well as to
any mailing list.
-<p>
-This feature can often be combined usefully with mailing
+<p>This feature can often be combined usefully with mailing
<code>quiet</code> - see below.
-<h2><A name="severities">Severity levels</A></h2>
+<h2><A name="severities">Severity levels</a></h2>
-If a report is of a particularly serious $gBug, or is merely a feature
+<p>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.
-<p>
-To assign a severity level put a
+<p>To assign a severity level put a
<code>Severity: <var>severity</var></code> line in the pseudo-header,
together with <code>Package</code> and <code>Version</code>. The
severity levels available are described in the
-<A href="Developer.html#severities">developers' documentation</A>.
+<a href="Developer.html#severities">developers' documentation</a>.
<h2>Not forwarding to the mailing list - minor $gBug reports</h2>
-If a $gBug report is minor (for example, a documentation typo or other
+<p>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 <code>maintonly\@$gEmailDomain</code> or <code>quiet\@$gEmailDomain</code>.
+send them to <code>maintonly\@$gEmailDomain</code> or
+<code>quiet\@$gEmailDomain</code>.
<code>maintonly</code> will send the report on to the package
maintainer (provided you supply a correct <code>Package</code> line in
the pseudo-header and the maintainer is known), and <code>quiet</code>
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).
-<p>
-If you do this the $gBug system will set the <code>Reply-To</code> of
+<p>If you do this the $gBug system will set the <code>Reply-To</code> of
any forwarded message so that replies will by default be processed in
the same way as the original report.
-<h3>Unknown packages or $gBugs with no <code>Package</code> key</h3>
+<h3>$gBug reports against unknown packages</h3>
-If the $gBug tracking system doesn't know who the maintainer of the
+<p>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 <code>maintonly</code> was used.
-<p>
-When sending to <code>maintonly\@$gEmailDomain</code> or
+<p>When sending to <code>maintonly\@$gEmailDomain</code> or
<var>nnn</var><code>-maintonly\@$gEmailDomain</code> you should make sure that
the $gBug report is assigned to the right package, by putting a correct
<code>Package</code> at the top of an original submission of a report,
-or by using <A href="server-control.html">the
-<code>control\@$gEmailDomain</code> service</A> to (re)assign the report
+or by using <a href="server-control.html">the
+<code>control\@$gEmailDomain</code> service</a> to (re)assign the report
appropriately first if it isn't correct already.
$gXtraReportingInfo
<hr>
-Other pages:
-<ul>
-<li><A href="./">Bug tracking system main contents page.</A>
-<li><A href="Developer.html">Developers'
-information regarding the $gBug processing system.</A>
-<li><A href="Access.html">Accessing the $gBug tracking logs other than by WWW.</A>
-<li><A href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</A>
-<li><A href="db/ix/packages.html">Packages with $gBug reports.</A>
-<li><A href="db/ix/maintainers.html">Maintainers of packages with $gBug reports.</A>
+<p>Other pages:
+<ul>
+ <li><a href="./">Bug tracking system main contents page.</a>
+ <li><a href="Developer.html">Developers' information regarding the $gBug processing system.</a>
+ <li><a href="Access.html">Accessing the $gBug tracking logs other than by WWW.</a>
+ <li><a href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</a>
+ <li><a href="db/ix/packages.html">Packages with $gBug reports.</a>
+ <li><a href="db/ix/maintainers.html">Maintainers of packages with $gBug reports.</a>
$gHTMLOtherPageList
-
</ul>
$gHTMLTail
$gIndexHtml = <<HTML_END
-<html><head>
-<title>$gProject $gBug tracking system</title>
-<link rev="made" href="mailto:$gMaintainerEmail">
-</head><body>
+<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+ <title>$gProject $gBug tracking system</title>
+ <link rev="made" href="mailto:$gMaintainerEmail">
+</head>
+<body>
+
<h1>$gProject $gBug tracking system main contents page</h1>
-$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.
+<p>$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
<h2>Documentation about the $gBug tracking system</h2>
<ul>
-<li><A href="Reporting.html">Instructions for reporting a $gBug.</A>
-<li><A href="Access.html">Ways of accessing the $gBug reporting logs.</A>
-<li><A href="server-request.html">Requesting $gBug reports by email.</A>
-<li><A href="Developer.html">Developers' information on how to use the system.</A>
-<li><A href="server-control.html">Developers' information on
-manipulating $gBugs by email.</A>
-<li><A href="server-refcard.html">Mailservers' reference card.</A>
+ <li><a href="Reporting.html">Instructions for reporting a $gBug.</a>
+ <li><a href="Access.html">Ways of accessing the $gBug reporting logs.</a>
+ <li><a href="server-request.html">Requesting $gBug reports by email.</a>
+ <li><a href="Developer.html">Developers' information on how to use the system.</a>
+ <li><a href="server-control.html">Developers' information on manipulating $gBugs by email.</a>
+ <li><a href="server-refcard.html">Mailservers' reference card.</a>
</ul>
<h2>Reviewing $gBug reports on the WWW</h2>
<ul>
-<li><A href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</A>
-<li><A href="db/ix/packages.html">Index of packages with $gBug reports.</A>
-<li><A href="db/ix/maintainers.html">Index of maintainers of packages with $gBug reports.</A>
-<li>Outstanding
-<A href="db/si/pendingcritical.html">critical</A>,
-<A href="db/si/pendinggrave.html">grave</A>,
-<A href="db/si/pendingnormal.html">normal</A> and
-<A href="db/si/pendingfixed.html">fixed</A> $gBugs and
-<A href="db/si/pendingwishlist.html">wishlist</A> items.
-<li>Forwarded
-<A href="db/si/forwardedcritical.html">critical</A>,
-<A href="db/si/forwardedgrave.html">grave</A>,
-<A href="db/si/forwardednormal.html">normal</A> and
-<A href="db/si/forwardedfixed.html">fixed</A> $gBugs and
-<A href="db/si/forwardedwishlist.html">wishlist</A> items.
-<li>Resolved
-<A href="db/si/donecritical.html">critical</A>,
-<A href="db/si/donegrave.html">grave</A>,
-<A href="db/si/donenormal.html">normal</A> and
-<A href="db/si/donefixed.html">fixed</A> $gBugs and
-<A href="db/si/donewishlist.html">wishlist</A> items.
-<li><A href="db/ix/psummary.html">Summary of outstanding reports, sorted by package.</A>
-<li><A href="db/ix/summary.html">Summary of outstanding reports, sorted by number.</A>
-<li><A href="db/ju/junk.html">Logs not associated with a particular $gBug report.</A>
-<li><A href="db/ix/zstamp.html">Time stamp page (for checking that mirror is current).</A>
+ <li><a href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</a>
+ <li><a href="db/ix/packages.html">Index of packages with $gBug reports.</a>
+ <li><a href="db/ix/maintainers.html">Index of maintainers of packages with $gBug reports.</a>
+ <li>Outstanding
+ <a href="db/si/pendingcritical.html">critical</a>,
+ <a href="db/si/pendinggrave.html">grave</a>,
+ <a href="db/si/pendingnormal.html">normal</a> and
+ <a href="db/si/pendingfixed.html">fixed</a> $gBugs and
+ <a href="db/si/pendingwishlist.html">wishlist</a> items.
+ <li>Forwarded
+ <a href="db/si/forwardedcritical.html">critical</a>,
+ <a href="db/si/forwardedgrave.html">grave</a>,
+ <a href="db/si/forwardednormal.html">normal</a> and
+ <a href="db/si/forwardedfixed.html">fixed</a> $gBugs and
+ <a href="db/si/forwardedwishlist.html">wishlist</a> items.
+ <li>Resolved
+ <a href="db/si/donecritical.html">critical</a>,
+ <a href="db/si/donegrave.html">grave</a>,
+ <a href="db/si/donenormal.html">normal</a> and
+ <a href="db/si/donefixed.html">fixed</a> $gBugs and
+ <a href="db/si/donewishlist.html">wishlist</a> items.
+ <li><a href="db/ix/psummary.html">Summary of outstanding reports, sorted by package.</a>
+ <li><a href="db/ix/summary.html">Summary of outstanding reports, sorted by number.</a>
+ <li><a href="db/ju/junk.html">Logs not associated with a particular $gBug report.</a>
+ <li><a href="db/ix/zstamp.html">Time stamp page (for checking that mirror is current).</a>
</ul>
-Each closed $gBug report is expired from these logs $gRemoveAge days after the
-last message relating to it is received and filed.
-
-<h3>Find a $gBug report by reference number</h2>
-
-<form method="get" action="$gCGIDomain/bugs-fetch2.pl">
-<input type="hidden" name="type" value="ref">
-<input type="text" size="10" name="ref" value="">
-<input type="hidden" name="base" value="http://$gWebDomain">
-<input type="submit" value="Fetch">
-</form>
-`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 <A href="db/ix/zstamp.html">timestamp page</A>.
-
-<h3>Find a $gBug report by package</h2>
-
-<form method="get" action="$gCGIDomain/bugs-fetch2.pl">
-<input type="hidden" name="type" value="package">
-<input type="text" size="30" name="package" value="">
-<input type="hidden" name="base" value="http://$gWebDomain">
-<input type="submit" value="Fetch">
-</form>
-`Not found' means that that package does not exist or does not have
-any outstanding or recently closed $gBug reports.
-
-<h3>Find an archived bug report by reference number</h2>
-<form method="get" action="http://cgi.debian.org/cgi-bin/bugreport.cgi">
-<input type="hidden" name="archive" value="yes">
-<input type="text" size="10" name="bug" value="">
-<input type="submit" value="Fetch">
-</form>
-<h3>Find an archived bug report by package</h2>
-<form method="get" action="http://cgi.debian.org/cgi-bin/pkgarch.cgi">
-<input type="text" size="20" name="pkg" value="">
-<input type="submit" value="Fetch">
-</form>
-<A HREF="http://cgi.debian.org/cgi-bin/pkgarch.cgi">or get a list of
-packages</A>
+<p><small>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.</small>
+
+<h3>Find $gBug reports</h3>
+
+<table border="0" width="100%" summary="$gBug report search forms">
+<tr>
+ <td valign="top" nowrap>
+ <form method="get" action="http://$gCGIDomain/cgi-bin/bugreport.cgi">
+ <font face="Arial,Helvetica"><b>
+ By number:
+ <br>
+ <input type="text" size="9" name="bug" value="">
+ <input type="submit" value="Fetch">
+ </b>
+ </font>
+ </form>
+ </td>
+
+ <td valign="top" nowrap>
+ <form method="get" action="http://$gCGIDomain/cgi-bin/pkgreport.cgi">
+ <font face="Arial,Helvetica"><b>
+ By package:
+ <br>
+ <input type="text" size="35" name="pkg" value="">
+ <input type="submit" value="Fetch">
+ </b>
+ <br>
+ <small>
+ <input type="radio" name="archive" value="no" checked> active bugs
+ <input type="radio" name="archive" value="yes"> archived bugs
+ </small>
+ </font>
+ </form>
+ </td>
+</tr>
+<tr>
+ <td valign="top" nowrap>
+ <form method="get" action="http://$gCGIDomain/cgi-bin/pkgreport.cgi">
+ <font face="Arial,Helvetica"><b>
+ By maintainer e-mail:
+ <br>
+ <input type="text" size="35" name="maint" value="">
+ <input type="submit" value="Fetch">
+ </b>
+ <br>
+ <small>
+ <input type="radio" name="archive" value="no" checked> active bugs
+ <input type="radio" name="archive" value="yes"> archived bugs
+ </small>
+ </font>
+ </form>
+ </td>
+
+ <td valign="top" nowrap>
+ <form method="get" action="http://$gCGIDomain/cgi-bin/pkgreport.cgi">
+ <font face="Arial,Helvetica"><b>
+ By submitter e-mail:
+ <br>
+ <input type="text" size="35" name="submitter" value="">
+ <input type="submit" value="Fetch">
+ </b>
+ <br>
+ <small>
+ <input type="radio" name="archive" value="no" checked> active bugs
+ <input type="radio" name="archive" value="yes"> archived bugs
+ </small>
+ </font>
+ </form>
+ </td>
+</tr>
+</table>
$gHTMLOtherPages
$gHTMLTail
HTML_END
-
$gControlHtml = <<HTML_END
-<html><head>
-<html><head>
-<title>$gProject $gBug system - control mail server commands</title>
-<link rev="made" href="mailto:$gMaintainerEmail">
-</head><body>
+<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+ <title>$gProject $gBug system - control mail server commands</title>
+ <link rev="made" href="mailto:$gMaintainerEmail">
+</head>
+<body>
+
<h1>Introduction to the $gBug control and manipulation mailserver</h1>
-In addition to the mailserver on <code>request\@$gEmailDomain</code>
+<p>In addition to the mailserver on <code>request\@$gEmailDomain</code>
which allows the retrieval of $gBug data and documentation by email,
there is another server on <code>control\@$gEmailDomain</code> which
also allows $gBug reports to be manipulated in various ways.
-<p>
-The control server works just like the request server, except that it
+<p>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.
-<p>
-Please see the
-<A href="server-request.html#introduction">introduction to
-the request server</A>
-available on the World Wide Web, in the file
+<p>Please see the
+<a href="server-request.html#introduction">introduction to the request
+server</a> available on the World Wide Web, in the file
<code>bug-maint-mailcontrol.txt</code>, or by sending
<code>help</code> to either mailserver, for details of the basics of
operating the mailservers and the common commands available when
mailing either address.
-<p>
-The <A href="server-refcard.html">reference card</A> for the
+<p>The <a href="server-refcard.html">reference card</a> for the
mailservers is available via the WWW, in
<code>bug-mailserver-refcard.txt</code> or by email using the
<code>refcard</code> command).
<dl>
<dt><code>close</code> <var>bugnumber</var>
-<dd>
-Close $gBug report #<var>bugnumber</var>.
-<p>
+ <dd>Close $gBug report #<var>bugnumber</var>.
-A notification is sent to the user who reported the $gBug, but (in
-contrast to mailing <var>bugnumber</var><code>-done@$gEmailDomain</code>) the
-text of the mail which caused the $gBug to be closed is <em>not</em>
-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.
+ <p>A notification is sent to the user who reported the $gBug, but (in
+ contrast to mailing <var>bugnumber</var><code>-done@$gEmailDomain</code>) the
+ text of the mail which caused the $gBug to be closed is <em>not</em>
+ 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.
<dt><code>reassign</code> <var>bugnumber</var> <var>package</var>
-<dd>
-Records that $gBug #<var>$gBugnumber</var> is a $gBug in <var>package</var>.
-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).
+ <dd>Records that $gBug #<var>${gBug}number</var> is a $gBug in <var>package</var>.
+ 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).
<dt><code>reopen</code> <var>bugnumber</var>
[ <var>originator-address</var> | <code>=</code> | <code>!</code> ]
-<dd>
-
-Reopens #<var>bugnumber</var> if it is closed.
-<p>
-
-By default, or if you specify <code>=</code>, the original submitter is
-still as the originator of the report, so that they will get the ack
-when it is closed again.
-<p>
-
-If you supply an <var>originator-address</var> 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 <code>!</code>
-shorthand or specify your own email address.
-<p>
-
-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.
-<p>
-
-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).
+
+ <dd>Reopens #<var>bugnumber</var> if it is closed.
+
+ <p>By default, or if you specify <code>=</code>, the original submitter is
+ still as the originator of the report, so that they will get the ack
+ when it is closed again.
+
+ <p>If you supply an <var>originator-address</var> 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 <code>!</code>
+ shorthand or specify your own email address.
+
+ <p>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.
+
+ <p>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).
<dt><code>forwarded</code> <var>bugnumber</var> <var>address</var>
-<dd>
-Notes that <var>bugnumber</var> has been forwarded to the upstream
-maintainer at <var>address</var>. 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.
+ <dd>Notes that <var>bugnumber</var> has been forwarded to the upstream
+ maintainer at <var>address</var>. 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.
<dt><code>notforwarded</code> <var>bugnumber</var>
-<dd>
-Forgets any idea that <var>bugnumber</var> has been forwarded to any
-upstream maintainer. If the $gBug was not recorded as having been
-forwarded then this will do nothing.
+ <dd>Forgets any idea that <var>bugnumber</var> has been forwarded to any
+ upstream maintainer. If the $gBug was not recorded as having been
+ forwarded then this will do nothing.
<dt><code>retitle</code> <var>bugnumber</var> <var>new-title</var>
-<dd>
-Changes the title of a $gBug report to that specified (the default is
-the <code>Subject</code> mail header from the original report.
-<p>
+ <dd>Changes the title of a $gBug report to that specified (the default is
+ the <code>Subject</code> 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.
+ <p>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.
<dt><code>severity</code> <var>bugnumber</var> <var>severity</var>
-<dd>
-Set the severity level for $gBug report #<var>bugnumber</var> to
-<var>severity</var>. No notification is sent to the user who reported
-the $gBug.
-<p>
+ <dd>Set the severity level for $gBug report #<var>bugnumber</var> to
+ <var>severity</var>. No notification is sent to the user who reported
+ the $gBug.
-For <A href="Developer.html#severities">their meanings</A> please
-consult the general developers' documentation for the $gBug system.
+ <p>For <a href="Developer.html#severities">their meanings</a> please
+ consult the general developers' documentation for the $gBug system.
<dt><code>merge</code> <var>bugnumber</var> <var>bugnumber</var> ...
-<dd>
-
-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.
-<p>
-
-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 <code>reassign</code>, <code>reopen</code>
-and so forth to make sure that they are before using
-<code>merge</code>.
-<p>
-
-If any of the $gBugs listed in a <code>merge</code> 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.
-<p>
-
-Merging reports causes a note to appear on each report's logs; on the
-WWW pages this is includes links to the other $gBugs.
-<p>
-
-Merged reports are all expired simultaneously, and only when all of
-the reports each separately meet the criteria for expiry.
+
+ <dd>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.
+
+ <p>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 <code>reassign</code>, <code>reopen</code>
+ and so forth to make sure that they are before using
+ <code>merge</code>.
+
+ <p>If any of the $gBugs listed in a <code>merge</code> 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.
+
+ <p>Merging reports causes a note to appear on each report's logs; on the
+ WWW pages this is includes links to the other $gBugs.
+
+ <p>Merged reports are all expired simultaneously, and only when all of
+ the reports each separately meet the criteria for expiry.
<dt><code>unmerge</code> <var>bugnumber</var>
-<dd>
-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.
-<p>
+ <dd>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.
-<p>
+ <p>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 <code>unmerge</code>
-command; if you want to disconnect more than one $gBug simply include
-several <code>unmerge</code> commands in your message.
+ <p>You can only unmerge one report with each <code>unmerge</code>
+ command; if you want to disconnect more than one $gBug simply include
+ several <code>unmerge</code> commands in your message.
</dl>
<hr>
-Other pages:
+
+<p>Other pages:
<ul>
-<li><A href="./">$gBug tracking system main contents page.</A>
-<li><A href="Reporting.html">Instructions for reporting $gBugs.</A>
-<li><A href="Access.html">Accessing the $gBug tracking logs other than by WWW.</A>
-<li><A href="Developer.html">Developers'
-information regarding the $gBug processing system.</A>
-<li><A href="server-request.html">Fundamentals of the mailserver
-and commands for retrieving $gBugs.</A>
-<li><A href="server-refcard.html">Mailservers' reference card.</A>
-<li><A href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</A>
-<li><A href="db/ix/packages.html">Packages with $gBug reports.</A>
-<li><A href="db/ix/maintainers.html">Maintainers of packages with $gBug reports.</A>
- $gHTMLOtherPageList
+ <li><a href="./">$gBug tracking system main contents page.</a>
+ <li><a href="Reporting.html">Instructions for reporting $gBugs.</a>
+ <li><a href="Access.html">Accessing the $gBug tracking logs other than by WWW.</a>
+ <li><a href="Developer.html">Developers' information regarding the $gBug processing system.</a>
+ <li><a href="server-request.html">Fundamentals of the mailserver and commands for retrieving $gBugs.</a>
+ <li><a href="server-refcard.html">Mailservers' reference card.</a>
+ <li><a href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</a>
+ <li><a href="db/ix/packages.html">Packages with $gBug reports.</a>
+ <li><a href="db/ix/maintainers.html">Maintainers of packages with $gBug reports.</a>
+$gHTMLOtherPageList
</ul>
$gHTMLTail
$gRefcardHtml = <<HTML_END
-<html><head>
-<title>$gProject $gBug system - mail servers' reference card</title>
-<link rev="made" href="mailto:$gMaintainerEmail">
-</head><body>
+<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+ <title>$gProject $gBug system - mail servers' reference card</title>
+ <link rev="made" href="mailto:$gMaintainerEmail">
+</head>
+<body>
+
<h1>Mail servers' reference card</h1>
-Full documentation of the mail servers is available on the WWW, in the
+<p>Full documentation of the mail servers is available on the WWW, in the
files
-<A href="server-request.html">bug-log-mailserver.txt</A> and
-<A href="server-control.html">bug-maint-mailcontrol.txt</A> or by
+<a href="server-request.html">bug-log-mailserver.txt</a> and
+<a href="server-control.html">bug-maint-mailcontrol.txt</a> or by
sending the word <code>help</code> to each mailserver.
<h2>Synopsis of commands available at <code>request@$gEmailDomain</code></h2>
<ul compact>
-<li><code>send</code> <var>bugnumber</var>
-<li><code>send-detail</code> <var>bugnumber</var>
-<li><code>index</code> [<code>full</code>]
-<li><code>index-summary by-package</code>
-<li><code>index-summary by-number</code>
-<li><code>index-maint</code>
-<li><code>index maint</code> <var>maintainer-substring</var>
-<li><code>index-packages</code>
-<li><code>index packages</code> <var>package-substring</var>
-<li><code>send-unmatched</code> [<code>this</code>|<code>0</code>]
-<li><code>send-unmatched</code> <code>last</code>|<code>-1</code>
-<li><code>send-unmatched</code> <code>old</code>|<code>-2</code>
-<li><code>getinfo</code> <var>filename</var> <em>(see below)</em>
-<li><code>help</code>
-<li><code>refcard</code>
-<li><code>quit</code>|<code>stop</code>|<code>thank</code>...|<code>--</code>...
-<li><code>#</code>... <em>(comment)</em>
-<li><code>debug</code> <var>level</var>
+ <li><code>send</code> <var>bugnumber</var>
+ <li><code>send-detail</code> <var>bugnumber</var>
+ <li><code>index</code> [<code>full</code>]
+ <li><code>index-summary by-package</code>
+ <li><code>index-summary by-number</code>
+ <li><code>index-maint</code>
+ <li><code>index maint</code> <var>maintainer-substring</var>
+ <li><code>index-packages</code>
+ <li><code>index packages</code> <var>package-substring</var>
+ <li><code>send-unmatched</code> [<code>this</code>|<code>0</code>]
+ <li><code>send-unmatched</code> <code>last</code>|<code>-1</code>
+ <li><code>send-unmatched</code> <code>old</code>|<code>-2</code>
+ <li><code>getinfo</code> <var>filename</var> <em>(see below)</em>
+ <li><code>help</code>
+ <li><code>refcard</code>
+ <li><code>quit</code>|<code>stop</code>|<code>thank</code>...|<code>--</code>...
+ <li><code>#</code>... <em>(comment)</em>
+ <li><code>debug</code> <var>level</var>
</ul>
<h3>List of info files for <code>getinfo</code></h3>
<ul compact>
-<li><code>maintainers</code>
-<li><code>override.stable</code>
-<li><code>override.development</code>
-<li><code>override.contrib</code>
-<li><code>override.non-free</code>
-<li><code>override.experimental</code>
-<li><code>override.</code><var>codeword</var>
-<li><code>pseudo-packages.description</code>
-<li><code>pseudo-packages.maintainers</code>
+ <li><code>maintainers</code>
+ <li><code>override.stable</code>
+ <li><code>override.development</code>
+ <li><code>override.contrib</code>
+ <li><code>override.non-free</code>
+ <li><code>override.experimental</code>
+ <li><code>override.</code><var>codeword</var>
+ <li><code>pseudo-packages.description</code>
+ <li><code>pseudo-packages.maintainers</code>
</ul>
<h2>Synopsis of extra commands available at control mailserver</h2>
<ul compact>
-<li><code>close</code> <var>bugnumber</var>
- <em>(you must separately tell originator why)</em>
-<li><code>reassign</code> <var>bugnumber</var> <var>package</var>
-<li><code>severity</code> <var>bugnumber</var> <var>severity</var>
-<li><code>reopen</code> <var>bugnumber</var>
- [ <var>originator-address</var> | <code>=</code> | <code>!</code> ]
-<li><code>forwarded</code> <var>bugnumber</var> <var>address</var>
-<li><code>notforwarded</code> <var>bugnumber</var>
-<li><code>retitle</code> <var>bugnumber</var> <var>new-title</var>
-<li><code>merge</code> <var>bugnumber</var> <var>bugnumber</var> ...
-<li><code>unmerge</code> <var>bugnumber</var>
+ <li><code>close</code> <var>bugnumber</var>
+ <em>(you must separately tell originator why)</em>
+ <li><code>reassign</code> <var>bugnumber</var> <var>package</var>
+ <li><code>severity</code> <var>bugnumber</var> <var>severity</var>
+ <li><code>reopen</code> <var>bugnumber</var>
+ [ <var>originator-address</var> | <code>=</code> | <code>!</code> ]
+ <li><code>forwarded</code> <var>bugnumber</var> <var>address</var>
+ <li><code>notforwarded</code> <var>bugnumber</var>
+ <li><code>retitle</code> <var>bugnumber</var> <var>new-title</var>
+ <li><code>merge</code> <var>bugnumber</var> <var>bugnumber</var> ...
+ <li><code>unmerge</code> <var>bugnumber</var>
</ul>
-<code>reopen</code> with <code>=</code> or no originator address leaves
+
+<p><code>reopen</code> with <code>=</code> or no originator address leaves
the originator as the original submitter; <code>!</code> sets it to
you, the person doing the reopen.
-<p>
+<dl>
$gHTMLSeverityDesc
+</dl>
<hr>
-Other pages:
+
+<p>Other pages:
<ul>
-<li><A href="./">$gBug tracking system main contents page.</A>
-<li><A href="server-request.html">Full documentation of the request mailserver.</A>
-<li><A href="server-control.html">Full documentation of the control mailserver.</A>
-<li><A href="Reporting.html">Instructions for reporting $gBugs.</A>
-<li><A href="Access.html">Accessing the $gBug tracking logs other than by WWW.</A>
-<li><A href="Developer.html">Developers'
-information regarding the $gBug processing system.</A>
-<li><A href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</A>
-<li><A href="db/ix/packages.html">Packages with $gBug reports.</A>
-<li><A href="db/ix/maintainers.html">Maintainers of packages with $gBug reports.</A>
+ <li><a href="./">$gBug tracking system main contents page.</a>
+ <li><a href="server-request.html">Full documentation of the request mailserver.</a>
+ <li><a href="server-control.html">Full documentation of the control mailserver.</a>
+ <li><a href="Reporting.html">Instructions for reporting $gBugs.</a>
+ <li><a href="Access.html">Accessing the $gBug tracking logs other than by WWW.</a>
+ <li><a href="Developer.html">Developers' information regarding the $gBug processing system.</a>
+ <li><a href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</a>
+ <li><a href="db/ix/packages.html">Packages with $gBug reports.</a>
+ <li><a href="db/ix/maintainers.html">Maintainers of packages with $gBug reports.</a>
$gHTMLOtherPageList
</ul>
$gRequestHtml = <<HTML_END
-<html><head>
-<title>$gProject $gBug system - $gBug logs by mail server</title>
-<link rev="made" href="mailto:$gMaintainerEmail">
-</head><body>
-<A name="introduction">
-<h1>Introduction to the $gBug system request server</h1>
-</A>
-
-There is a mailserver which can send the $gBug reports and
+<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+ <title>$gProject $gBug system - $gBug logs by mail server</title>
+ <link rev="made" href="mailto:$gMaintainerEmail">
+</head>
+<body>
+
+<h1><a name="introduction">Introduction to the $gBug system request server</a></h1>
+
+<p>There is a mailserver which can send the $gBug reports and
indices as plain text on request.
-<p>
-To use it you send a mail message to
-<A href="mailto:request\@$gEmailDomain"><code>request\@$gEmailDomain</code></A>.
+<p>To use it you send a mail message to
+<a href="mailto:request\@$gEmailDomain"><code>request\@$gEmailDomain</code></a>.
The <code>Subject</code> of the message is ignored, except
for generating the <code>Subject</code> of the reply.
-<p>
-The body you send should be a series of commands, one per line.
+<p>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.
-<p>
-Any text on a line starting with a hash sign <code>#</code> is
+<p>Any text on a line starting with a hash sign <code>#</code> is
ignored; the server will stop processing when it finds a line starting
with <code>quit</code>, <code>stop</code>, <code>thank</code> or two
hyphens (to avoid parsing a signature). It will also stop if it
<dl>
<dt><code>send</code> <var>bugnumber</var>
<dt><code>send-detail</code> <var>bugnumber</var>
-<dd>
-Requests the transcript for the $gBug report in question.
-<code>send-detail</code> sends all of the `boring' messages in the
-transcript, such as the various auto-acks (you should usually use
-<code>send</code> as well, as the interesting messages are not sent by
-<code>send-detail</code>).
+ <dd>Requests the transcript for the $gBug report in question.
+ <code>send-detail</code> sends all of the `boring' messages in the
+ transcript, such as the various auto-acks (you should usually use
+ <code>send</code> as well, as the interesting messages are not sent by
+ <code>send-detail</code>).
<dt><code>index</code> [<code>full</code>]
<dt><code>index-summary by-package</code>
<dt><code>index-summary by-number</code>
-<dd>
-Request the full index (with full details, and including done and
-forwarded reports), or the summary sorted by package or by number,
-respectively.
+ <dd>Request the full index (with full details, and including done and
+ forwarded reports), or the summary sorted by package or by number,
+ respectively.
<dt><code>index-maint</code>
-<dd>
-Requests the index page giving the list of maintainers with $gBugs (open
-and recently-closed) in the tracking sytem.
+ <dd>Requests the index page giving the list of maintainers with $gBugs
+ (open and recently-closed) in the tracking sytem.
<dt><code>index maint</code> <var>maintainer</var>
-<dd>
-Requests the index pages of $gBugs in the system for all maintainers
-containing the string <var>maintainer</var>. The search term is a
-case insensitive substring. The $gBug index for each matching
-maintainer will be sent in a separate message.
+ <dd>Requests the index pages of $gBugs in the system for all maintainers
+ containing the string <var>maintainer</var>. The search term is a
+ case insensitive substring. The $gBug index for each matching
+ maintainer will be sent in a separate message.
<dt><code>index-packages</code>
-<dd>
-Requests the index page giving the list of packages with $gBugs (open
-and recently-closed) in the tracking sytem.
+ <dd>Requests the index page giving the list of packages with $gBugs (open
+ and recently-closed) in the tracking sytem.
<dt><code>index packages</code> <var>package</var>
-<dd>
-Requests the index pages of $gBugs in the system for all packages
-containing the string <var>package</var>. The search term is a case
-insensitive substring. The $gBug index for each matching package will
-be sent in a separate message.
+ <dd>Requests the index pages of $gBugs in the system for all packages
+ containing the string <var>package</var>. The search term is a case
+ insensitive substring. The $gBug index for each matching package will
+ be sent in a separate message.
<dt><code>send-unmatched</code> [<code>this</code>|<code>0</code>]
<dt><code>send-unmatched</code> <code>last</code>|<code>-1</code>
<dt><code>send-unmatched</code> <code>old</code>|<code>-2</code>
-<dd>
-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.)
+ <dd>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.)
<dt><code>getinfo</code> <var>filename</var>
-<dd>
-Request a file containing information about package(s) and or
-maintainer(s) - the files available are:
-<dl compact>
-<dt><code>maintainers</code>
-<dd>
-The unified list of packages' maintainers, as used by the tracking
-system.
+ <dd>Request a file containing information about package(s) and or
+ maintainer(s) - the files available are:
-$gCreateMaintainers
+ <dl compact>
+ <dt><code>maintainers</code>
+ <dd>The unified list of packages' maintainers, as used by the tracking
+ system.
-<!-- Override file quivilent information -->
+ $gCreateMaintainers
-<dt><code>pseudo-packages.description</code>
-<dt><code>pseudo-packages.maintainers</code>
-<dd>
-List of descriptions and maintainers respectively for pseudo-packages.
-</dl>
+ <!-- Override file quivilent information -->
+
+ <dt><code>pseudo-packages.description</code>
+ <dt><code>pseudo-packages.maintainers</code>
+ <dd>List of descriptions and maintainers respectively for
+ pseudo-packages.
+ </dl>
-<dt><code>refcards</code>
-<dd>
-Requests that the mailservers' reference card be sent in plain ASCII.
+<dt><code>refcard</code>
+
+ <dd>Requests that the mailservers' reference card be sent in plain ASCII.
<dt><code>help</code>
-<dd>
-Requests that this help document be sent by email in plain ASCII.
+
+ <dd>Requests that this help document be sent by email in plain ASCII.
<dt><code>quit</code>
<dt><code>stop</code>
<dt><code>thank</code>...
<dt><code>--</code>...
-<dd>
-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 <code>#</code>, for
-example for the benefit of human readers of your message (reading it
-via the tracking system logs or due to a <code>CC</code> or
-<code>BCC</code>).
+ <dd>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 <code>#</code>, for
+ example for the benefit of human readers of your message (reading it
+ via the tracking system logs or due to a <code>CC</code> or
+ <code>BCC</code>).
<dt><code>#</code>...
-<dd>
-One-line comment. The <code>#</code> must be at the start of the
-line.
+ <dd>One-line comment. The <code>#</code> must be at the start of the
+ line.
<dt><code>debug</code> <var>level</var>
-<dd>
-Sets the debugging level to <var>level</var>, 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.
+ <dd>Sets the debugging level to <var>level</var>, 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.
</dl>
-There is a <A href="server-refcard.html">reference card</A> for the
+<p>There is a <a href="server-refcard.html">reference card</a> for the
mailservers, available via the WWW, in
<code>bug-mailserver-refcard.txt</code> or by email using the
<code>refcard</code> command (see above).
-<p>
-If you wish to manipulate $gBug reports you should use the
+<p>If you wish to manipulate $gBug reports you should use the
<code>control\@gEmailDomain</code> address, which understands a
-<A href="server-control.html">superset of the commands listed
-above</A>. This is described in another document, available on the
-WWW</A>, in the file <code>bug-maint-mailcontrol.txt</code>, or by
+<a href="server-control.html">superset of the commands listed
+above</a>. This is described in another document, available on the
+<a href="server-control.html">WWW</a>, in the file
+<code>bug-maint-mailcontrol.txt</code>, or by
sending <code>help</code> to <code>control\@$gEmailDomain</code>.
-<p>
-In case you are reading this as a plain text file or via email: an
+<p>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
<code>http://$gWebDomain/</code>.
-<p>
<hr>
-Other pages:
+
+<p>Other pages:
<ul>
-<li><A href="./">$gBug tracking system main contents page.</A>
-<li><A href="Reporting.html">Instructions for reporting $gBugs.</A>
-<li><A href="Access.html">Accessing the $gBug tracking logs other than by WWW.</A>
-<li><A href="Developer.html">Developers'
-information regarding the $gBug processing system.</A>
-<li><A href="server-control.html">Developers'
-information - $gBug manipulation using the email control interface.</A>
-<li><A href="server-refcard.html">Mailservers' reference card.</A>
-<li><A href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</A>
-<li><A href="db/ix/packages.html">Packages with $gBug reports.</A>
-<li><A href="db/ix/maintainers.html">Maintainers of packages with $gBug reports.</A>
+ <li><a href="./">$gBug tracking system main contents page.</a>
+ <li><a href="Reporting.html">Instructions for reporting $gBugs.</a>
+ <li><a href="Access.html">Accessing the $gBug tracking logs other than by WWW.</a>
+ <li><a href="Developer.html">Developers' information regarding the $gBug processing system.</a>
+ <li><a href="server-control.html">Developers' information - $gBug manipulation using the email control interface.</a>
+ <li><a href="server-refcard.html">Mailservers' reference card.</a>
+ <li><a href="db/ix/full.html">Full list of outstanding and recent $gBug reports.</a>
+ <li><a href="db/ix/packages.html">Packages with $gBug reports.</a>
+ <li><a href="db/ix/maintainers.html">Maintainers of packages with $gBug reports.</a>
$gHTMLOtherPageList
</ul>
projects / debbugs.git / commitdiff