Attila Kinali wrote: > On Sat, 24 May 2014 11:26:50 +0200 > Michael Biebl <[email protected]> wrote: > > > Am 24.05.2014 11:04, schrieb Attila Kinali: > > > > I want to add a little bit on this bug here. > > > IMHO the bug is valid in the sense that policykit unnecessarily > > > pulls in systemd. > > > > No, it's not unnecessary. policykit-1 requires systemd-logind. > > Without it, it's broken. > > Then the package dependencies are borken: > > attila@shuuji:~ # dpkg -s policykit-1|grep Status > Status: install ok installed > attila@shuuji:~ # dpkg -s systemd-logind|grep Status > dpkg-query: package 'systemd-logind' is not installed and no > information is available Use dpkg --info (= dpkg-deb --info) to > examine archive files, and dpkg --contents (= dpkg-deb --contents) to > list their contents. > > > And aparently, the whole system still works, as i can still print > documents using hplip (which depends on policykit) without having > systemd-logind installed.
The systemd-logind executable is in the systemd package. Installing this package is not automatically switching your system to systemd as PID1 (this is done by the systemd-sysv package). The only thing policykit requires is a registered logind session. Cheers, Laurent Bigonville -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
