On Sat, Feb 25, 2006 at 11:30:16AM -0700, Shaun Jackman wrote:
> A grave bug has been file against a package I maintain pointing out
> that the package does not work on AMD64 and in fact never has, even
> though it builds on AMD64. Since it turns out this package has never
> worked on AMD64, this bug is not a regression, but the status-quo.
> Should such a bug be grave, or merely important?

As Steve has pointed out already, packages that don't work on
amd64 are considered to be grave bugs.

Anyway, not having even idea which package it is, it's probably
affecting more than 1 arch.  Like for instance all 64 bit arches.
So it should be an RC bug for those too.

I suggest you try to find out what kind of problem it is, which
shouldn't be that hard.  And depending on that you can do various
things, like fixing it.

In any case, it's always a good idea to do some regression tests
during build, and make it fail to build in case it finds an
error.  That way you can be a little more sure that you can do
basic things with it.  It also means that if it's failing, no
binaries that aren't working end up in the archive, and you don't
end up with grave bugs.

In case there are more architectures that have the same problem,
you'll have to file a request to remove those binaries from
unstable after you've made sure that no broken binaries will get
upload to unstable.


Kurt


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.or
g

[ Post a follow-up to this message ]