Bug#814240: systemd triggers break upgrades within unstable

Zack Weinberg zackw at panix.com
Tue Feb 9 22:30:43 GMT 2016


On Tue, Feb 9, 2016 at 9:46 AM, Michael Biebl <biebl at debian.org> wrote:
>>
>> 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.

I do not have either the time or the skills to dig into this any
further, but I suggest you reassign the bug to dpkg and maybe they can
do something with it?

zw




More information about the Pkg-systemd-maintainers mailing list