(Please, Cc: me, I'm not subscribed) Hello,
On Sun, Jul 08, 2007 at 07:17:45PM +0200, Jens Seidel wrote: > > > According to debian-devel archives, bugs are now distributed > > in debian-bugs-dists since November 1996[*] ;-) > > Then, debian-bugs manual must be upgraded: > > http://www.debian.org/doc/manuals/debian-bugs/ch4.html [...] > Since you seem to be a very careful reader could you please send more > updates? The source file is available in > http://cvs.debian.org/ddp/manuals.sgml/debian-bugs/?root=debian-doc Please find a more complete patch in attachment in order to fix other trivial errors or very obsolete informations. Before to begin more important updates, I want to emphasize that debian-bugs manual lacks of a lot of new features now documented in http://www.debian.org/Bugs/* pages. Then I'm not sure it's appropriate to duplicate (and keep uptodate) this informations in this debian-bugs manual... Do you think useful to have a new version of debian-bugs manual to centralize all BTS informations? Or http://www.debian.org/Bugs/* pages are sufficient? (If they are, I suggest to remove debian-bugs manual from WWW pages or tag it as 'deprecated' to avoid confusion with obsolete informations). Regards, -- Gregory Colpart <[EMAIL PROTECTED]> GnuPG:1024D/C1027A0E Evolix - Informatique et Logiciels Libres http://www.evolix.fr/
--- debian-bugs.sgml.ori 2007-07-26 03:41:03.000000000 +0200 +++ debian-bugs.sgml 2007-08-08 02:30:47.000000000 +0200 @@ -33,8 +33,8 @@ <tt>/usr/doc/copyright/GPL</tt> in the Debian GNU/Linux distribution or on the World Wide Web at <tt>http://www.gnu.org/copyleft/gpl.html</tt>. You can also obtain it -by writing to the Free Software Foundation, Inc., 675 Mass Ave, -Cambridge, MA 02139, USA. +by writing to the Free Software Foundation, Inc., 51 Franklin Street, +Fifth Floor Boston, MA 02110-1301, USA. <p> <toc sect> @@ -64,10 +64,11 @@ If you want to report a bug (this can be a bug in any part of the Debian GNU/Linux system, e.g. in a document or a package), please send a mail to - <tt>[EMAIL PROTECTED]</tt>. + <tt>[EMAIL PROTECTED]</tt> or use <em>reportbug</em> + tool. <p> The bug report will be automatically processed by a program, - postet to the <tt>debian-bugs-dist</tt> mailing list (you + posted to the <tt>debian-bugs-dist</tt> mailing list (you can prevent this, see below), and forwarded to the responsible maintainer. Therefore, the bug report should have a pseudo-header at the top so that the bug tracking @@ -302,16 +303,16 @@ <p> The <em>right</em> way to do this is to use the - <tt>X-Debian-CC</tt> header. Add a line like this to your + <tt>X-Debbugs-CC</tt> header. Add a line like this to your message's mail header (not to the pseudo header with the Package field): <example> - X-Debian-CC: [EMAIL PROTECTED] + X-Debbugs-CC: [EMAIL PROTECTED] </example> This will cause the bug tracking system to send a copy of your report to the address(es) specified in the - <tt>X-Debian-CC</tt> line as well as to the + <tt>X-Debbugs-CC</tt> line as well as to the <tt>debian-devel</tt> mailing list. <p> @@ -345,14 +346,14 @@ <p> Copies of the logs are available on the World Wide Web at - <tt>http://www.chiark.greenend.org.uk/debian/Bugs/</tt> and <tt>http://www.debian.org/Bugs/</tt>. - <p> + <!-- Hum, I think this is now wrong + <p> The HTML files containing the bug report logs are available in the WebPages subdirectory of the Debian FTP archive, and will be available on mirror sites that haven't explicitly removed them from their mirror configuration. A web server which is configured to serve this part of - the FTP area as a webtree will provide a local copy of the pages. + the FTP area as a webtree will provide a local copy of the pages. --> <p> There is a mailserver which can send bug reports as plain text on request. To use it send the word <tt/help/ as the sole contents of @@ -486,7 +487,7 @@ <tag><tt> debug level</tt> <item> Sets the debugging level to level, which should be a - nonnegative integer. 0 is no debugging; 1 is usually + non-negative 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 bug system. </taglist> @@ -509,6 +510,7 @@ [EMAIL PROTECTED] <p> + <!-- Hum, I think this is now wrong <sect>Summary postings <p> @@ -532,6 +534,7 @@ the override file. <p> + --> <chapt>Handling of bug reports<p> @@ -541,11 +544,10 @@ If a developer wishes to reply to a bug report without marking the bug as done they may simply reply to the message. Their reply will (by default) go to - <tt><var>nnn</var>@bugs.debian.org</tt> and to the original submitter of the bug - report. The bug tracking system will file the reply with - the rest of the logs for that bug report and forward it to - <tt>debian-bugs-dist</tt>. The bug will not be marked as - done. + <tt><var>nnn</var>@bugs.debian.org</tt> and to the original + submitter of the bug report. The bug tracking system will file the + reply with the rest of the logs for that bug report and forward it to + <tt>debian-bugs-dist</tt>. The bug will not be marked as done. <p> @@ -612,8 +614,8 @@ takes responsibility for it should hit `Reply' in their favourite mailreader, and then edit the `To' field to say <tt><var>nnn</var>[EMAIL PROTECTED]</tt> instead of - <tt><var>nnn</var>@bugs</tt> (<tt><var>nnn</var>-close</tt> is provided as an - alias for <tt><var>nnn</var>-done</tt>). + <tt><var>nnn</var>@bugs</tt> (<tt><var>nnn</var>-close</tt> + is provided as an alias for <tt><var>nnn</var>-done</tt>). <p> @@ -624,9 +626,9 @@ <p> `Done' messages are automatically forwarded to the - <tt>debian-bugs-closed</tt> mailing list, so it may sometimes be worthwhile including - the <tt>debian-devel</tt> mailing list if the other - developers are likely to be interested. + <tt>debian-bugs-closed</tt> mailing list, so it may sometimes be + worthwhile including the <tt>debian-devel</tt> mailing list if the + other developers are likely to be interested. <p> @@ -683,12 +685,12 @@ Close bug report `#bugnumber.' <p> A notification is sent to the user who reported the bug, but - (in contrast to mailing <tt>[EMAIL PROTECTED]</tt>) - the text of the + (in contrast to mailing <tt>[EMAIL PROTECTED]</tt>) the text of the mail which caused the bug 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 bug knows why it is being closed. + The use of this command is therefore deprecated. <p> <tag><tt> reassign bugnumber package</tt> <item>
