Package: cryptsetup Version: 2:1.0.4-8 Severity: grave Justification: renders package unusable
unfortunately we introduced a new RC bug in cryptsetup 1.0.4-7. The initscripts both should use 'set -e' and therefore fail for every single error that occurs. unfortunately the 'modprobe -q dm-crypt' at do_start() in cryptdisks.functions fails if the module isn't present: $ modprobe -q dm-crypt || echo "failed" failed $ one way would be to remove the 'set -e' from the initscripts, but in bug #390354 Goswin Brederlow asked for 'set -e' in the initscripts explicitely. what do you think about the bug? i would prefer a way where modprobe is only run when the module is available, but i don't know of any easy way to implement that. if you've no simple solution either, maybe we should remove the 'set -e' for now and search for better solutions post etch. ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
