The vol_id call was introduced to parse LUKS data? I see that removing
it unbreaks raw devices, but doesn't vol_id also make sure that the
device is fully settled, as opposed to a RAID just being halfway up or
so? Or is that handled later?

You don't need to wait until Jaunty opens. We can upload to intrepid-
proposed, let it build, and copy the source+binary to jaunty (I'll do
that, it's quite common right after releases, where the new one isn't
open yet and we have plenty of SRUs).

** Changed in: cryptsetup (Ubuntu Intrepid)
       Status: New => Incomplete

-- 
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to