Bug#1075757: elogind’s conflict with libelogind0 precludes upgrade
Benjamin Cama
benoar at dolka.fr
Thu Jul 4 12:57:00 BST 2024
Package: elogind
Version: 246.10-1debian1
Severity: important
Dear Maintainer,
I tried to upgrade to the latest 255 version of elogind, but I do not
understand the recent "Conflicts" addition with libelogind0: it renders
it uninstallable together with latest libelogind0, and thus ask me to
install libsystemd instead, which I do not want.
>From what I understand, dependency to libelogind0 has been dropped
because it actually provides exactly the libsystemd ABI now, so elogind
now depends on just libsystemd. But the addition of the "Conflicts" with
libelogind0 makes its use as a libsystemd substitute impossible. What
gives?
Maybe I have gotten something wrong, please tell me if so. Attached is
my upgrade attempt (not a full/dist-upgrade) for just elogind *with*
libelogind0 to nail the problem down; this is the output of:
apt-get install elogind libsystemd0+
This issue first appeared when installing/upgrading *any* package, where
apt wanted to install systemd on my system, because of some reverse
dependency I suppose.
Thanks for your support of this nice alternative software BTW.
Regards.
-- Benjamin
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-3-amd64 (SMP w/23 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages elogind depends on:
ii dbus 1.14.10-4+b1
ii debconf 1.5.86
ii init-system-helpers 1.66
ii libacl1 2.3.2-2
ii libc6 2.38-13
ii libcap2 1:2.66-5
ii libelogind0 246.10-1debian1
ii libpam0g 1.5.3-7
ii libselinux1 3.5-2+b2
ii libudev1 256.1-2
ii lsb-base 11.6
ii sysvinit-utils [lsb-base] 3.09-2
Versions of packages elogind recommends:
ii libpam-elogind 246.10-1debian1
pn polkitd <none>
elogind suggests no packages.
-- no debconf information
-------------- next part --------------
Reading package lists...
Building dependency tree...
Reading state information...
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: libelogind0 but 255.5-1debian2 is to be installed
Recommends: polkitd
E: Unable to correct problems, you have held broken packages.
More information about the Debian-init-diversity
mailing list