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

Craig Sanders cas at taz.net.au
Sun Jul 17 03:21:26 BST 2022

On Sun, Jul 17, 2022 at 04:01:38AM +0200, Thorsten Glaser wrote:
> On Sun, 17 Jul 2022, Craig Sanders wrote:
> > and, of course:
> >
> >     apt-mark hold sysvinit-core
> >
> > To prevent systemd from being auto-installed in some future upgrade.
> You most likely want some pinning.

I've never found pinning to be of much use. When I did have an actual use for
it (many years ago, during the gnome 2 -> gnome 3 transition), it required
constant work and tweaking of the pinning rules to get it to do what I
wanted. Far more work than it was worth - I ended up just purging gnome and
switching to xfce instead.

Having `APT::Default-Release "unstable";` is enough for my needs. That allows
me to run sid and cherry pick a few things (mostly nvidia-kernel-dkms and
friends) from experimental. With that default release, apt will only install
from unstable unless I explicitly force it to with `-t experimental`. Works
for me.

Or `APT::Default-Release "stable";` allows a system to run stable and
cherry-pick from testing/sid/experimental plus backports as needed.

> 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
a few days/weeks for updated packages.  I don't run a dist-upgrade every day
anyway, so waiting is no big deal.


craig sanders <cas at taz.net.au>

More information about the Debian-init-diversity mailing list