Bug#1056321: elogind conflicts with same version libelogind
Low Salt Popcorn
thelowsaltpopcorn at hotmail.com
Thu Nov 23 17:26:39 GMT 2023
Wouldn't it be better, or at least more elegant, to turn
libelogind0 into a dummy transitional package that pulls in
libsystemd0? Here's the result of trying to install elogind
using the apt front end.
$ sudo apt install -t testing elogind
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:
apt : Depends: libapt-pkg6.0 (>= 2.7.6) but it is not going to be
installed
elogind : Depends: dbus (>= 1.9.14)
Conflicts: libelogind0 but 246.10-1debian1 is to be installed
Recommends: polkitd
# [etc]
I must note that the aptitude frontend is able to install
elogind using the default solution No. 1.
$ sudo aptitude install -t testing elogind
# [etc]
Install the following packages:
1) libsystemd0 [254.5-1 (testing)]
Accept this solution? [Y/n/q/?]
On the other hand, an "apt full-upgrade" will automatically
remove elogind and replace it with systemd, which is NOT what
a user that's installed elogind would want. (An "apt upgrade"
will abort with an "unmet dependencies" conflict.)
More information about the Debian-init-diversity
mailing list