Steve Langasek <[EMAIL PROTECTED]> writes:

> A binary package that's unusable on the architecture it's built for is
> 'grave'.  An arch: all package (like balazar) that isn't usable on one
> particular arch may be serious (if the maintainer thinks it's a blocker for
> the release), or it may be important, or it may be wishlist...

If so, there no more possibility to differenciate a binary package built
for all arches which crash on *ALL* architecture, and is really
unusuable, and one which is having problems with a specific
architecture. I cannot see how i should be considering soya "unusable or
mostly so" when it works perfectly on so much architectures...

Btw, if nobody really helps, i'd remove support for amd64 before
release. I see no reason to have Slune and Balazar (and the coming
Balazar Brothers) to be removed from the archive for this.

-- 
Marc Dequènes (Duck)

Attachment: pgpyLndjykEnd.pgp
Description: PGP signature

Reply via email to