Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable

[Jonas Meurer]

Hi Gordon,

thanks for the bugreport. I escalate this bugreport to the
debian-release team, asking for advice: would you accept another
cryptsetup upload targeted to jessie in order to add 'plymouth' to the
list of recommended packages?

Am 03.03.2015 um 03:43 schrieb Gordon Morehouse:
> Booting in jessie is currently nearly impossible with multiple cryptsetup
> volumes which are mounted at boot time.  systemd spews messages over the
> prompt and there's a 90-second timeout while typing blind.  Please see
> the bug report[1] and discussion on debian-qa[2].
> 
> The bug appears to be "fixed" by installing plymouth, so it's proposed that
> systemd-sysv and cryptsetup should at least recommend plymouth.

I agree that plymouth should be pulled in per default on jessie
installations with systemd and cryptsetup. While I don't know nothing
about systemd without plymouth, when cryptsetup comes into play,
plymouth is critical for the interactive password prompt at boot.

Therefore I agree with the bug submitter, that cryptsetup in jessie
should recommend plymouth.

I could upload cryptsetup packages with the added recommends immediately
after the pre-approval of the jessie release team.

Cheers,
 jonas

PS: This mail goes directly to Niels as he suggested the recommends[3].


> 
> This is a major usability problem for users with multiple required
> cryptsetup volumes, e.g. on /var and /usr.  I do not believe jessie should
> ship as "stable" with it unresolved.
> 
> 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768314 
> 2. https://lists.debian.org/debian-qa/2015/02/msg00051.html


[3] https://lists.debian.org/debian-qa/2015/02/msg00056.html