Bug#607225: breaks when using mdadm or cryptsetup
On Wed, Dec 15, 2010 at 10:08:01PM +0100, Daniel Baumann wrote:
> mdadm and cryptsetup, same as what we already fixed with lvm, doesn't
> get installed (apparently for different reason though), thus it breaks
> when using luks or raid for target.
I tried to reproduce this with a daily build using the "Guided - use
entire disk and set up encrypted LVM" option, but I couldn't - it
installs cryptsetup into /target successfully and the resulting system
boots fine. Can you point me at a way to reproduce this?
Alternatively, a syslog from an installation run with the
DEBCONF_DEBUG=developer boot parameter would be helpful.
Colin Watson [firstname.lastname@example.org]