Bug#189157: http://www.debian.org/Bugs/Reporting: It is not clear how/if bugs are forwarded upstream
On Sun, Apr 20, 2003 at 10:28:41PM +0200, Frank Lichtenheld wrote:
> > > What to do as a reporter when the maintainer doens't forward a bug, and
> > > it's clearly an upstream problem? Maybe this shouldn't be mentioned on
> > > www.debian.org, but I am curious anyway.
> > You can always send mail to <bugnumber>@bugs.debian.org asking for it to be
> > examined and forwarded. This will be seen by the maintainer of the package
> > and by other developers who track bugs. If this doesn't produce any result,
> > you can send mail to email@example.com asking for the bug to be
> > looked at.
> > I agree that we could polish up the docs about these issues.
> Comments welcomed:
> --- Reporting.wml 13 Apr 2003 15:15:42 -0000 1.36
> +++ Reporting.wml 20 Apr 2003 20:21:59 -0000
> @@ -24,7 +24,12 @@
> <p>If you'd like to send a copy of your bug report to additional recipients
> (such as mailing lists), you shouldn't use the usual e-mail headers, but
> -<a href="#xcc">a different method, described below</a>.</p>
> +<a href="#xcc">a different method, described below</a>. Please note
> +that it is normally not recommended to report a bug both to the debian
> +bug tracking system and the program's original bug address (or other
> +bug tracking systems like bugzilla or Sourceforge.net's one): The
> +maintainer will forward your report when needed. This helps to
> +avoid duplicate reports.</p>
Personally I don't think we should be as explicit as that. We may not
actually have consensus among developers for such a statement, and I can
certainly think of cases where filing some bugs upstream rather than having
the Debian maintainer sort them out first would be preferable.
(And once again, don't tack on things to the ends of paragraphs unless
they're inseparable. Starting a new paragraph is _fine_ :)
2. That which causes joy or happiness.