Dne 14.6.2010 00:44, Bastian Blank napsal(a):
On Sun, Jun 13, 2010 at 11:29:06PM +0100, Alasdair G Kergon wrote:
On Sun, Jun 13, 2010 at 10:42:14PM +0200, Thomas Koch wrote:
I've updated by accident (lack of better knowledge...) only
libdevmapper, but not dmsetup. Afterwards my system didn't boot anymore:
The package manager should enforce updating the packages together.
It makes no sense to have a system with dmsetup older that libdevmapper.
No, this is not how an ABI works. This means that libdevmapper have a
broken interface with its users.
There are few problems - however in this case the only possible fix at this
moment is to setup stronger Dependency from dmsetup to the same
'libdevmapper' version.
libdevmapper library is now working with udev- however Debian provides udev
rules inside dmsetup package.
Best solution for now is to add 'libdevmapper1.02.1 (= ${binary:Version})'
to dmsetup package.
Also questionable is the existence of libdevmapper library without udev rules
from same package version. In the current situation there are on going udev
changes and it may cause troubles to have multiple different libdevmapper libs
and same udev rules.
This may result into the situation that all application which are using
libdevmapper in effect need dmsetup - simply because dmsetup usage is required
through udev rules - so unless user explicitly requests to not use udev in
lvm.conf - any lvm need libdevmapper and dmsetup from the same release.
k...@debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
