Bug 120802 - sys-fs/cryptsetup-0.1-r2 fails with newer device-mapper
|
Bug#:
120802
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: strerror@gentoo.org
|
Reported By: ceed@xrc.de
|
|
Component: Applications
|
|
|
URL:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344313
|
|
Summary: sys-fs/cryptsetup-0.1-r2 fails with newer device-mapper
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2006-01-29 02:36 0000
|
Portage's cryptsetup needs libdevmapper.so.1.01 to be able to read the maps,
otherwise crypted images will not mount with the error:
"Command failed: Invalid argument"
There seems to be a cryptsetup snapshot which adresses this issue, please see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344313
As a temporary fix, masking '>=sys-fs/device-mapper-1.02.02' helps.
This might affekt cryptsetup-luks as well, I have not tested it.
in cvs, thanks for reporting
This problem still exists in the AMD64 stable branch. device-mapper-1.02.02 has
been marked stable on AMD64, however cryptsetup-0.1-r3 is still masked and
cryptsetup-0.1-r2 (the current stable lead) doesn't work with
device-mapper-1.02 versions as described.
The solution is quite easy: Mark cryptsetup-0.1-r3 stable or mask
device-mapper-1.02.02 again. Please reopen this bug (I don't have sufficient
permissions for this).
