Hello, Am 2015-03-20 16:49, schrieb Gordon Morehouse:
On 03/19/2015 06:58 PM, Michael Biebl wrote:As pointed out, a recommends does not really help for new installs, since they have no effect when installing the base system.A recommends at least provides users a pointer towards fixing a really nasty problem (which they shouldn't even have, but, they currently will).Also, what Julien said. Therefor, I wonder if this bug report is useful in this form and if there's a point, keeping it open.Perhaps you could open a more appropriate bug to fix the problem for new installs? I'm not familiar enough with Debian to do so. Leaving this bug completely untouched is not a good idea. It makes Debian look cartoonishly bad when it bites.
Seems like there's some more discussion needed in order to fix the reported bug: a) do we want cryptsetup to recommend plymouth? this way at least for manual installation of cryptsetup, plymouth would be pulled in, fixing destroyed nasty boot-password-prompts introduced that were introduced by the switch to systemd. b) do we want plymouth to be installed per default on new installs? to my knowledge it's not _required_ for systemd to work, but as soon as an initscript with user interaction is invoked, apparently plymouth is required. This *is* an argument for installing plymouth by default. c) do we want any of the above to be fixed/changed in time for jessie? I'm happy to implement the outcome of this discussion into the cryptsetup package, and I'm happy to prepare a quick upload with an added recommends on plymouth targeted at jessie. But at the moment I'm unsure which is the best solution, waiting for more opinions and especially for comments by the RMs ;) Cheers, jonas