Re: Policy 3.9.0.0 released
Emil Langrock <emil.langrock@gmx.de> writes:
> Russ Allbery wrote:
>> Debian Policy 3.9.0.0 has been released. The next time you upload your
>> packages, please review them against the upgrading checklist in the
>> debian-policy package and see if they require changes for the new
>> version of Policy.
>>
> [...]
>> 5.6.8, 7.1, 11.1.1
>> Architecture wildcards may be used in addition to specific
>> architectures in `debian/control' and `*.dsc' Architecture
>> fields, and in architecture restrictions in build relationships.
> Why is this allowed and still all packages are send to all
> architectures? This creates a lot of false "failed ... build of ..."
> mails. In the log of these builds on those architectures only appears
> something like:
> .... not in arch list or does not match any arch wildcards: linux-any all
It's a long-standing limitation of the way that the buildds work that if a
package builds any arch-independent package, that package is attempted on
all the buildds even if none of the arch-dependent packages will build
there. It would be lovely to have that bug fixed, but it's not new nor is
it directly related to arch wildcards. It's affected the openafs package
for years, which explicitly lists out the architectures it supports.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: