Bug#1016561: sysvinit-core: Please recommend systemd-tmpfiles and systemd-tmpfiles
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
Bug#1016561: sysvinit-core: Please recommend systemd-tmpfiles and systemd-tmpfiles
On Wed, Aug 03, 2022 at 01:20:58AM +0200, Thorsten Glaser wrote: > > On Wed, 3 Aug 2022, Adam Borowski wrote: > > > On Wed, Aug 03, 2022 at 12:04:29AM +0200, GSR wrote: > > > > Otherwise in cases like upgrading lvm2 (see bug #1014565) the full > > 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? 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? > > Sysvinit is often installed in small containers, and I would be wary of > > bloating them by 460KB with gratuitous dependences. I share that concern. And this solution wouldn't fix the issue for other inits or initless containers. Mark Mark
Bug#1016561: sysvinit-core: Please recommend systemd-tmpfiles and systemd-tmpfiles
On Wed, 3 Aug 2022, Adam Borowski wrote: > On Wed, Aug 03, 2022 at 12:04:29AM +0200, GSR wrote: > > Otherwise in cases like upgrading lvm2 (see bug #1014565) the full 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? > Sysvinit is often installed in small containers, and I would be wary of > bloating them by 460KB with gratuitous dependences. 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 :| > > systemd is installed unnecessarily. 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 -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg /⁀\ The UTF-8 Ribbon ╲ ╱ Campaign against Mit dem tarent-Newsletter nichts mehr verpassen: ╳ HTML eMail! Also, https://www.tarent.de/newsletter ╱ ╲ header encryption!
Bug#1016561: sysvinit-core: Please recommend systemd-tmpfiles and systemd-tmpfiles
On Wed, Aug 03, 2022 at 12:04:29AM +0200, GSR wrote: > 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. 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! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Say what you want about Adolf, at least he was the man who ⢿⡄⠘⠷⠚⠋⠀ killed Hitler. Your turn, Vlad! ⠈⠳⣄
Bug#1016561: sysvinit-core: Please recommend systemd-tmpfiles and systemd-tmpfiles
Package: sysvinit-core Version: 3.03-1 Severity: normal 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 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages sysvinit-core depends on: ii debconf [debconf-2.0] 1.5.79 ii initscripts3.03-1 ii libc6 2.33-8 ii libselinux13.3-1+b1 ii mount 2.38-6 ii sysv-rc3.03-1 ii sysvinit-utils 3.03-1 Versions of packages sysvinit-core recommends: ii orphan-sysvinit-scripts 0.11 Versions of packages sysvinit-core suggests: pn bootlogd -- debconf information: sysvinit/hurd-fix-inittab:
