Processing commands for cont...@bugs.debian.org:
> retitle 659688 LVM on LUKS won't boot if not all LVs are available initially
Bug #659688 [cryptsetup] cryptsetup: LVM on cryptsetup won't boot
Changed Bug title to 'LVM on LUKS won't boot if not all LVs are available
initially' from 'cryptsetup:
retitle 659688 LVM on LUKS won't boot if not all LVs are available initially
severity 659688 normal
thanks
Roland Mas, 2012-02-14 20:18:25 +0100 :
> Feel free to downgrade it; I only picked "critical" because the effects
> were the same as for #659235, but I agree my setup may be a bit more
> inv
Jonas Meurer, 2012-02-14 00:03:37 +0100 :
> Hey Roland,
Hi,
> Am 13.02.2012 09:35, schrieb Roland Mas:
>> Package: cryptsetup Version: 2:1.4.1-2 Severity: critical
>
> To be honest I don't agree with you on the severity of this bug.
Feel free to downgrade it; I only picked "critical" because t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Roland,
Am 13.02.2012 09:35, schrieb Roland Mas:
> Package: cryptsetup Version: 2:1.4.1-2 Severity: critical
To be honest I don't agree with you on the severity of this bug. I
understand that the changes in LVM handling of cryptroot initramfs
scr
Package: cryptsetup
Version: 2:1.4.1-2
Severity: critical
Note that although this bug was introduced at version 2:1.4.1-1, it is
different from #659235: my PVs and LVs and VGs don't have dashes in
their name.
The current sequence: grub loads the kernel and the initramfs; the
kernel boots; the ini
5 matches
Mail list logo
