Bug#446099: clarify /Bugs/reporting
On Wed, 10 Oct 2007, martin f krafft wrote:
> ? Reporting.wml.patch
> Index: Reporting.wml
> ===================================================================
> RCS file: /cvs/webwml/webwml/english/Bugs/Reporting.wml,v
> retrieving revision 1.59
> diff -u -r1.59 Reporting.wml
> --- Reporting.wml 12 Sep 2007 23:54:02 -0000 1.59
> +++ Reporting.wml 10 Oct 2007 13:41:27 -0000
> @@ -1,6 +1,8 @@
> #use wml::debian::template title="Debian BTS - reporting bugs" NOHEADER=yes NOCOPYRIGHT=true
>
> -<h1>How to report a bug in Debian using reportbug</h1>
> +<h1>How to report a bug in Debiang</h1>
^
> +
> +<h2>Use reportbug</h2>
These were split out this way because using reportbug is the
recommended way, and the instructions below do not apply in the normal
case if you're using
> <a name="reportbug"></a>
> <p>We strongly recommend that you report bugs in Debian using the
> @@ -15,13 +17,9 @@
> href="mailto:debian-user@lists.debian.org";> Debian user mailing
> list</a>.</p>
>
> -<h1>How to report a bug in Debian using email</h1>
> -
> -
> <h2>Important things to note <strong>before</strong> sending your bug
> report</h2>
>
> -
> <a name="whatpackage"></a>
> <h3>What package does your bug report belong to?</h3>
> <p>You need to know what package your bug report should be filed
> @@ -63,12 +61,13 @@
> Debian. If necessary, the maintainer of the package will forward the
> bug upstream.</p>
>
> -
> <h2>Sending the bug report via e-mail</h2>
>
> <p>You can report bugs in Debian by sending an e-mail to
> <a href="mailto:submit@bugs.debian.org";><code>submit@bugs.debian.org</code></a>
> -with a special format described below.</p>
> +with a special format described below. <code>reportbug</code> (<a
> +href="#reportbug">see above</a>) will properly format the e-mails for you;
> +please use it!</p>
This is needless because it's already explained above.
> <h3>Headers</h3>
> <p>Like any e-mail you should include a clear, descriptive
> @@ -371,10 +370,14 @@
> <h2><a name="findpkgver">Using <code>dpkg</code> to find the package and
> version for the report</a></h2>
>
> -<p>If you are reporting a bug in a command, you can find out which
> -package installed it by using <code>dpkg --search</code>. You can
> -find out which version of a package you have installed by using
> -<code>dpkg --list</code> or <code>dpkg --status</code>.
> +<p>When using <code>reportbug</code> to report a bug in a command, say
> +<code>grep</code>, the following will automatically select the right package
> +and let you write the report right away: <code>reportbug --file $(which
> +grep)</code></p>
> +
> +<p>You can also find out which package installed it by using <code>dpkg
> +--search</code>. You can find out which version of a package you have
> +installed by using <code>dpkg --list</code> or <code>dpkg --status</code>.
> </p>
And likewise, these commands only apply when you're not using
reportbug; mentioning it here is useless.
Don Armstrong
--
Certainly the game is rigged. Don't let that stop you. If you don't
bet, you can't win.
-- Robert Heinlein _Time Enough For Love_ p240
http://www.donarmstrong.com http://rzlab.ucr.edu
Reply to: