Control: severity -1 wishlist On Tue, 2022-08-16 at 18:46 +0200, Adam Borowski wrote: > On Tue, Aug 16, 2022 at 03:13:35PM +0100, Luca Boccassi wrote: > > On Tue, 16 Aug 2022 13:13:53 +0200 Johannes Schauer Marin Rodrigues > > > The package passwd=1:4.11.1+dfsg1-2 in the archive does not have the > > > dependency on "systemd | systemd-tmpfiles" and was compiled with > > > debhelper 13.6. > > > > > > This currently installs systemd on a systems that don't need it, > > which > > > is especially bad for minimal and embedded systems and/or containers. > > > Thus setting the severity to serious. Feel free to adjust. > > > This looks entirely correct to me. You can install the -standalone > > variant if you prefer a slightly smaller footprint, which is provided > > exactly for those non-default use cases. > > No, the "passwd" package does not need systemd (nor its -standalone subset > as evidenced by currently working fine). And the added dependency has > the tiny little effect of effectively dropping three official architectures > plus a number of unofficial but known to be worked on. > > Breaking machines that fail to boot with systemd, or are configured in a way > that doesn't work with it is also not nice. And minimal/embedded systems > really don't want the extra 460KB -standalone binary, either. > > > The regression here is commit 0e313c2f58df0f8ce6389380d735767dfaa936ab; > I've read changelogs of all packages that have since gained this automatic > dependency¹, and it appears none have a mention of relying on tmpfiles > on !systemd, with one exception -- tomcat9 -- which manually depends on > systemd-tmpfiles thus doesn't need the debhelper change. > > The stated reason for the change, roundcube (#1013969) hasn't been uploaded > yet thus it still works fine via cron. If the maintainer wants to migrate > to systemd ways, he can add the dependency on systemd-tmpfiles by hand, > just like tomcat9 does. That'd be a regression but oh well. > > > Thus, it doesn't appear like a revert would have any downsides
- yes, the passwd package does need 'systemd | systemd-tmpfiles' as it ships a tmpfile, thus the dependency is entirely correct - no official architecture is dropped, both packages are available on all official release architecture plus a number of ports - as tmpfiles.d is ufficially supported, it is up to the 3 !linux unofficial ports to provide an alternative implementation if so they will, or to get src:systemd to build minimally there. With recent changes I've done to the Meson usage, it might even be quite simple to achieve, and might only require a couple of lines in d/rules of src:systemd that, if someone provided a MR for, I might be happy to include and maintain - for the millionth time, installing the systemd (or systemd-tmpfiles) package does not make a machine boot with systemd, that is done by the systemd-sysv package which is different and separate, and you know this perfectly well, so please kindly stop spreading this blatantly untrue piece of information Thus, this is a wishlist at best and most likely a close+wontfix like the half a dozen of identical ones that preceded it. -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
