[Buildd-tools-devel] Bug#456934: Bug#456934: sbuild: Wrong handling of or'ed build-dependencies
Jan-Marek Glogowski
glogow at fbihome.de
Wed Dec 19 07:10:37 UTC 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> On Tue, Dec 18, 2007 at 10:40:56PM +0000, Roger Leigh wrote:
> > Jan-Marek Glogowski <glogow at fbihome.de> writes:
> > > I'm trying to build bzr-svn for Debian Etch.
> > >
> > > The package has the following build dependencies:
> > >
> > > Build-Depends-Indep: python-subversion, bzr (>= 1.0~), python (>= 2.5) | python-pysqlite2
>
> > Thanks. I have altered the patch slightly to remove some of the
> > redundancy in the checks. Is this OK?
>
> Isn't it usual sbuild behaviour to only try the first package of a set
> of alternatives?
Currently yes, but I consider this a bug. The patched code already runs
in a loop to check for all alternatives, but it currently fails, if it
can't satisfy a versioned dependency.
sbuild[1301]: foreach $d ($dep, @{$dep->{'Alternatives'}}) {
Without the 'next', $installable is set, even if it's not installable.
sbuild[1325]: $installable = $name if !$installable;
Jan-Marek
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFHaMPwj6MK58wZA3cRArM1AJ94D8nv0eMhRY0Wbyu92aJF66Q+sgCbBFa6
UzluK40y/1HcXf/q0lZdbas=
=yzAJ
-----END PGP SIGNATURE-----
More information about the Buildd-tools-devel
mailing list