Re: Bug#154829: Is a bug "grave" if the package is unusable for at least two architectures (Was: Bug#154829: Aido problems on 64 bit architectures)
On Fri, Jun 13, 2003 at 12:08:49AM +0200, Wouter Verhelst <firstname.lastname@example.org> wrote:
> I agree with Andreas here. I feel that 'major impact, does not render
> unusable to everyone' should be interpreted as 'the bug makes things go
> all whacky, making it hard to do useful stuff with the program, although
> it's probably still useful to some users in its current state, with the
> bug'. Not something such as "if there's any user on this planet who can
> still use the program, it's not a grave bug", since in that case, grave
> bugs would be reserved for packages that segfault at startup on *all*
My logic is that it segfaults on startup on very few architectures,
unless someone has information to the contrary (so far I've heard about
two). I don't contend that, say, one user being able to use it means
that it's not grave; I do contend that *most* users can use it.
That said, I'm not interested enough in keeping this bug at "important"
to deal with getting two mail from every friggin' -devel subscriber
(hint: the maintainer gets mail to email@example.com; Cc:ing me accomplishes
nothing except further annoying me). I'll leave it as-is, though I'm
still not convinced.
Mike Markley <firstname.lastname@example.org>
GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F36A 3B04 7084
For future reference - don't anybody else try to send patches as vi scripts,
please. Yes, it's manly, but let's face it, so is bungee-jumping with the
cord tied to your testicles.
- Linus Torvalds