#1016561 sysvinit-core: Please recommend systemd-tmpfiles and systemd-tmpfiles

Package:
sysvinit-core
Source:
sysvinit-core
Description:
System-V-like init
Submitter:
GSR
Date:
2025-02-12 15:24:02 UTC
Severity:
normal
#1016561#5
Date:
2022-08-02 22:04:29 UTC
From:
To:
Hi:

The package already "Recommends: orphan-sysvinit-scripts", in same
fashion it could recommend systemd-tmpfiles and systemd-tmpfiles (or
the packages that provide those, systemd-standalone-tmpfiles and
systemd-standalone-sysusers, whatever follows Debian policy better).
Otherwise in cases like upgrading lvm2 (see bug #1014565) the full
systemd is installed unnecessarily.

Cheers,
GSR

#1016561#10
Date:
2022-08-02 23:00:52 UTC
From:
To:
That's a bug in the dependency that pulls in systemd.

Sysvinit is often installed in small containers, and I would be wary of
bloating them by 460KB with gratuitous dependences.


Meow!

#1016561#15
Date:
2022-08-02 23:20:58 UTC
From:
To:
This is weird, but I looked at how debootstrap resolves dependencies,
and this is indeed a problem. Did anyone look at whether adding the
systemd-standalone-tmpfiles package to the list of dependencies, instead
of relying on the virtual package, helps?

It’d be a Recommends. Power users have been annoyed since squeeze
enabled the installation of Recommends by default and have been
disabling it ever since :|

My guess is you don’t have systemd pinned away.

$ cat /etc/apt/preferences.d/systemd
Package: systemd
Pin: version *
Pin-Priority: -1

Does it still want to install systemd with this enabled? (If so, apt
bug.) Does it successfully resolve this to systemd-standalone-tmpfiles
instead of exploding and refusing to do anything? (I don’t have a
suitably up-to-date sid system handy.)

Given how Debian currently treats nōn-systemd users I think asking
them to run with such a pinning (and not annoying maintainers so
much that they remove the standalone packages altogether) might be
sensible :/

Meow,
//mirabilos

#1016561#20
Date:
2022-08-03 06:59:51 UTC
From:
To:
If running debootstrap with --include systemd-standalone-tmpfiles replicates
changing the dependencies, then yes that fails.

Or do have you a better way of testing debootstrap with different dependencies I
haven't thought of?

I share that concern. And this solution wouldn't fix the issue for other inits
or initless containers.

Mark

Mark

#1016561#25
Date:
2022-08-03 07:04:40 UTC
From:
To:
The best solution I can think of here is that all packages, systemd included,
use the separately packaged tmpfiles implementation and that is the dependency
that debhelper generates when required.

But I don't know how to get the systemd maintainers to consider that.

Mark