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:
> > NO! Let's not annoy bug submitters!
>
> But annoying developers is just fine ;-)
Yes. Because the usual reason for something to not be closed is that
the developer either forgot to close it or hasn't done anything about
it yet.
> When I try to get respondents to tell me whether the bug is still present
> in the current version, the most often reply is a bounced message.
Well I would say that with the large libc5 -> libc6 change, if that
happens, nobody would complain with you closing the bug.
> > I do not want to get any more mail than I already do, especially if
> > it's not my problem.
>
> You would report a bug that was not a problem for you? I report bugs
I think you misunderstand what I meant. By "not my problem" I meant
that it's not my problem that the bug is still in the database after x
(where x is something large) amount of days -- it's the maintainer's
problem. Of course, the original report probably is a problem for me.
> because they are a problem. While I hope that their repair will help more
> folks than myself, it is my needs that prompt the bug report. Why
> shouldn't I hold some responsibility for having reported the bug?
The submitter certainly should be available to answer the maintainer's
questions about the report and provide more info if necessary. I'm
not sure what else should be required of them..?
--
John Goerzen Linux, Unix consulting & programming jgoerzen@complete.org |
Developer, Debian GNU/Linux (Free powerful OS upgrade) www.debian.org |
----------------------------------------------------------------------------+
Visit the Air Capitol Linux Users Group on the web at http://www.aclug.org
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: