Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
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 Michael, 219-5 is MUCH MUCH better. If I type the wrong password it's a bit glitchy (prints multiple prompts and starts a service to dispatch password prompts but then holds after a spurious prompt or two). I didn't wait to see if there was a hidden timeout. I got the system booted in one try which is a first. If v219 works reasonably well (without plymouth), we might consider backporting those patches (depending on how invasive they are). So far so good here. Best, -Gordon M. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
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 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 Just A User(tm) but I really think this should be fixed in time for jessie, because it looks really, really terrible. Yes, there's a fix - if you can get your system booted, which takes me on average 3-5 tries with only two interactive password prompts. If I were a sysadmin and ran into this after installing jessie, I'd think strongly about uninstalling it and going with something else. It can't even boot right?! is the first question that came to mind after my first install of jessie - really unacceptable UX for a release soon to be marked stable and a distribution which people have relied upon for stability for well over a decade, including myself. I'll drop it after this, but I urge release maintainers to take the above into consideration and fix this in time for jessie. Thanks for all your hard work. Best, -Gordon M. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
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. Best, -Gordon M. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
On Sun, 08 Mar 2015 12:45:28 +0100, Jonas Meurer jo...@freesources.org 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 packages? Thank you! 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. There are some differing opinions starting at about [1] on Bug#768314. I will attempt to direct them here. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768314#160 Best, -Gordon M. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#779612: recommends, suggest, and which packages
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?bug=779612 Best, -Gordon M. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#768314: proposed 'recommend' as suggested on debian-qa
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 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#768314: proposed 'recommend' as suggested on debian-qa
On Wed, 04 Mar 2015 17:56:52 +0100, Michael Biebl bi...@debian.org 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 myself and got a suggestion to file a bug suggesting a recommendation. I don't like that for the exact reason you mentioned - they're still going to end up doing a web search and then finding something that they then have to fix. I am unsure of any problems that might be raised by adding a dependency on plymouth. Best, -Gordon M. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable
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 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. 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 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
