From 7efcdc08506f27b1441a20554817781653cae7a0 Mon Sep 17 00:00:00 2001 From: joy <> Date: Wed, 5 Mar 2003 18:20:30 -0800 Subject: [PATCH] [project @ 2003-03-05 18:20:30 by joy] various fixes from webwml --- html/Reporting.html.in | 159 ++++++++++++++++++++++++++++------------- 1 file changed, 108 insertions(+), 51 deletions(-) diff --git a/html/Reporting.html.in b/html/Reporting.html.in index 733fd25..4e31b8b 100644 --- a/html/Reporting.html.in +++ b/html/Reporting.html.in @@ -9,58 +9,80 @@ $gReportingHtml = <How to report a $gBug in $gProject -

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

Important things to note before sending

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). +different packages - in a single $gBug report. + +

You should check if your $gBug report has already been filed by someone +else before submitting it. Lists of currently outstanding $gBugs are +available on the World Wide Web and +elsewhere - see other documents for details. +You can submit your comments to an existing $gBug report +#<number> by sending e-mail to +<number>\@$gEmailDomain

+ +

If you can't seem to determine which package contains the problem, +please send e-mail to the +$gMaintainerEmail asking for advice. +$gHTMLPseudoDesc +

-

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

If you'd like to send a copy of your $gBug report to additional +recipients (such as mailing lists), you shouldn't use the usual e-mail +headers, but a different method, described below.

-

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.) -$gHTMLFindPackage +

Sending the bug report using an automatic bug report tool

-

See below for further requirements. +

There is a program that was developed in Debian to help reporting +$gBug reports, it's called +reportbug. +It will guide you through the bug reporting process step by step, +and probably ease filing bugs that way.

-$gHTMLPseudoDesc -

Example

+

Sending the bug report via e-mail

-

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-16
+
Send mail to
+submit\@$gEmailDomain,
+as described below.

 
-  When I invoke `hello' without arguments from an ordinary shell
-  prompt it prints `goodbye', rather than the expected `hello, world'.
-  Here is a transcript:
+
Of course, like with 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!

 
-  $ hello
-  goodbye
-  $ /usr/bin/hello
-  goodbye
-  $
+
You need to put a pseudo-header at the start
+of the body of the message. That means that the first line of the message
+body should say:

 
-  I suggest that the output string, in hello.c, be corrected.
+
+Package: <something>
+

 
-  I am using Debian GNU/Linux 2.2, kernel 2.2.17-pre-patch-13
-  and libc6 2.1.3-10.
+
Replace <something> with the name of the package which
+has the $gBug.

+
+
The second line of the message should say:

+
+
+Version: <something>
 

 
-
Please include in your report:

+
Replace <something> with the version of the package.

+
+
You need to supply a correct Package line in the
+pseudo-header in order for the $gBug tracking system to deliver the message
+to the package's maintainer.

+
+$gHTMLFindPackage
+
+
The pseudo-header fields should start at the very start of their lines.

+
+$gHTMLPseudoDesc
+
+
Please include in your report: