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

[Mark Hindley]

Craig,

Thanks for this.

What release are you upgrading from an to?

On Sat, Jul 16, 2022 at 06:34:35PM +1000, Craig Sanders wrote:
> Package: elogind
> Version: 246.9.1-1+debian1
> 
> I don't know if a newer version of elogind would help here, but it
> probably wouldn't hurt. elogind in debian hasn't been updated since
> Dec 23.
> 
> # apt -u dist-upgade
> [...]
> The following packages will be REMOVED:
>   alsa-firmware-loaders bluez brasero fwupd gnome-disk-utility
>   gnome-session-bin gvfs gvfs-backends gvfs-daemons i2c-tools kpartx
>   lcdproc libblockdev-mdraid2 libtss2-esys-3.0.2-0 libtss2-mu0
>   libtss2-sys1 libtss2-tcti-cmd0 libtss2-tcti-device0 libtss2-tcti-mssim0
>   libtss2-tcti-swtpm0 linux-image-5.16.0-6-amd64 linux-image-5.17.0-3-amd64
>   linux-image-5.18.0-2-amd64 linux-image-amd64 mdadm tpm-udev udisks2
>   upower xfce4-power-manager xfce4-power-manager-plugins xserver-xorg
>   xserver-xorg-input-evdev xserver-xorg-input-kbd xserver-xorg-input-mouse
> 
> Most of those I don't care about, but I really don't want linux-* packages or
> mdadm or xserver-* packages to be force-removed.

I can't immediately see the package that might be causing the conflict here.

> Aborting that and running 'apt upgrade' just highlights the cause:
> 
> # apt -u upgrade
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Calculating upgrade... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  elogind : Conflicts: systemd
>            Conflicts: systemd:i386
>  libelogind0 : Conflicts: libsystemd0
>                Conflicts: systemd
>                Conflicts: systemd:i386
> E: Broken packages

AFAIK this should still work, but apt might need a bit of help to find the
solution you want: it uses the first/default option which can lead it down the
systemd route.

My suggestions:

 - Ensure you have the correct apt sources and remove any pinning or held
   packages.

 - apt update

 - Manually install the new elogind, libelogind and libpam-elogind.

 - apt upgrade

 - apt dist-upgrade

If you find apt is trying to install systemd at any of these steps, we need to
identify the package that has a hard systemd dependency and deal with it.

HTH. Let me know how you get on.

Mark