elogind plan

Adam Borowski kilobyte at angband.pl
Mon Dec 3 09:38:49 GMT 2018

On Mon, Dec 03, 2018 at 09:11:30AM +0000, Mark Hindley wrote:
> On Sun, Dec 02, 2018 at 11:42:26PM +0100, Adam Borowski wrote:
[reboot/shutdown needs packagekit-1 work]
> > Besides that, with libpam-elogind-compat installed xfce works for me, and
> > since today so does mate.
> Good news.
> > But, that compat package is not going to hit buster (nor even sid), so we'd
> > need to fix dependencies.  I think smcv's suggestion from January would work
> > -- we can replace depends on "libpam-systemd" with "default-logind | logind",
> > with elogind declaring Provides: logind (and on some derivatives, also
> > default-logind).  That would handle packages needing this part of the
> > functionality.  Does this sound ok to you?  If so, please say so -- I still
> > have a set of patches implementing this, thus filing bugs would be far less
> > work for me.  And if you have a different but similar solution, it's likely a
> > sed job on the patches would be enough.
> I don't see any problems with that approach, but we will need to get the virtual
> package names formally agreed.

Simon: could you please tell us if you still think your old idea is good?

In January, I prepared a set of patches for all packages with a
libpam-systemd dependency that don't have a direct dep on systemd (and it
turned out some of direct deps are spurious), the packages are at:
    https://angband.pl/debian logind main
They went through only very rudimentary testing, and require updates and
re-testing for current state, obviously.  But that's a lot easier than doing
the work from scratch.

Renaming the virtual package is no problem at all -- all it'd take is a sed
command over the dir with diffs.  But you may want an approach that differs
beyond mere names.

> > There's also the matter of upgrades: there's a need to be able to switch
> > from systemd to sysvinit+elogind, which you can't currently do (systemd's
> > prerm refuses to remove while it's pid 1).
> The impression I had received was that it might be difficult to persuade
> systemd's maintainers to remove that restriction. Do you know if anyone has
> actually tried asking them?

Might require some thinking first.  And testing to know what's actually
wrong and what works.

But, easy but long task first.  I'd go with the logind dependencies first,
as they affect many packages, and would start with an one-line change in
diff -Nru systemd-238/debian/control systemd-238/debian/control
--- systemd-238/debian/control  2018-05-26 10:31:29.000000000 +0200
+++ systemd-238/debian/control  2018-06-05 01:31:05.000000000 +0200
@@ -205,6 +205,7 @@
          libpam-runtime (>= 1.0.1-6),
          systemd-shim (>= 10-3~) | systemd-sysv
+Provides: logind (= ${binary:Version}), default-logind (= ${binary:Version})
 Description: system and service manager - PAM module
  This package contains the PAM module which registers user sessions in
  the systemd control group hierarchy for logind.

⣾⠁⢠⠒⠀⣿⡁ Ivan was a wordly man: born in St. Petersburg, raised in
⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned
⠈⠳⣄⠀⠀⠀⠀ to the city of his birth to die.

More information about the Debian-init-diversity mailing list