On Wed, Oct 15, 2014 at 09:44:03PM +0200, Guido Günther wrote: > On Wed, Oct 15, 2014 at 11:21:56AM +0300, Yauheni Kaliuta wrote: > > Package: libvirt-daemon-system > > Version: 1.2.8-3 > > Severity: normal > > > > Dear Maintainer, > > > > attempts to do "apt-get dist-upgrade" recently started to report: > > > > The following packages will be REMOVED: > > libvirt-bin libvirt-daemon-system virt-goodies > > > > $ apt-cache policy libvirt-daemon-system > > libvirt-daemon-system: > > Installed: 1.2.8-3 > > Candidate: 1.2.9-3 > > Version table: > > 1.2.9-3 0 > > 500 http://ftp.fi.debian.org/debian/ unstable/main amd64 Packages > > *** 1.2.8-3 0 > > 500 http://ftp.fi.debian.org/debian/ jessie/main amd64 Packages > > 100 /var/lib/dpkg/status > > > > The reason is that the new libvirt-daemon-system version Depends of > > policykit-1, > > which depends of libpam-systemd which Depends of systemd which is blocked > > on my > > system. > > > > Since it's declared, that systemd is not mandatory in Debian, the package > > must > > be installable (or what I did wrong?). > > It's "declared" that you don't need systemd as init system > (systemd-sysv), depending on systemd itself is fine - you should > adjust your blocks accordingly (it's like asking not to depend on > dnsmasq since you don't like it, it's perfectly valid as a wishlist > bug, but that's about it). > > I'm closing this since this since it's just another dependency, please > reopen if you think otherwise.
Another point here: polkit in wheezy doesn't depend on systemd but the jessie version does. So looking if we can make polkit's dependency on systemd optional - or offer a polkit compatible replacement in the long run would make the "hard" indirect dependency on systemd. I've also checked that (forcibly) removing polkit makes libvirt-daemon-system still work for uid 0. So we can run without polkit even with enabled polkit support. Cheers, -- Guido -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
