On Sat, Nov 12, 2016 at 05:57:33AM +0100, Johannes Schauer wrote: > Hi, > > Quoting Colin Watson (2016-11-12 03:58:04) > > On Sat, Nov 12, 2016 at 12:58:13AM +0100, Adam Borowski wrote: > > > * wanna-build(?)'s resolution of arch-specific build-depends is buggy. > > > For > > > example, my package arch-test wants, among others: > > > binutils-x86-64-linux-gnu [!amd64 !i386 !x32] which is a no-op on amd64, > > > properly recognized as such by dpkg-dev, debuild, sbuild, pbuilder, etc, > > > yet the package never gets picked for autobuilding. > > > > Possibly a dose-builddebcheck bug, though it could certainly be in the > > fairly complex wanna-build integration with dose-builddebcheck > > (https://anonscm.debian.org/cgit/mirror/wanna-build.git/tree/bin/wanna-build#n1846 > > and the various functions it calls). > > it doesn't seem to be a dose-builddebcheck bug. Consider the following > Packages > file: > > --%<---------------------- > Package: build-essential > Architecture: amd64 > Version: 1 > -->%---------------------- > > And the following Sources file: > > --%<---------------------- > Package: foo > Architecture: any > Version: 1 > Build-Depends: binutils-x86-64-linux-gnu [!amd64 !i386 !x32] > -->%----------------------
Actually, as suggested in a thread at https://lists.debian.org/debian-wb-team/2016/04/msg00008.html it's probably caused by looking for literally "all" in the list instead of real architectures of potential buildds. Thus, while the arch:all buildd has real arch=amd64, the dependency fails to be excluded by [!amd64 !i386 !x32]. -- A true bird-watcher waves his tail while doing so.
