Re: On bug reporting
Enrico Zini wrote:
>I would like to know if there are guidelines for bug reporting: I use
>debian unstable, and I find bugs, but I don't report most of them for many
>reasons.
...
> - Evident bugs
>
> I work mainly offline, so I don't have constant access to
> bugs.debian.org, and usually can't know when a bug has already been
> reported.
> When I find a bug in a package that is likely to already have been
> reported, I don't do it to avoid the possibility of flooding the bug
> database with reduntant reports.
...
> I only report these bugs when I see the problem persisting after a week
> or two. Should I always report it, instead?
I suggest you write out a bug-report, at least in outline, and check the
BTS when you can to see if it has been reported. If it is not reported,
file a bug; if it is, check the bug report to see if you can add any
relevant information.
> - Pedantic bugs
>
> Sometimes I notice something that should be different, but I don't know
> if it is to be considered as a bug, and I don't report it.
...
> Should I be on the safe side and risk reporting a non-bug, or should I
> be on the other safe side and risk non-reporting a bug?
If you're not sure if something is a bug, you can mail
<package>@packages.debian.org; I don't mind receiving such mails, though
I don't promise to do more than read them. If you're not sure about
the bug, this saves you from leaving your misunderstandings on public
record!
> - Non-Debian small bugs
>
> Sometimes I find small bugs that are clearly to be reported upstream,
...
> It would be very handy to file a `whishlist' bug to the Debian BTS,
> knowing they are eventually reported upstream, but I don't do it to
> avoid flooding the BTS with non-debian-related items.
Upstream bugs should be checked against the upstream bug list or TODO list
or FAQ. If the behaviour is apparently unreported, report it to the
Debian BTS; the maintainer should verify your report and pass it on.
Some bug reports that I get are actually down to PEBKAC[1] but I
don't mind that, because we all have to learn; even if the user has
read and misunderstood the documentation, it is useful to know that
that piece of documentation can be misunderstood.
Upstream bugs are not "non-Debian issues". If the package is in Debian,
we have a responsibility to try and make it as good as possible. This
includes packages' native defects.
=======
[1] PEBKAC: problem exists between keyboard and chair - Illiad
--
Oliver Elphick Oliver.Elphick@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
========================================
"And, behold, I come quickly; and my reward is with me,
to give every man according as his work shall be."
Revelation 22:12
Reply to: