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

Adam Borowski kilobyte at angband.pl
Sat Jul 16 14:32:55 BST 2022

On Sat, Jul 16, 2022 at 11:07:47PM +1000, Craig Sanders wrote:
> The machine is running sid, so this was just a routine dist-upgrade.
> > I can't immediately see the package that might be causing the conflict here.
> A little more investigation reveals that it's udev.
> udev 2.51.3-1 (Wed, 13 Jul 2022 23:05:40 +0200) now depends on 'systemd | systemd-tmpfiles'.

Just do:
apt dist-upgrade systemd-

That will let apt find the solution where it install systemd-tmpfiles but no
systemd itself.

The _correct_ way would be to write that dependency as
'systemd-tmpfiles | systemd' which is no-op on systemd installs but
avoids init switch elsewhere.

> I'm going to make another attempt to switch this machine to systemd.  It's
> been at least two years since I last tried.

Don't.  My primary desktop is in the same situation, and it appears I risk
physical damage(!) whenever I attempt to boot systemd.

> And, no, there's nothing unusual about this machine. It's an AMD FX 8150 on an
> Asus Sabertooth 990FX motherboard.  I have another identical motherboard with
> an AMD Phenom II 1090T which runs systemd without a problem.  And it's not the
> FX 8150 CPU - this machine used to have an identical 1090T CPU, and systemd
> wouldn't boot on it back then either.

AMD Threadripper+ 2990WX here.

⣾⠁⢠⠒⠀⣿⡁ How to squander your resources: those silly Swedes have a sauce
⢿⡄⠘⠷⠚⠋⠀ named "hovmästarsås", the best thing ever to put on cheese, yet
⠈⠳⣄⠀⠀⠀⠀ they waste it solely on mere salmon.

More information about the Debian-init-diversity mailing list