Re: Bug reporting proceedure, was Re: Bug#24066: libc6: rsh segfaults as , a result of new libc 2.0.7r2

[Raul Miller <rdm@test.legislate.com>]

Dale Scheetz <dwarf@polaris.net> writes:
> > Well, I disagree with this point of view. Yes, Debian wishes to support
> > newcomers to Linux. That is why we have debian-user. We have a
> > responsibility to those new users to "train" them to be "free" users.
> > They can only do that if they become familiar with the ins and outs of the
> > "Debian Way".

John Goerzen <jgoerzen@complete.org> wrote:
> But by actually submitting a bug report in the first place, they're
> already helping.  The maintainer can either fix it or open a dialogue
> up with the submitter if more information is needed.

Slow down folks.  [Er... except on getting hamm released.]

Dale is talking from the viewpoint of being libc maintainer.  John
is talking about the application view of the system.

In general, I agree with John's point of view. However, before reporting
that something about libc is broken, it's worthwhile doing a certain
amount of research. [If you find that the point you're researching is
undocumented, or that the documentation doesn't adequately describe the
situation, that may itself be a bug, of course.]

That said, "info libc" doesn't even mention the debian bug tracking
system, let alone that the web pages should be consulted before
reporting a bug on libc.

-- 
Raul


--  
Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null