Package: elogind Version: 246.10-1debian1 Severity: normal Dear Maintainer,
The systemd alternative, elogind, appears to conflict with its apparent support library (libelogind0). Is this a packaging oversight? Or this part of a plan to eventually deprecate elogind as an install option? Below is a prettifed shell output showing the conflict between the version of elogind vs. libelogind in Testing (also Unstable). $ apt show elogind/testing libelogind0/testing | grep -E '^(Package|Version|Depend|Conflicts)' Package: elogind Version: 252.9-1debian2 Depends: libacl1 (>= 2.2.23), libc6 (>= 2.34), libcap2 (>= 1:2.10), libmount1 (>= 2.19.1), libpam0g (>= 0.99.7.1), libselinux1 (>= 3.1~), libudev1, libsystemd0, dbus (>= 1.9.14) Conflicts: libelogind0, systemd Package: libelogind0 Version: 252.9-1debian2 Depends: libc6 (>= 2.34), libcap2 (>= 1:2.10) Conflicts: libsystemd0, systemd A casual look at the Conflicts field for "elogind" suggests a possible fix. Maybe you could add a "versioned" conflict for libelogind, something like: libelogind (>= xxx.xx)? If elogind is to be phased out, maybe an appropriate notice should be posted and perhaps a transitional dummy package should be made? -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN 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-3 ii debconf 1.5.82 ii init-system-helpers 1.65.2 ii libacl1 2.3.1-3 ii libc6 2.37-12 ii libcap2 1:2.66-4 ii libelogind0 246.10-1debian1 ii libpam0g 1.5.2-9.1 ii libselinux1 3.5-1 ii libudev1 254.5-1 ii lsb-base 11.6 ii sysvinit-utils [lsb-base] 3.08-3 Versions of packages elogind recommends: ii libpam-elogind 246.10-1debian1 pn polkitd <none> elogind suggests no packages. -- no debconf information
