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

Craig Sanders cas at taz.net.au
Sun Jul 17 02:46:18 BST 2022

On Sat, Jul 16, 2022 at 02:35:33PM +0100, Mark Hindley wrote:
> On Sat, Jul 16, 2022 at 11:07:47PM +1000, Craig Sanders wrote:
> > 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'.
> Great. systemd-tmpfiles is a virtual package that is also provided by
> systemd-standalone-tmpfiles. If you manually install that, I suspect you
> will find everything is OK again.

Thanks, I have just tried that and it seems to work.

Perhaps elogind should Suggest or Recommend systemd-standalone-tmpfiles?

BTW, I had already installed systemd, but hadn't rebooted yet, before I
saw this, but (after examining /var/log/dpkg.log to find out exactly which
packages had been removed because of that), running the following reverted my
system back to the way it was before.

    apt-get install systemd-standalone-tmpfiles sysvinit-core elogind

and, of course:

    apt-mark hold sysvinit-core

To prevent systemd from being auto-installed in some future upgrade.

indra:/var/log# grep -E ' (remove|purge) ' dpkg.log
2022-07-16 17:05:39 startup packages remove
2022-07-16 17:05:39 remove libelogind0:amd64 246.9.1-1+debian1 <none>
2022-07-16 17:05:39 remove elogind:amd64 246.9.1-1+debian1 <none>
2022-07-16 17:05:41 startup packages remove
2022-07-16 17:05:41 remove sysvinit-core:amd64 3.03-1 <none>
2022-07-16 17:05:42 startup packages remove
2022-07-16 17:05:43 remove libpam-elogind:amd64 246.9.1-1+debian1 <none>
2022-07-16 17:05:44 startup packages remove
2022-07-16 17:05:44 remove libpam-elogind-compat:amd64 1.3 <none>


More information about the Debian-init-diversity mailing list