On 10/05/16 at 12:31 +0200, Andreas Beckmann wrote: > Package: debian-policy > Severity: normal > > Hi, > > I just noticed that there are also Build-Depends-Arch/Build-Conflicts-Arch: > > from deb-src-control(5): > > Build-Depends-Arch: package-list > Same as Build-Depends, but they are only needed when build‐ > ing the architecture dependent packages. The Build-Depends > are also installed in this case. This field is supported > since dpkg 1.16.4; in order to build with older dpkg ver‐ > sions, Build-Depends should be used instead. > > Build-Conflicts-Arch: package-list > Same as Build-Conflicts, but only when building the archi‐ > tecture dependent packages. This field is supported since > dpkg 1.16.4; in order to build with older dpkg versions, > Build-Conflicts should be used instead. > > These are not mentioned at all in the policy, but given that the dpkg > version constraint is satisfied in oldstable, it should be safe to use > them now.
There are now packages in the archive relying on Build-Depends-Arch (the botch package, at least). This does not seem to raise issues. It's not supported in the version of sbuild in stable, but is supposed in the sbuild branch used on buildds. Lucas
