On Sun, 10 May 2015 at 10:10 Michael Biebl <[email protected]> wrote: > Can you confirm that adding that "|| true" to postinst manually fixes > your issue and allows you to uninstall systemd-sysv? >
Unfortunately, that won't work with my current test system, because colord crashes before it gets to the systemd trigger. Preconfiguring packages ... (Reading database ... 32367 files and directories currently installed.) Removing colord (1.2.1-1+b2) ... Failed to get D-Bus connection: No such file or directory dpkg: error processing package colord (--remove): subprocess installed pre-removal script returned error exit status 1 Failed to get D-Bus connection: No such file or directory Failed to get D-Bus connection: No such file or directory dpkg: policykit-1: dependency problems, but removing anyway as you requested: colord depends on policykit-1 (>= 0.103). Removing policykit-1 (0.105-8) ... Removing libpam-systemd:i386 (215-17) ... dpkg: systemd-sysv: dependency problems, but removing anyway as you requested: init depends on systemd-sysv | sysvinit-core | upstart; however: Package systemd-sysv is to be removed. Package sysvinit-core is not installed. Package upstart is not installed. Removing systemd-sysv (215-17) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for dbus (1.8.16-1) ... Errors were encountered while processing: colord E: Sub-process /usr/bin/dpkg returned an error code (1) Ideally, we wouldn't allow to install systemd-sysv in the first place in > such a case by adding preinst checks which test for necessary kernel > features and abort. > Yes, that is a thought. Might get complicated if a "apt-get dist-upgrade" from wheezy fails half way though. Still, this might be a better outcome, not sure. However, I think we are past that point now.
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
