Michael Meskes <michael@fam-meskes.de> writes:
PackageKit uses the very same resolver as apt itself does... A log
file of what actually happened would be very helpful here, to determine
the problem causing the package removal.
Just try an update on a recently updated (Sunday) sid system and you'll
see see the conflicts.
I'm unclear as to what you have installed that triggers this, because I've
been using systemd and sid for eons and have never encountered this
behavior. (That also makes me pretty sure, pace Steve, that this is not
something *systemd* as systemd is actually doing, but some other
component.)