12
12
<p>In addition to the mailserver on <code>request\@$gEmailDomain</code>
13
13
which allows the retrieval of $gBug data and documentation by email,
14
14
there is another server on <code>control\@$gEmailDomain</code> which
15
also allows $gBug reports to be manipulated in various ways.
15
also allows $gBug reports to be manipulated in various ways.</p>
17
17
<p>The control server works just like the request server, except that it
18
18
has some additional commands; in fact, it's the same program. The two
19
19
addresses are only separated to avoid users making mistakes and
20
causing problems while merely trying to request information.
20
causing problems while merely trying to request information.</p>
23
23
<a href="server-request.html#introduction">introduction to the request
24
24
server</a> available on the World Wide Web, in the file
25
<code>bug-maint-mailcontrol.txt</code>, or by sending
25
<code>bug-log-mailserver.txt</code>, or by sending
26
26
<code>help</code> to either mailserver, for details of the basics of
27
27
operating the mailservers and the common commands available when
28
mailing either address.
28
mailing either address.</p>
30
30
<p>The <a href="server-refcard.html">reference card</a> for the
31
31
mailservers is available via the WWW, in
32
32
<code>bug-mailserver-refcard.txt</code> or by email using the
33
<code>refcard</code> command).
33
<code>refcard</code> command.</p>
35
<h1>Commands available only at the control mailserver</h1>
35
<h1>Commands available at the control mailserver</h1>
39
<dt><code>close</code> <var>bugnumber</var>
41
<dd>Close $gBug report #<var>bugnumber</var>.
43
<p>A notification is sent to the user who reported the $gBug, but (in
44
contrast to mailing <var>bugnumber</var><code>-done@$gEmailDomain</code>) the
45
text of the mail which caused the $gBug to be closed is <em>not</em>
46
included in that notification. The maintainer who closes a report
47
should ensure, probably by sending a separate message, that the user
48
who reported the $gBug knows why it is being closed.
50
39
<dt><code>reassign</code> <var>bugnumber</var> <var>package</var>
52
41
<dd>Records that $gBug #<var>${gBug}number</var> is a $gBug in <var>package</var>.
77
66
<p>If the $gBug is not closed then reopen won't do anything, not even
78
change the originator. There is no way to change the originator of an
79
open $gBug report (this is deliberate, so that you can't have a $gBug be
80
closed and then deleted $gRemoveAge days later without someone being told about
67
change the originator. To change the originator of an open $gBug report,
68
use the <code>submitter</code> command; note that this will inform the
69
original submitter of the change.
71
<dt><code>submitter</code> <var>bugnumber</var>
72
<var>originator-address</var> | <code>!</code>
74
<dd>Changes the originator of #<var>bugnumber</var> to
75
<var>originator-address</var>.
77
<p>If you wish to become the new originator of the report you can use
78
the <code>!</code> shorthand or specify your own email address.</p>
80
<p>While the <code>reopen</code> command changes the originator of other
81
bugs merged with the one being reopened, <code>submitter</code> does not
82
affect merged bugs.</p>
83
84
<dt><code>forwarded</code> <var>bugnumber</var> <var>address</var>
97
98
<dt><code>retitle</code> <var>bugnumber</var> <var>new-title</var>
99
100
<dd>Changes the title of a $gBug report to that specified (the default is
100
the <code>Subject</code> mail header from the original report.
101
the <code>Subject</code> mail header from the original report).
102
103
<p>Unlike most of the other $gBug-manipulation commands when used on one of
103
104
a set of merged reports this will change the title of only the
112
113
<p>For <a href="Developer.html#severities">their meanings</a> please
113
114
consult the general developers' documentation for the $gBug system.
116
<dt><code>clone</code> <var>bugnumber</var> [ <var>new IDs</var> ]
118
<dd>The clone control command allows you to duplicate a $gBug report. It is
119
useful in the case where a single report actually indicates that multiple
120
distinct $gBugs have occurred. "<var>New IDs</var>" are negative numbers,
121
separated by spaces, which may be used in subsequent control commands to
122
refer to the newly duplicated $gBugs. A new report is generated for each
125
<p>Example usage:</p>
130
retitle -1 foo: foo sucks
132
retitle -2 bar: bar sucks when used with foo
136
retitle -3 foo: foo sucks
115
140
<dt><code>merge</code> <var>bugnumber</var> <var>bugnumber</var> ...
117
142
<dd>Merges two or more $gBug reports. When reports are merged opening,
122
147
<p>Before $gBugs can be merged they must be in exactly the same state:
123
148
either all open or all closed, with the same forwarded-to upstream
124
author address or all not marked as forwarded, and all assigned to the
149
author address or all not marked as forwarded, all assigned to the
125
150
same package or package(s) (an exact string comparison is done on the
126
package to which the $gBug is assigned). If they don't start out in the
127
same state you should use <code>reassign</code>, <code>reopen</code>
128
and so forth to make sure that they are before using
151
package to which the $gBug is assigned), and all of the same severity.
152
If they don't start out in the same state you should use
153
<code>reassign</code>, <code>reopen</code> and so forth to make sure
154
that they are before using <code>merge</code>.
131
156
<p>If any of the $gBugs listed in a <code>merge</code> command is already
132
157
merged with another $gBug then all the reports merged with any of the
134
159
is reflexive, transitive and symmetric.
136
161
<p>Merging reports causes a note to appear on each report's logs; on the
137
WWW pages this is includes links to the other $gBugs.
162
WWW pages this includes links to the other $gBugs.
139
164
<p>Merged reports are all expired simultaneously, and only when all of
140
165
the reports each separately meet the criteria for expiry.
164
189
The default action is adding.
166
191
<p>Available tags currently include <code>patch</code>, <code>wontfix</code>,
167
<code>moreinfo</code>, <code>unreproducible</code>, <code>fixed</code>,
168
and <code>stable</code>.
192
<code>moreinfo</code>, <code>unreproducible</code>, <code>help</code>,
193
<code>pending</code>, <code>fixed</code>, <code>security</code>,
194
<code>upstream</code>, <code>potato</code>, <code>woody</code>,
196
<code>sid</code> and <code>experimental</code>.
170
198
<p>For <a href="Developer.html#tags">their meanings</a> please consult the
171
199
general developers' documentation for the $gBug system.
201
<dt><code>close</code> <var>bugnumber</var>
203
<dd>Close $gBug report #<var>bugnumber</var>.
205
<p>A notification is sent to the user who reported the $gBug, but (in
206
contrast to mailing <var>bugnumber</var><code>-done@$gEmailDomain</code>) the
207
text of the mail which caused the $gBug to be closed is <strong>not</strong>
208
included in that notification. The maintainer who closes a report
209
should ensure, probably by sending a separate message, that the user
210
who reported the $gBug knows why it is being closed.
211
The use of this command is therefore deprecated.
213
<dt><code>quit</code>
214
<dt><code>stop</code>
215
<dt><code>thank</code>...
216
<dt><code>--</code>...
218
<dd>Tells the control server to stop processing the message; the remainder
219
of the message can include explanations, signatures or anything else,
220
none of it will be detected by the control server.
222
<dt><code>#</code>...
224
<dd>One-line comment. The <code>#</code> must be at the start of the line.
added
removed
html/server-control.html.in
