[buildd-tools-devel] Bug#809730: Bug#809730: sbuild: use build profiles when resolving cross build dependencies

[Niko Tyni]

On Sun, Jan 03, 2016 at 04:54:20PM +0200, Niko Tyni wrote:

> Anyway, I'll try to construct a simple test case and get back to you.

OK, just cross build libpipeline_1.4.1-1 from sid with the nocheck
profile and watch the 'check' package get installed when it doesn't in
a native build.

 Build-Depends: dpkg-dev (>= 1.17.14), debhelper (>= 9.20141010), pkg-config, check <!nocheck>, dh-autoreconf, automake (>= 1:1.10)

DEB_BUILD_OPTIONS=nocheck sbuild --host armel -c sid -d unstable --profiles=nocheck libpipeline_1.4.1-1

(I had to use
 deb http://snapshot.debian.org/archive/debian/20160103 unstable main
as there seems to be some flux in sid that makes crossbuild-essential-armel
uninstallable, but I'm sure you're used to things like that.)

I can provide build logs if you like, just let me know.

In the case where I originally noticed this glitch, I think I was
trying to use an extra build dependency for cross builds with a <cross>
annotation, so not getting that installed was quite a bit more visible.

This is in a code path by Colin that actually uses 'apt-get build-dep',
and I would expect that passing build profile information to it is
necessary.

 https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/?id=9aaa06de161ecb0a5422dc48805215211590c2f9

-- 
Niko