More patches to www.debian.org/Bugs
The following patches fix a bunch of open bugs against the BTS and
sync (for the most part) the b.d.o documentation up with the
documentation that is actually in debbugs.
If there are any questions, please let me know.
Don Armstrong
--
"Facts" are the refuge of people unwilling to reassess what they hold
to be "True".
http://www.donarmstrong.com http://rzlab.ucr.edu
? Bugs/Access.en.html
? Bugs/Developer.en.html
? Bugs/Reporting.en.html
? Bugs/bugs.css_old
? Bugs/index.en.html
? Bugs/pseudo-packages.en.html
? Bugs/server-control.en.html
? Bugs/server-refcard.en.html
? Bugs/server-request.en.html
Index: Bugs/Reporting.wml
===================================================================
RCS file: /cvs/webwml/webwml/english/Bugs/Reporting.wml,v
retrieving revision 1.46
diff -u -r1.46 Reporting.wml
--- Bugs/Reporting.wml 23 Aug 2005 18:09:51 -0000 1.46
+++ Bugs/Reporting.wml 17 May 2006 06:34:07 -0000
@@ -166,8 +166,7 @@
<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 (<strong>not</strong> to the pseudo header with the
-<code>Package</code> field):</P>
+message's mail header:</P>
<pre>
X-Debbugs-CC: other-list@cosmic.edu
</pre>
@@ -222,6 +221,37 @@
as described in the
<a href="Developer#tags">developers' documentation</a>.
Separate multiple tags with commas, spaces, or both.</p>
+
+<h2><a name="miscpseudoheaders">Other pseudo headers (primarily of
+interest to package maintainers)</a></h2>
+
+<pre>
+Forwarded: <var>foo@example.com</var>
+</pre>
+
+will mark the newly submitted bug as forwarded to foo@example.com. See
+<a href="Developer#forward">Recording that you have passed on a bug
+report</a> in the developers' documentation for details.
+
+<pre>
+Owner: <var>foo@example.com</var>
+</pre>
+
+will indicate that foo@example.com is now responsible for fixing this
+bug. See <a href="Developer#owner">Changing bug ownership</a> in the
+developers' documentation for details.
+
+<pre>
+Source: <var>foopackage</var>
+</pre>
+
+the equivalent of <code>Package:</code> for bugs present in the source
+package of foopackage; for most bugs in most packages you don't want
+to use this option.</p>
+
+<p>Finally, if your MUA doesn't allow you to edit the headers, you can
+set the various <code>X-Debbugs-</code> headers in the
+<a href="#pseudoheader">pseudo-headers</a>.</p>
<h2>Different submission addresses (minor or mass bug reports)</h2>
Index: Bugs/server-control.wml
===================================================================
RCS file: /cvs/webwml/webwml/english/Bugs/server-control.wml,v
retrieving revision 1.49
diff -u -r1.49 server-control.wml
--- Bugs/server-control.wml 29 Jul 2005 17:24:31 -0000 1.49
+++ Bugs/server-control.wml 17 May 2006 06:34:07 -0000
@@ -160,7 +160,7 @@
<p>For <A href="Developer#severities">their meanings</A> please
consult the general developers' documentation for the bug system.
-<dt><code>clone</code> <var>bugnumber</var> [ <var>new IDs</var> ]
+<dt><code>clone</code> <var>bugnumber</var> <var>NewID</var> [ <var>new IDs</var> ... ]
<dd>The clone control command allows you to duplicate a bug report. It is
useful in the case where a single report actually indicates that multiple
@@ -213,6 +213,12 @@
<P>Merged reports are all expired simultaneously, and only when all of
the reports each separately meet the criteria for expiry.
+
+<dt><code>forcemerge</code> <var>bugnumber</var> <var>bugnumber</var> ...
+ <dd>Forcibly merges two or more $gBug reports. The first bug is
+ chosen as the master bug, and its seetings are assigned to the bugs
+ listed next in the command. See the text above for a description of
+ what merging means.
<dt><code>unmerge</code> <var>bugnumber</var>
<dd>
Index: Bugs/server-refcard.wml
===================================================================
RCS file: /cvs/webwml/webwml/english/Bugs/server-refcard.wml,v
retrieving revision 1.31
diff -u -r1.31 server-refcard.wml
--- Bugs/server-refcard.wml 23 Oct 2005 11:33:48 -0000 1.31
+++ Bugs/server-refcard.wml 17 May 2006 06:34:08 -0000
@@ -49,11 +49,14 @@
<var>address</var> | <code>!</code>
<li><code>noowner</code> <var>bugnumber</var>
<li><code>retitle</code> <var>bugnumber</var> <var>new-title</var>
-<li><code>clone</code> <var>bugnumber</var> [ <var>new IDs</var> ]
+<li><code>clone</code> <var>bugnumber</var> <var>NewID</var> [ <var>new IDs</var> ... ]
<li><code>merge</code> <var>bugnumber</var> <var>bugnumber</var> ...
<li><code>unmerge</code> <var>bugnumber</var>
-<li><code>tags</code> <var>bugnumber</var>
+<li><code>forcemerge</code> <var>bugnumber</var> <var>bugnumber</var> ...
+<li><code>tag</code> <var>bugnumber</var>
[ <code>+</code> | <code>-</code> | <code>=</code> ] <var>tag</var> [ <var>tag</var> ... ]
+<li><code>block</code> <var>bugnumber</var> <code>by</code> <var>bug</code> ...
+<li><code>unblock</code> <var>bugnumber</var> <code>by</code> <var>bug</code> ...
<li><code>close</code> <var>bugnumber</var> [ <var>fixed-version</var> ]
<strong>(deprecated – you must separately tell originator why, see
“<a href="Developer#closing">Closing bug reports</a>”
Reply to: