Bug#753357: How to avoid stealth installation of systemd?
On Wed Jul 2 2014 07:26:52 PM HKT, Juliusz Chroboczek wrote: > > Please send it publicly in the Debian bug tracker. > > Sorry, Thomas, but I'm not quite sure what are the privacy implications > of making public the set of packages running on my system. (Probably > none, but I'd rather not find out I'm wrong.) just carefully cut the relevant parts... Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#753357: How to avoid stealth installation of systemd?
>>> Juliusz, can you please paste your apt logs >> Sent by private mail. > Please send it publicly in the Debian bug tracker. Sorry, Thomas, but I'm not quite sure what are the privacy implications of making public the set of packages running on my system. (Probably none, but I'd rather not find out I'm wrong.) -- Juliusz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#753357: How to avoid stealth installation of systemd?
On 07/02/2014 03:52 AM, Juliusz Chroboczek wrote: >> Juliusz, can you please paste your apt logs showing what pulled systemd >> in on the system? > > Sent by private mail. If anyone else wants a copy, please drop me a note. > > -- Juliusz Please send it publicly in the Debian bug tracker. Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#753357: How to avoid stealth installation of systemd?
> Juliusz, can you please paste your apt logs showing what pulled systemd > in on the system? Sent by private mail. If anyone else wants a copy, please drop me a note. -- Juliusz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#753357: How to avoid stealth installation of systemd?
Am 01.07.2014 21:20, schrieb Steve Langasek: > Hi Michael, > > On Tue, Jul 01, 2014 at 05:37:55PM +0200, Michael Biebl wrote: >> Am 01.07.2014 17:20, schrieb Thomas Weber: >>> Or, taking a different perspective: now that the issue is known, what is >>> done to prevent another user from hitting the very same issue in the >>> future? > >> Install systemd-sysv for systemd-shim. >> The libpam-systemd package in 204-9 ensures that either of the two is >> installed. > > Ok, but assuming that is the fix (install systemd-sysv or systemd-shim), how > did bug #7533357 happen? I assume it did happen because Juliusz' did have 204-8 installed which did not yet have this dependency. libpam-systemd up until 204-8 did only depend on systemd. Which is sufficient for the session tracking part but requires either systemd-shim or systemd as PID 1 for the suspend/poweroff support. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#753357: How to avoid stealth installation of systemd?
Hi Michael, On Tue, Jul 01, 2014 at 05:37:55PM +0200, Michael Biebl wrote: > Am 01.07.2014 17:20, schrieb Thomas Weber: > > Or, taking a different perspective: now that the issue is known, what is > > done to prevent another user from hitting the very same issue in the > > future? > Install systemd-sysv for systemd-shim. > The libpam-systemd package in 204-9 ensures that either of the two is > installed. Ok, but assuming that is the fix (install systemd-sysv or systemd-shim), how did bug #7533357 happen? Notwithstanding Juliusz's desire to not have systemd installed (which I don't expect us to address), if both of those packages were missing from the system, then something is buggy. Juliusz, can you please paste your apt logs showing what pulled systemd in on the system? If something is depending on systemd directly without either systemd-sysv or systemd-shim, that something is buggy. If systemd-sysv *was* installed and logind wasn't working, this probably points to the bug with logind being broken before reboot to systemd. However, acpi-support-base also needs to make sure that logind is functional before delegating control of the power button to it. And for that, I see that acpi-support 0.141-4 introduced a change in unstable *yesterday* to deal with exactly this problem: instead of only checking for a running logind, acpi-support-base now checks the systemd dbus interface to verify that logind is running and usable. So it's possible that Juliusz's issue is a duplicate of bug #752781. On Tue, Jul 01, 2014 at 07:19:26PM +0200, Michael Biebl wrote: > Am 01.07.2014 18:53, schrieb Juliusz Chroboczek: > > Michael closed it straight away, > > without investigating the issue. > Oh, I did. That's why I told you to install systemd-shim. It should not be the user's responsibility to install this package manually to get back to a working system. On Tue, Jul 01, 2014 at 06:51:22PM +0200, Michael Biebl wrote: > > Install systemd-sysv for systemd-shim. > > The libpam-systemd package in 204-9 ensures that either of the two is > > installed. > The behaviour of acpi-support-base is correct, there shouldn't be any > bug filed against it. Well, I think the behavior of acpi-support-base is *now* correct in unstable, in response to bug #752781. I don't think it's correct in testing. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
