dependancy problem: cryptdisks_start should require watershed

[Pieter]

Binary package hint: cryptsetup

Using a encrypted file, i got the following error when opening/seting it ip.

:~$ sudo cryptdisks_start personal
[sudo] password for pieters:
 * Starting crypto disk... * personal (starting)..
/usr/sbin/cryptdisks_start: 1: /lib/udev/watershed: not found
/usr/sbin/cryptdisks_start: 1: /lib/udev/watershed: not found
/usr/sbin/cryptdisks_start: 1: /lib/udev/watershed: not found
 * personal (failed)... [fail]
:~$

After installing watershed, the errors were gone, and the mounting worked.

$ sudo cryptdisks_start personal
 * Starting crypto disk... * personal (starting)..
Unlocking the disk /dev/loop1 (personal)
Enter passphrase:
 * personal (started)... [ OK ]
$

$ lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10
Same problem on 10.04

[Steve Langasek (vorlon)]

Rather than depending on watershed, it would be better to detect when we're invoked by cryptdisks_start and not require watershed at all. Watershed is really only required when there's the possibility of two processes trying to decrypt the same disk at the same time; while this might happen with cryptdisks_start, that would be user error rather than an init system bug, and it's probably simpler to not guard against this case.

[Graeme Hewson (ghewson)]

Problem is still present in Oneiric.

[Jean-Louis Dupond (dupondje)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Precise Pangolin. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://help.ubuntu.com/community/UbuntuBackports for more information.