preinst reports exit status 10

I have also encountered this bug during the upgrade from breezy to dapper. The error message is identical. Synaptic mentions a broken package - ubuntu-standard - which depends on lvm2. I've been unable to complete the dist-upgrade.

Bob

Same bug with my upgrade. (Identical error message) Though I was able to install/upgrade all the other packages, which dist-upgrade would have installed/upgraded, with apt-get install.

Got exactly the same bug on two different machines I upgraded from Ubuntu breezy to dapper (ppc and i386).

I apt-get remove'd lvm2 and kept going on fine with the dist-upgrade afterwards.

HTH

Just noticed I didn't make myself quite clear: purging lvm2 and installing it again afterwards fixed the issue.

> Just noticed I didn't make myself quite clear: purging lvm2 and
> installing it again afterwards fixed the issue.

I've tried this, using apt-get, dpkg, and synaptic. It still won't install.

Thanks!

Bob

>
> --
> lvm2 does not install after breezy -> dapper (kubuntu)
> https://launchpad.net/bugs/47972
>
>

--
A millihelen is the amount of beauty required to launch one ship.

On 6/5/06, Bob_White <email address hidden> wrote:
>
> > Just noticed I didn't make myself quite clear: purging lvm2 and
> > installing it again afterwards fixed the issue.
>
> I've tried this, using apt-get, dpkg, and synaptic. It still won't
> install.

Specifically I did:
apt-get remove lvm2
dpkg --purge lvm2
apt-get install lvm2

which worked fine, I could install ubuntu-standard without trouble afterwards.

Given Dapper installs fine with fresh install, I believe this is a
packaging issue related to upgrading the package, hence the above
*should* fix the issue (purging and installing again equals to doing a
fresh install).

HTH

--
Thibaut VARENE
http://www.parisc-linux.org/~varenet/

T-Bone,

> Specifically I did:
> apt-get remove lvm2
> dpkg --purge lvm2
> apt-get install lvm2
>
> which worked fine, I could install ubuntu-standard without trouble
> afterwards.

1) apt-get said it was ignoring the remove request because lvm2 wasn't
installed.

2) dpkg said purge request was ignored because lvm2 wasn't installed

3) apt-get install generated the same error message as reported earlier.

I may try pointing the repositories back to breezy and try to reinstall
lvm2, then go back to dapper and try the upgrade again. It'll probably
have fits, but we'll see!

Thanks!

Bob
--
A millihelen is the amount of beauty required to launch one ship.

I am experiencing the same issue. I have purged the package but am still unable to reinstall it.

When I first ran into the problem, I completed my dist-upgrade with a "echo lvm2 hold | dpkg --set-selections"

My workaround for now was to unpack the files, modify the preinst file to exit 0 immediately, and then rebuild the .deb ...

The problem happens because of the kernel running. I strace'd the install and got the error "FSET lvm2/kernel seen false
10 lvm2/kernel doesn\'t exist"

I've not tried it yet, but I suspect putting lvm2 on hold as the others suggest, finishing the install, then rebooting into the 2.6.15 kernel, is the way to go.

The problem happens because of this code in the preinst:

if ! dpkg --compare-versions $(uname -r) ge '2.6.12'; then
 db_fset lvm2/kernel seen false
 db_input critical lvm2/kernel || true
 db_go
 exit 1
fi

I'm upgrading from Hoary, so my kernel is < 2.6.12, the code runs, and the question doesn't exist, so it fails as Edd reports.

This problem is reported at Debian's BTS: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358373

Their fix is version 2.02.05, which supports older kernels. Being that the upgrade will result in a kernel > 2.6.12 pretty soon afterwards, it really doesn't matter.

I had a go at backporting it, but it seems to need a newer version of libdevmapper now, so I've just resigned myself to building a package without the version check. :)

I'm upgrading from breezy and not even using lvm AFAIK. The

dpkg --purge
[...]
workaround failed for me, though the purge succeeded. Am running a custom 2.6.10 kernel.

This workaround allowed installation to proceed:

/bin/sh

cd /var/cache/apt/archives

cat >uname <<EOF
#!/bin/sh
echo 2.6.12
EOF

chmod +x uname

PATH=.:$PATH

dpkg -i lvm2_2.02.02-1ubuntu1_i386.deb

rm uname

CTL+D

Will upgrade kernel soon.

Is this bug still an issue for feisty/gutsy/hardy?

Even if it hasn't been fixed, if the lowest supported version of Ubuntu has a kernel newer than 2.6.12 (i.e. is newer than Dapper) it should be OK.

As Dapper is still in LTS, should bugs that affect an upgrade from a now non-supported version be ignorable?

Now that Dapper is, in fact, the lowest supported version of Ubuntu (Dapper Server only even), this bug, while real, has no effect on supported users.

Changing status to 'Won't Fix'.