PPA cannot build package that requires lilo on i386

Asked by Timothy Pearson

When I try to build a package that relies on lilo, the build succeeds for amd64 and lpia, but fails for i386. It fails when it attempts to install the lilo build-dep:
-------------------------------------------------------------------------------------
Setting up lilo (1:22.8-8ubuntu1) ...
mount: unknown filesystem type 'ext2'
dpkg: error processing lilo (--configure):
 subprocess post-installation script returned error exit status 32
-------------------------------------------------------------------------------------
Errors were encountered while processing:
 lilo
E: Sub-process /usr/bin/dpkg returned an error code (1)
apt-get failed.
Package installation failed
-------------------------------------------------------------------------------------

The full build log is here: http://launchpadlibrarian.net/33335622/buildlog_ubuntu-karmic-i386.kdeadmin-kde3_4%3A3.5.10-0ubuntu3_FAILEDTOBUILD.txt.gz

Any ideas? ;-)

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
LaMont Jones Edit question
Last query:
Last reply:
Revision history for this message
Barry Warsaw (barry) said :
#1

I've assigned this issue to our Soyuz team lead.

Revision history for this message
Julian Edwards (julian-edwards) said :
#2

Hi - thanks for raising this. We've identified a problem in the builder chroot, it should be fixed later today, I will reply back here.

Revision history for this message
LaMont Jones (lamont) said :
#3

Fixed.

Revision history for this message
Timothy Pearson (kb9vqf) said :
#4

You're welcome. Glad to see it's fixed.

Can someone rescore the rebuild attempt so that it actually gets built?
https://launchpad.net/~kb9vqf/+archive/ppa/+build/1283136

Thanks!

Revision history for this message
Timothy Pearson (kb9vqf) said :
#5
Revision history for this message
LaMont Jones (lamont) said :
#6

See https://bugs.launchpad.net/ubuntu/+source/lilo/+bug/505485 - the chroots haven't changed, lilo has.

lamont

Revision history for this message
LaMont Jones (lamont) said :
#7

In more detail: the fstab in the chroot has entries for / and /boot, "because the kernel build needed this at one time" - I'll dig into this more on monday.

Can you help with this problem?

Provide an answer of your own, or ask Timothy Pearson for more information if necessary.

To post a message you must log in.