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'.
** Changed in: lvm2 (Ubuntu)
Status: Confirmed = Won't Fix
--
preinst reports exit status 10
Is this bug still an issue for feisty/gutsy/hardy?
--
preinst reports exit status 10
https://bugs.launchpad.net/bugs/47972
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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?
--
preinst reports exit status 10
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
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
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
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
