[buildd-tools-devel] Bug#602571: Bug#602571: cannot build due to ESSENTIAL dep phase

[Kees Cook]

Hi Roger,

On Sat, Nov 06, 2010 at 11:08:29PM +0000, Roger Leigh wrote:
> apt-cache --names-only search '^sysvinit$' | sed -e 's/\([^[:space:]][[:space:]]*\)[[:space:]].*/\1/'
> 
> What do you get in your chroot for the above?

This returns nothing.

17:20 root@(natty-amd64)gorgon# apt-cache --names-only search '^sysvinit$' | sed -e 's/\([^[:space:]][[:space:]]*\)[[:space:]].*/\1/' 
17:21 root@(natty-amd64)gorgon# apt-cache --names-only search '^sysvinit$'
17:21 root@(natty-amd64)gorgon# exit

I suspect this is related to how Ubuntu has replaced sysvinit with upstart?
I haven't looked too closely, but this is the first time I've run into it
causing a problem.

> If you set $resolve_virtual=0 in your config, does this then work OK?

It changes slightly but still fails:

Checking for dependency conflicts...
E: Package 'sysvinit' has no installation candidate
Installing positive dependencies: sysvinit
Reading package lists...
Building dependency tree...
Reading state information...
E: Package 'sysvinit' has no installation candidate
apt-get failed.
Package installation failed
Not removing build depends: cloned chroot in use
Essential dependencies not satisfied; skipping rng-tools

> TBH, fixing this might be really tricky, so it might be best to
> disable installing the essential package set by default when using
> the internal resolver.  Even the virtual dependency rewriting in
> virtual_dependencies could do the wrong thing if a package providing
> it vdep other than the one we pick is already installed; the
> aptitude resolver is really the way to go since the internal
> resolver is such a hairy mess it's really difficult to change without
> breaking stuff.  I'm tempted to back out even the virtual_dependencies
> change.

Thanks for looking into this! For now, I'll continue to just have
Sbuild/Build.pm install_essential() return 1. :)

-Kees

-- 
Kees Cook                                            @debian.org