On Fri, Nov 05, 2010 at 05:55:34PM -0700, Kees Cook wrote: > Package: sbuild > Version: 0.60.2-1 > Severity: normal > User: ubuntu-de...@lists.ubuntu.com > Usertags: origin-ubuntu natty > > It seems that the ESSENTIAL dep resolution breaks me (at least on Ubuntu). > I had to "exit 1" from install_essential() to restore my ability to build > (0.60.0 was working fine). > sysvinit: missing > I assume "sysvinit: missing" is the problem, but that should be satisfied > by "sysvinit-utils":
Grr, that's annoying. I've not seen this on Debian, but I do have the actual sysvinit package installed. So it's likely an issue with checking if virtual packages are installed. Note that the "aptitude" resolver should cope just fine with this; if you set $build_dep_resolver='aptitude' in your .sbuildrc, do you still have any problems? I'm planning on making the aptitude resolver the default with the next release since situations like this are handled much better. The "internal" resolver has only rudimentary support for virtual package installation (added with this release). This is however only currently used for installation of build-deps, not checking if a dependency is actually installed, so doesn't do a good job of checking in this situation. I've taken a look at the code (lib/Sbuild/InternalResolver.pm in git), but I'm not currently sure what the best strategy is to handle this. Note: the current git master may be worth trying here, since I've made some changes to both the aptitude and internal resolvers since 0.60.2 was released. Could you possibly try current git master and run with script to capture all stderr and with --debug to turn on debugging messages? This should let us know exactly where it's getting stuck. I'm not sure the "missing" error above is where it's getting stuck. That's in filter_dependencies and it /should/ rewrite in virtual_dependencies() to handle installation of a real package, but this doesn't take into account if it's installed under another name (which it is). We might need to be more intelligent about this and do the rewriting while checking if the package is already installed. Any thoughts? Hopefully the "internal" resolver will be removed in time, since it's rather limited, but the Debian buildds will use it until at least squeeze release. So getting this fixed would be ideal. Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
signature.asc
Description: Digital signature
