elogind 246.9-1+debian1

Mark Hindley mark at hindley.org.uk
Mon Dec 21 19:01:52 GMT 2020

On Mon, Dec 21, 2020 at 07:02:37PM +0100, Adam Borowski wrote:
> Could you please expand these entries?  Neither bug is "please update to the
> new version".
> I'd suggest something like:
>     * Merge upstream v246.9
>       + Support ABI of systemd-logind 246 (Closes: #968379).
>       + Log to syslog rather than kernel log (Closes: #964006).


> >   * Refresh quilt patch.
> >   * d/control: update Vcs-* following gitea migration.
> >   * Document solutions for libelogind0/libsystemd-dev build-depends
> >     conflict.
> >   * Change rootlibdir to /lib.
> Could you please provide a rationale for this?  Booting the actual system
> from separate /usr is long since unsupported (must be one fs or mount from
> initrd) thus early-boot rationales no longer apply; there's a migration off
> /lib; moving stuff around can cause problems with usrmerge (which is bad IMO
> but currently the default).

I originally made the change[1] in response to Devuan #482[2]. Yes, the poster
was using lvm without an initrd. But it fixed his issue without causing any
regressions that I am aware of. Although I accept usrmerge is not the default on

It also mirrors the systemd setup which (still?) has libsystemd0 in /lib.

Is emptying /lib a target for bullseye?



[1]  https://git.devuan.org/devuan/elogind/commit/c18b0e4a4b6a0ca0b1100462526cdacaee827e25

[2]  https://bugs.devuan.org/482

More information about the Debian-init-diversity mailing list