Bug#992711: debhelper: Please provide backport for bullseye
Michael Biebl
biebl at debian.org
Mon Aug 23 22:31:47 BST 2021
Am 23.08.21 um 22:29 schrieb Mattia Rizzolo:
> We are talking about this 2-line change in update-rc.d:
> https://salsa.debian.org/debian/init-system-helpers/-/commit/552e993488a403bf88aa342f73bf0b22ce62ff16
> <https://salsa.debian.org/debian/init-system-helpers/-/commit/552e993488a403bf88aa342f73bf0b22ce62ff16>
Sure, we can add that. It's simple enough.
And as I tried to explain, it's a codepath that shouldn't be hit in the
"normal" case anyway as either systemd is installed or the package in
question is using a newer compat level.
> I think it's feasible to add that in buster in the next point release,
> and with it allow debhelper &co to safely move the .service files also
> in bullseye-backports.
>
In bullseye, everything is installed in /lib/system/system.
It just feels a bit weird that we now start moving files in a "stable"
release (I consider bullseye-backports as part of stable).
That's not really a technical concern though.
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20210823/db6817fd/attachment-0001.sig>
More information about the Pkg-systemd-maintainers
mailing list