Steve Langasek wrote:
The testing scripts only check the installability of arch: all packages on one of our architectures -- for obvious reasons, that architecture is i386.
It's more the other way around: the testing scripts would check the installability of arch: all packages on all architectures, but the only one where that's remotely feasible is i386. :( Solving this probably requires some dak magic that'll automatically put some arch:all packages only in some arches, rather than all of them. It's not remotely clear what that magic would look like though.
Anyway, f your package only actually works on one arch, there's no point marking it arch: all, and generally better not to.
Cheers, aj