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

1998-07-16 Thread Raul Miller
Pat Kennedy <[EMAIL PROTECTED]> wrote: > Just from the point of view of a typical user, eg, me just doing > a quick scan of the debian-user archives doesn't take all that long. > They're very up-to-date, usually just a day or so behind. Browsing > the archives with navigator presents a nice thr

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

1998-07-16 Thread Pat Kennedy
He who wonders discovers that this in itself is wonder. -- M.C. Escher On Wed, 15 Jul 1998, Raul Miller wrote: > Dale Scheetz <[EMAIL PROTECTED]> writes: > > > Well, I disagree with this point of view. Yes, Debian wishes to support > > > newcomers to Linux. That is why we have

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

1998-07-16 Thread Bill Bell
gt; >Cc: Manoj Srivastava <[EMAIL PROTECTED]>, > Rob Browning <[EMAIL PROTECTED]>, debian-devel@lists.debian.org, > debian-user@lists.debian.org, debian-policy@lists.debian.org >Subject: Re: Bug reporting proceedure, was Re: Bug#24066: libc6: rsh segfaults as , a result of new li

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

1998-07-16 Thread Raul Miller
Dale Scheetz <[EMAIL PROTECTED]> 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

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

1998-07-15 Thread John Goerzen
Dale Scheetz <[EMAIL PROTECTED]> writes: > Suggesting, even strongly, that it is proper proceedure when submitting a > bug, to research the bug reporting system first, and provide useful > information second, doesn't seem onerous to me, and has several practical > uses for the bug submitter, as we

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

1998-07-15 Thread John Goerzen
Dale Scheetz <[EMAIL PROTECTED]> 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 familia

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

1998-07-01 Thread Ed Cogburn
Larry Walewski wrote: > > I think your ideas are great. I too am a newbie to Linux. First tried > installing > Caldera's OpenLinux Lite, but couldn't get it to work on my machine with > only 5 megs (probably could've with a little more work). Someone then > pointed me, thankfully, to Debian!

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

1998-06-30 Thread Dale Scheetz
On 30 Jun 1998, Manoj Srivastava wrote: > Hi, > >>"Dale" == Dale Scheetz <[EMAIL PROTECTED]> writes: > > Dale> I never said "demand" anything. I am talking about "higher > Dale> education" for users, not binding them to a post in the town > Dale> square and giving them 20 lashes. > > ;-

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

1998-06-30 Thread Manoj Srivastava
Hi, >>"Dale" == Dale Scheetz <[EMAIL PROTECTED]> writes: Dale> I never said "demand" anything. I am talking about "higher Dale> education" for users, not binding them to a post in the town Dale> square and giving them 20 lashes. ;-) Well said. I agree with this post, completely. (If yo

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

1998-06-30 Thread Dale Scheetz
On 30 Jun 1998, Manoj Srivastava wrote: > Hi, > >>"Dale" == Dale Scheetz <[EMAIL PROTECTED]> writes: > > Dale> On 29 Jun 1998, Manoj Srivastava wrote: > > >> Umm, no. It would be nice if they did it, but a novce user is > >> perfectly free to just file a bug report. I know I often do. I find

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

1998-06-30 Thread Ed Cogburn
Dale Scheetz wrote: > > On 29 Jun 1998, Manoj Srivastava wrote: > > > Hi, > > >>"Rob" == Rob Browning <[EMAIL PROTECTED]> writes: > > > > Rob> Dale Scheetz <[EMAIL PROTECTED]> writes: > > >> What I am requesting is that the submitter of a bug take some time, in > > >> exchange for the time the

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

1998-06-30 Thread Adam P. Harris
Geeze, the crossposting is horrendous. I don't see this as a policy issue, so followups to debian-devel or debian-user only please. Dale Scheetz <[EMAIL PROTECTED]> writes: > On 29 Jun 1998, Manoj Srivastava wrote: > > Make bug reporting any more onerous than it is, and peole > > merely sto

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

1998-06-30 Thread Manoj Srivastava
Hi, >>"Dale" == Dale Scheetz <[EMAIL PROTECTED]> writes: Dale> On 29 Jun 1998, Manoj Srivastava wrote: >> Umm, no. It would be nice if they did it, but a novce user is >> perfectly free to just file a bug report. I know I often do. I find >> an error, usually that by itself is a frustrating e

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

1998-06-30 Thread Dale Scheetz
On 29 Jun 1998, Manoj Srivastava wrote: > Hi, > >>"Rob" == Rob Browning <[EMAIL PROTECTED]> writes: > > Rob> Dale Scheetz <[EMAIL PROTECTED]> 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 veri

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

1998-06-30 Thread Rob Browning
Manoj Srivastava <[EMAIL PROTECTED]> writes: > Make bug reporting any more onerous than it is, and peole > merely stop filing reports. I suppose there is something to that. > For the most part the maintainer knows the bugs on a package > better than anyone else, and the maintainers

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

1998-06-30 Thread Manoj Srivastava
Hi, >>"Rob" == Rob Browning <[EMAIL PROTECTED]> writes: Rob> Dale Scheetz <[EMAIL PROTECTED]> 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

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

1998-06-29 Thread Rob Browning
Dale Scheetz <[EMAIL PROTECTED]> 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 t

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

1998-06-29 Thread Dale Scheetz
Before I start whining ;-) I want to thank Steve for the useful information in his bug report, and although his bug report is a duplicate report, and that is what I am here to complain about, I appreciate his report and am not directing this at him specifically. I have never experienced this probe