On Aug 30, 2011, at 08:57 PM, Stefano Rivera wrote:
>Hrm, I generally find sbuild's internal resolver to be the closest to
>Launchpad buildds. In this case, the internal resolver works fine
>(sbuild 0.62.5-1)
Here's what the sbuild(1) manpage says about the internal resolver:
--build-dep-resolver=resolver
...
mended for use by default. The internal resolver is much
older, contains several significant deficiencies such as not
being able to handle complex alternative and virtual dependen‐
cies, and is deprecated. Like apt, it only uses the first
alternative build dependency when multiple alternatives exist.
It is not recommended for future use, and will be removed in
the future.
I've generally had pretty good luck with the default apt resolver. I think
this is the first case where it's failed me.
Further information, if, after the initial failed attempt to install the build
dependencies, I enter the preserved chroot and do `apt-get build-dep pyside`
they all install just fine. This makes me wonder whether this is an sbuild
problem, an apt problem, or a problem with the dependencies.
My local pyside build is still ongoing (it takes a long time), but I'll give
the internal resolver a shot to see if I can confirm your observation. I
suppose I'll file a bug on sbuild after that, and it can always be
re-targeted to apt if that's the real problem.
Cheers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832864
Title:
pyside version 1.0.4-1 failed to build in oneiric
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pyside/+bug/832864/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
