As much as anything it was misunderstanding that systemd-shim doesn't eliminate the installation of systemd on the system; it just allows you to not use systvinit as your init system.
Regards, Daniel On 06/01/15 04:26 AM, Michael Biebl wrote: > control: forcemerge 774664 -1 > > Am 06.01.2015 um 05:00 schrieb Daniel Dickinson: >> Package: policykit-1 >> Version: 0.105-8 >> Severity: normal >> >> policykit has a hard dependency on libpam-systemd which has a hard >> dependency on >> systemd AND the dependency is NOT eliminated through the use of systemd-shim. >> >> It is probably intended that systemd-shim OUGHT to eliminate the depency on >> systemd HOWEVER THIS IS NOT THE CASE. >> >> I believe there is a packaging error in which libpam-systemd has been >> incorrectly >> specified in such a way that the dependency is not resolved through the use >> of systemd-shim. >> > > policykit-1 requires the org.freedesktop.login1 interface and the proper > registration of a logind session upon login. This is provided by > libpam-systemd. > > Therefor this dependency is correct, You might not like that, but this > is not a bug. > > >
smime.p7s
Description: S/MIME Cryptographic Signature
