Bug#814240: systemd triggers break upgrades within unstable

[Michael Biebl]

Am 09.02.2016 um 14:12 schrieb Zack Weinberg:
> Package: systemd
> Version: 228-6
> Severity: normal
> 
> libpam-systemd, systemd, and libsystemd0 have = dependencies on each
> other.  This invariant can be temporarily violated in the middle of a
> large upgrade, and AIUI that is normal and to be expected.  However,
> systemd has several dpkg triggers that can fire while the = dependencies
> are violated, and when this happens, the entire upgrade bombs out.
> Worse, one of those triggers seems to be armed and immediately fired *by
> upgrading libsystemd0*, before dpkg has had a chance to upgrade systemd
> proper, so this is guaranteed to happen any time the systemd packages
> are upgraded.
> 
> It's possible to recover by manually installing the new versions of
> libpam-systemd, systemd, and libsystemd0, but there's got to be some
> way to make apt do the Right Thing, right?  (I don't really understand
> triggers.  I thought they were supposed to postpone work until the *end*
> of a large upgrade, but they seem to go off all the time in the middle.)
> 

This looks like something which needs to be fixed in either dpkg or
aptitude.

Fwiw, I've never seen such a problem using apt.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160209/b5999d3a/attachment-0002.sig>