There are many schools of thought on handling bugs like
these in Debian. There even has been some bug wars of
closing and reopening the same bug repeatedly, because of
these differences. So, there is no right answer, everybody
just Does The Right Thing and hopes it will be accepted.
That said, whe
Le Fri, Sep 10, 1999 at 12:54:23AM +0100, Frankie Fisher écrivait:
> Maybe you could downgrade it or something.
No please close it if :
- the bug submitter doesn't respond to your questions
- you can't duplicate the problem with the last version
- the bug is quite old
- nobody else complained abo
On Thu, Sep 09, 1999 at 08:12:19PM -0400, Ben Darnell wrote:
> But in this case, there is no evidence that the bug actually exists in
> this package. The bug can't be reproduced, and the submitter can't be
> reached for additional information. If the bug was in this package, it
You could possib
On Fri, Sep 10, 1999 at 12:54:23AM +0100, Frankie Fisher wrote:
> > >
> > > Can I just close this bug?
> > >
> >
> > Sure, someone can always re-open it.
>
> Not that I am an authority on the subject (or have ever even been in a
> position to close a bug as I'm not even a maintainer yet), but t
> >
> > Can I just close this bug?
> >
>
> Sure, someone can always re-open it.
Not that I am an authority on the subject (or have ever even been in a
position to close a bug as I'm not even a maintainer yet), but that would be
tantamount to denying that the problem exists.
And debian prides it
On 09-Sep-99 Brent Fulgham wrote:
> I have a bug filed against an old version of premail that
> is about 850 days old. I can neither recreate the
> problem, nor get feedback from the filer that the
> problem exists (it's a really vague report in which
> she lost some mail, thought it *might* be
6 matches
Mail list logo
