On Sat, Nov 06, 2010 at 05:26:37PM -0700, Kees Cook wrote: > 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.
This is the root cause of the failure in this case. There isn't a package providing sysvinit on your system (if there is, then we aren't checking for it properly). You might want to check /usr/share/doc/build-essential/essential-packages-list (contains sysvinit) You might want to drop sysvinit from the list on ubuntu, since this is the definitive list we refer to when we set up the build environment. > 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. We previously installed build-essential when setting up a chroot, and reported missing bits in the logs. The latest release now actually reads the lists and adds them to the positive source dependencies to actually *ensure* they are installed. This is supported to be an additional sanity check to be sure the environment has the build essential packages installed, but in your case (assuming the list is outdated) contains an uninstallable package, and hence the error. If this is the case, could you let me know? 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