Bug#1015015: unable to upgrade due to elogind vs systemd conflict

Thorsten Glaser t.glaser at tarent.de
Sun Jul 17 03:33:00 BST 2022

On Sun, 17 Jul 2022, Craig Sanders wrote:

> > You most likely want some pinning.
> I've never found pinning to be of much use. When I did have an actual use for

No, not that. You need it to get apt to not even consider systemd

> wanted. Far more work than it was worth - I ended up just purging gnome and
> switching to xfce instead.

That anyway.

> Having `APT::Default-Release "unstable";` is enough for my needs. That allows
> Or `APT::Default-Release "stable";` allows a system to run stable and
> cherry-pick from testing/sid/experimental plus backports as needed.

No, not that. See above and below.

> > Just held in dpkg or even marked as XB-Important: yes often brings apt to
> > tears in sid, i.e. refusing to dist-upgrade at all.
> Yeah, but I **want** apt to chuck a wobbly, it alerts me to the fact that
> there are problems that need manual intervention and/or that I need to wait

Nope. These are things apt could, in theory, solve by itself but cannot
because it can only consider one solution but that’s uninstallable. By
forcing it to not even consider systemd by pinning it down to -1 you get
apt to consider an alternative solution instead.

In pbuilder, I pin down dconf-gsettings-backend for example, so it gets
gconf-gsettings-backend instead, which works without systemd. (Not that
this is actually used during the building, but dependencies are gonna

<diogenese> Beware of ritual lest you forget the meaning behind it.
<igli> yeah but it means if you really care about something, don't
    ritualise it, or you will lose it. don't fetishise it, don't
    obsess. or you'll forget why you love it in the first place.

More information about the Debian-init-diversity mailing list