120802 2006-01-29 02:36 0000 sys-fs/cryptsetup-0.1-r2 fails with newer device-mapper 2006-10-12 04:21:27 0000 1 1 1 Unclassified Gentoo Linux Applications unspecified All Linux RESOLVED FIXED http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344313 P2 normal --- 124928 1 ceed@xrc.de strerror@gentoo.org bugreports@tittel.net ceed@xrc.de 2006-01-29 02:36:23 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. vapier@gentoo.org 2006-01-29 03:21:57 0000 patch is here: http://bugs.debian.org/cgi-bin/bugreport.cgi/diff?bug=344313;msg=10;att=1 strerror@gentoo.org 2006-02-02 06:59:05 0000 in cvs, thanks for reporting bugreports@tittel.net 2006-03-15 15:33:14 0000 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). strerror@gentoo.org 2006-03-16 01:43:41 0000 reopenned. AMD plesae mark stable as per bug #124928 blubb@gentoo.org 2006-06-23 08:43:46 0000 only alpha is left on bug 124928, removing amd64 strerror@gentoo.org 2006-10-12 04:21:27 0000 fixed