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

[Johannes Schauer]

Hi,

Quoting Niko Tyni (2016-01-03 15:24:38)
> It looks like sbuild doesn't currently take build profiles into account when
> resolving cross build dependencies. This seems to me like a fundamental
> building block for at least the "cross" profile, so maybe I'm missing
> something?
> 
> In case I'm not, please consider the attached patch for the APT resolver.

can you show me an example where sbuild does not respect build profiles for
build dependency resolving?

Sbuild cannot use apt's new "apt-get build-dep foo.dsc" method until that apt
version is in old-old-stable because sbuild uses apt *inside* the chroot for
dependency resolving. Until support for "apt-get build-dep foo.dsc" is
supported by old-old-stable, sbuild will use an internal dummy repository. This
repository is populated with a dummy binary package which is created by sbuild
and contains the correct build dependencies for the package build. These build
dependencies are calculated by Dpkg::Deps::deps_parse which is told about build
profiles.

Also back when I implemented build profile support in sbuild it was working
just fine. Looking at the code now it still should.

Did you find a regression?

Also, because we must support apt in old-old-stable we cannot just push the -P
argument to the apt-get invocation since this will break apt pre-Jessie.

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20160103/02911bb7/attachment.sig>