On Sat, Jan 13, 2018 at 01:11:11PM +0530, Chris Lamb wrote: > As an aside, I was wondering whether a Lintian check for this would be sane, > like an inverse of "arch-independent-package-contains-binary-or-object"?
I think not.
There are several packages in the archive that totally ought to be
arch:all, but are otherwise arch:any due to how architectures
costrainsts propagates in a Multi-Arch situation (go ask helmut for more
details). It's a workaround, but it's the best way to deal with that
particular problem, I'd rather not have lintian warn about it.
Having a package arch:any instead of arch:all doesn't really inpact
anything except some extra buildd time and mirror space (and looks odd
to those who notice it).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
