Bug#898388: systemd-sysv: shutdown command always fails

[Meeuwissen Olaf]

Michael Biebl writes:

> Am 14.05.2018 um 01:23 schrieb Meeuwissen Olaf:
>
>> Definitely not from my POV.  I'm off now installing dbus myself because
>> systemd-sysv didn't think it important enough to do that for me :-(
>
> Well, the systemd package does do it for you, but you actively prevented
> dbus from being installed, so I don't think it's justified for you to
> complain about that.

I think that systemd-sysv should think for itself what is and is not
necessary for it to work.  It should not rely on systemd doing that for
it (because systemd probably doesn't really give a hoot about
systemd-sysv).

> In any case, yes, it's a good idea to have dbus installed and we do
> recommend you do so. I also recommend that you install libpam-systemd,
> so your user sessions are moved into proper cgroups.

I noticed this in the libpam-systemd package description ;-)

  Packages that depend on logind functionality need to depend on
  libpam-systemd.

Seeing that shutdown, scheduled shutdowns, depends on logind, shouldn't
systemd-sysv depend on it?  Would pull in dbus via a Depends: as well.

Anyway, this doesn't seem to be going anywhere and you're not going to
add a one-line dependency that would have saved me half a day trying to
find out why unattended-upgrades didn't work as advertised in the reboot
department, I'll call it quits.

Hope this helped anyway,
--
Olaf Meeuwissen, LPIC-2       FLOSS Engineer -- EPSON AVASYS CORPORATION
       Free Software Foundation Associate Member since 2004-01-27
    Support Free Software                  https://my.fsf.org/donate
    Join the Free Software Foundation        https://my.fsf.org/join