Your message dated Mon, 30 Jul 2012 19:36:46 +0100
with message-id <[email protected]>
and subject line Re: [buildd-tools-devel] Bug#683287: sbuild: will not install
a missing build-dep in some cases
has caused the Debian Bug report #683287,
regarding sbuild: will not install a missing build-dep in some cases
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
683287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683287
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sbuild
Version: 0.63.1-1ubuntu1
Severity: normal
User: [email protected]
Usertags: origin-ubuntu quantal
Dear Maintainer,
Consider the case of libio-socket-ip-perl in quantal as of this writing. It has
a dependency like "libsocket-perl (>= 1.97) | perl (>= 5.15.6)".
libsocket-perl's current version is 2.002-1 (which is fine). Perl's current
version is 5.14.2-12 (which does not satisfy the check).
So sbuild correctly reports:
libsocket-perl: missing
perl: non-matching version installed (5.14.2-12 ! >= 5.15.6)
And then does not try to install libsocket-perl. Which I think is a clear bug?
The build fails because it is dep waiting on libsocket-perl, despite it
actually being available.
It seems that sbuild's dependency checker stops if part of an or-clause is
already installed, regardless of whether it actually satisfies the
requirements. I'd argue it should take that into account and attempt to install
another part of the or-clause.
-- System Information:
Debian Release: wheezy/sid
APT prefers quantal-updates
APT policy: (500, 'quantal-updates'), (500, 'quantal-security'), (500,
'quantal')
Architecture: i386 (i686)
Kernel: Linux 3.5.0-6-generic (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages sbuild depends on:
ii adduser 3.113+nmu1ubuntu1
ii apt-utils 0.9.7.1ubuntu1
ii libsbuild-perl 0.63.1-1ubuntu1
ii perl 5.14.2-12
ii perl-modules 5.14.2-12
Versions of packages sbuild recommends:
ii debootstrap 1.0.41ubuntu1
ii fakeroot 1.18.4-2
Versions of packages sbuild suggests:
pn deborphan <none>
ii wget 1.13.4-3ubuntu1
-- no debconf information
--- End Message ---
--- Begin Message ---
Closing, thanks. Please do reopen if it is something we should
look at more closely, but for now I think this is fine given that
this is all delegated to apt/aptitude.
On Mon, Jul 30, 2012 at 02:20:42PM -0400, Michael Terry wrote:
> Aha, after some digging, I realized that Launchpad uses a forked
> copy of sbuild
> (https://code.launchpad.net/~canonical-launchpad-branches/launchpad-buildd/trunk).
>
> So it's not clear if this affects Debian's sbuild. Feel free to close.
>
> -mt
>
> On Mon 30 Jul 2012 12:38:16 EDT, Roger Leigh wrote:
> >On Mon, Jul 30, 2012 at 10:50:35AM -0400, Michael Terry wrote:
> >>Consider the case of libio-socket-ip-perl in quantal as of this writing. It
> >>has a dependency like "libsocket-perl (>= 1.97) | perl (>= 5.15.6)".
> >>libsocket-perl's current version is 2.002-1 (which is fine). Perl's current
> >>version is 5.14.2-12 (which does not satisfy the check).
> >>
> >>So sbuild correctly reports:
> >>
> >>libsocket-perl: missing
> >>perl: non-matching version installed (5.14.2-12 ! >= 5.15.6)
> >>
> >>And then does not try to install libsocket-perl. Which I think is a clear
> >>bug? The build fails because it is dep waiting on libsocket-perl, despite it
> >>actually being available.
> >>
> >>It seems that sbuild's dependency checker stops if part of an or-clause is
> >>already installed, regardless of whether it actually satisfies the
> >>requirements. I'd argue it should take that into account and attempt to
> >>install another part of the or-clause.
> >
> >Which dependency solver were you using? I'm assuming it wasn't
> >internal, which should be removed in this version.
> >
> >I think you're probably running afoul of the RESOLVE_ALTERNATIVES
> >setting, which for the apt resolver default to 0. That is, all
> >alternative build dependencies will be stripped out. You should
> >be able to confirm this by looking at the dependencies in the
> >dependency package--they should be printed as part of the build
> >log. You should see the filtered dependencies as having all the
> >alternatives removed.
> >
> >On the Debian buildds, RESOLVE_ALTERNATIVES is always 0, except
> >for the experimental and backports buildds which use aptitude and
> >are out of necessity more flexible, but less reproducible. For
> >all stable/testing/unstable builds, alternative build dependencies
> >are not allowed. I'm not sure what Ubuntu buildds do.
> >
> >I hope that helps explain things. If my assuption is wrong, I'll
> >be happy to look at it further.
> >
> >
> >Regards,
> >Roger
> >
>
>
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
--- End Message ---
