Simon, Thanks for this.
On Mon, Jan 22, 2024 at 10:47:08AM +0000, Simon McVittie wrote: > Package: libelogind0 > Version: 252.9-1debian3 > Severity: important > Tags: trixie sid > > Steps to reproduce: attempt to install a Debian unstable virtual machine > (I used amd64) with sysvinit-core, libpam-elogind, dbus-x11, and a small > X11 system (I used xdm and openbox). > > Expected result: libelogind0 is a drop-in replacement for libsystemd0 in > this scenario, This used to be the case, but in sid/trixie to resolve[1] the lag in upstream elogind releases[2], we now have a patch for elogind which enables it to use libsystemd0 directly[3]. That means that the expected dependencies are now libpam-elogind -> elogind -> libsystemd0 with procps installable and libelogind0 not installed. So, I am curious why libelogind0 was being installed in your VM. Did you request it specifically? Bin:libelogind0 is still built by src:elogind and available in the archive. I hesitated to remove it before being certain that the elogind cgroups patch to use libsystemd0 was reliable. But maybe libelogind0 should become a dependency package to smooth upgrades? Or is there another detail in the dependency chain I have missed? Mark [1] https://bugs.debian.org/1052064 [2] Upstream has still not released 254 [3] https://git.devuan.org/devuan/elogind/src/branch/debian/debian/patches/Use-libsystemd0-compatible-cgroups-layout.patch
