Re: Bug reporting proceedure, was Re: Bug#24066: libc6: rsh segfaults as , a result of new libc 2.0.7r2
Dale Scheetz <dwarf@polaris.net> writes:
> What I am requesting is that the submitter of a bug take some time, in
> exchange for the time they expect from the maintainer, and verify that the
> bug has not been reported already. If it has, it is appropriate to send
> the maintainer a confirmation that you also experienced the bug and any
> additional information you can contribute to the solution. This
> confirmation should be CC'd to the original bug report, for continuity
> purposes. But creating an additional report is both confusing and
> administrativly ugly.
This should be mandated (I thought it was). Not that I've always been
as careful as I should have been, but I've tried to be pretty good.
It's extremely helpful (especially for high-traffic-area/critical
packages like X and libc) that you not end up with floods of redundant
bugs.
> I am not looking to stifle information flow about bugs. I am suggesting
> that if the reporter of the bug will spend some time "doing the filing"
> correctly the task becomes possible and the end user and the maintainer
> both benefit.
Not only that, but the user might discover a workaround in the bug log
that helps them out. This might be the best way to "sell" the idea :>
--
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: