Am 17.03.2018 um 18:33 schrieb Benedikt Spranger: > On Sat, 17 Mar 2018 03:02:19 +0100 > Michael Biebl <bi...@debian.org> wrote: > >> On Mon, 12 Mar 2018 12:51:35 +0100 Benedikt Spranger >> <b.spran...@linutronix.de> wrote: >>> Package: consolekit >>> Version: 0.4.6-6 >>> Severity: serious >>> >>> Dear Maintainer, >>> >>> please readd consolekit to the archive. Without consolekit the >>> dependency to libpam-systemd as alternative to consolekit forces me >>> to install systemd without any further benefit. >>> >>> Since my systems works fine before (and till now, since consolekit >>> 0.4.6-6 is installed) the removal of consolekit from the archive >>> causes a regression. As my understanding of init system >>> dependencies this is a serious bug, since it forces a dependency to >>> a special system init system without any need. >> >> This is incorrect. The removal of consolekit does not enforce a switch >> to a different init system. You are probably mistaking systemd with >> systemd-sysv. Please read the package descriptions carefully. > > Please read the bug report carefully. I do not claim it forces me to > use, it forces me to *install* systemd due to libpam-systemd as > alternative to consolekit. So it forces me to *install* a different > init system:
You said, it "forces a dependency to a special init system". And this is simply wrong. You are mixing up systemd as init system with systemd-logind here. systemd-logind is a maintained alternative to consolekit. consolekit is dead upstream, unmaintained and has many design flaws. That it breaks certain setups like in #888892 was just the last straw that broke the camels back. Keep in mind, I'm the former maintainer of consolekit, so I very much know about its shortcomings. Hope that clarifies. Michael -- 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
