On 03/25/2015 10:24 AM, Michael Biebl wrote:
Gordon, can you try systemd v219 from experimental?
It has some tricks to suppress output from other jobs while a password
prompt is running. I dunno how well that works, though so having someone
with such a setup test this would be appreciated.
Hi
On 03/25/2015 09:29 AM, Jonas Meurer wrote:
[snip]
>
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 nas
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, bu
On Sun, 08 Mar 2015 12:45:28 +0100, Jonas Meurer wrote:
> 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 pac
Hi folks,
My mention of creating Bug#779612 was intended to steer discussion of a
packaging-related "fix" for jessie into that bug and out of this bug. ;)
It's currently being discussed there[1] and has been escalated to the Debian
release list.
1. https://bugs.debian.org/cgi-bin/bugreport.cgi
On Wed, 04 Mar 2015 17:56:52 +0100, Michael Biebl wrote:
> A recommends in systemd-sysv doesn't help on new installations, since
> during debootstrap, recommends are not considered.
I personally believe it should be a dependency, but I spoke with some people
who are more involved in Debian than
I've created Bug#779612 [1] to propose that 'systemd-sysv' and 'cryptsetup'
recommend 'plymouth' in Jessie. There is related discussion in debian-qa[2].
1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779612
2. https://lists.debian.org/debian-qa/2015/02/msg00051.html
___
Package: systemd-sysv,cryptsetup
Severity: important
Dear Maintainer,
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 r
Package: systemd
Version: 215-11
Followup-For: Bug #768314
Dear Maintainer,
This renders systems with needed partitions (e.g. /var, /usr) on encrypted
volumes near-totally unusable, especially if there are multiple partitions.
I updated recently and the UI changed again. If anything, it's WORSE
Corrections on my above update, apologies:
On Fri, 23 Jan 2015 16:35:09 -0800, Gordon Morehouse
wrote:
> What I expect to happen:
>
> 1. The system should STOP and WAIT for a password for any encrypted volume
> which is marked as critical to boot (I had debconf ask me which of my
10 matches
Mail list logo
