[buildd-tools-devel] Bug#695203: sbuild: cross-build-deps resolved from current apt sources rather than from package being built

[Colin Watson]

Package: sbuild
Version: 0.63.2-1
Severity: normal
Tags: patch
User: ubuntu-devel at lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch raring

A known problem (at least Wookey knew about it when implementing it)
with sbuild when cross-building is that it works out build-dependencies
based on the current apt sources rather than on the package you're
actually building.  This is problematic when you're using a bootstrap
repository with different build-dependencies, or when you're testing a
change that involves changing build-dependencies.

As it happens, this is not very difficult to fix.  We do still need to
use 'apt-get -aHOST build-dep', because that has special multiarch logic
we need to preserve.  But, when building its dummy package, sbuild
already constructs a .dsc as well as a .deb, and it adds a deb-src line
for the dummy archive.  This means that all we need to do when
cross-building is to split out the installation of essential and
gcc-snapshot (since they, and core, may not necessarily be resolvable
using 'apt-get -aHOST build-dep - I ran into such a problem in core
while testing this) and then use build-dep against the dummy archive.

This all seems to work nicely: I can add a build-dependency to an
existing package, build a new .dsc, feed it to sbuild, and it pulls in
the new build-dependency as instructed.

If you accept this change, it supersedes #693788.

Thanks,

-- 
Colin Watson                                       [cjwatson at ubuntu.com]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cross-build-deps.patch
Type: text/x-diff
Size: 5482 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20121205/7b6ccb67/attachment.patch>