Your message dated Thu, 01 Jan 2026 16:06:50 +0000
with message-id <[email protected]>
and subject line Bug#1039388: fixed in sysrqd 14-5
has caused the Debian Bug report #1039388,
regarding sysrqd: ships sysv-init script without systemd unit
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1039388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039388
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sysrqd
Severity: important
User: [email protected]
Usertags: missing-systemd-service
Dear Maintainer(s),
sysrqd has been flagged by Lintian as shipping a sysv-init script
without a corresponding systemd unit file. The default init system in
Debian is systemd, and so far this worked because a transitional
sysv-init-to-unit generator was shipped by systemd. This is in the
process of being deprecated and will be removed by the time Trixie
ships, so the remaining packages that ship init scripts without
systemd units will stop working.
There are various advantages to using native units, for example the
legacy generator cannot tell the different between a oneshot service
and a long running daemon. Also, sanboxing and security features
become available for services. For more information, consult the
systemd documentation:
https://www.freedesktop.org/software/systemd/man/systemd.unit.html
You can find the Lintian warning here:
https://lintian.debian.org/sources/sysrqd
In case this is a false positive, please add a Lintian override to
silence it and then close this bug.
Thanks!
--- End Message ---
--- Begin Message ---
Source: sysrqd
Source-Version: 14-5
Done: Syed Shahrukh Hussain <[email protected]>
We believe that the bug you reported is fixed in the latest version of
sysrqd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Syed Shahrukh Hussain <[email protected]> (supplier of updated
sysrqd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 31 Dec 2025 14:03:34 +0500
Source: sysrqd
Built-For-Profiles: noudeb
Architecture: source
Version: 14-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Syed Shahrukh Hussain <[email protected]>
Closes: 1039388
Changes:
sysrqd (14-5) unstable; urgency=medium
.
* QA upload.
* Added service file (Closes: #1039388).
Checksums-Sha1:
a739e330ab7e9b7d684e76e90cf82e9feb443a98 1735 sysrqd_14-5.dsc
c0cd9c520e39e20b13e8f94d1688cc81dafeaa4f 3172 sysrqd_14-5.debian.tar.xz
e912b6192cdb684fee0ad50732cdf5e8c356eff9 14887 sysrqd_14-5_source.buildinfo
Checksums-Sha256:
fe864a229c049310c9b9322e689c286abc359b5416372174e41d226e944d716c 1735
sysrqd_14-5.dsc
999f532bb556e2f4261c99c5db9fc766a9121f9b4cbca44450f4172668b6024e 3172
sysrqd_14-5.debian.tar.xz
4926678654ad74f7198bb28f1b98ec6f06879c5665590fd6874c431c2cffc2c8 14887
sysrqd_14-5_source.buildinfo
Files:
d4bf3de567820196172b0541cdf91e55 1735 admin optional sysrqd_14-5.dsc
c84bdf425271907e1bc9a85c1f553670 3172 admin optional sysrqd_14-5.debian.tar.xz
e27a0971448a5c19b06a91d9fa08383b 14887 admin optional
sysrqd_14-5_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEd8lhnEnWos3N8v+qQoMEoXSNzHoFAmlWk20ACgkQQoMEoXSN
zHpEbw/+LlRW0lVKDH8oCg5rNjcnkZ2jL1j5KU7AMjUFD6TtI6NHx5BMfKOsGqf3
3LWb/9tmsMuqlU5DPqZsMnM/qC18epGLK0NDPTQA361GN9F1GNmX1b7e8ARGDulY
k7PplablKB2IFrdRJetZm9oIhfjccWEcyFDWxn8GxXtIvtM0cdSng5ja+o7zHlK+
J21SUHUEE36qe9EjydBv8xV8BmCIK7xMeI3n7nqx08SRqtfHhRrWGzydiytELMe2
IvaFcSF6/HIHhQBKO1oiI49MqG0eJseJUgStisjkDzHoqe5/A6X25hZMDkxvs1RE
w6gYClDDit5UI9f+j+5fQuJyeHyBK8IqUz4YkNCf5okQBdRXVF5qMEFFo4y19fmt
2mqEPAtwYuN15K4CHja51hpstzED5DJT1ZAFt+qvexs1DIUnzTstb1DrUJctucPw
cOObdPSh+/HslViADBc1ZXGt8UhfdGcIAEMdQ63sumdRKEWaUj+zXFrSxGUj4H5G
08Kv7zwdWmebH5+7CQTzRs/5bu1NszKFB04kwaaHtkXStohY24upJs2LfPqoEhDD
BIyrtfI8ZyZ7QJVzLbZJN549ir/73m3Mnc36PxlPMCSitXgvzYY+lUbLcIYABfih
pIsxjyeUSSY34nxVdLA5bGA0Qw/wxTGSQA5lDhQFVkYY4Legh3A=
=KJPU
-----END PGP SIGNATURE-----
pgpGbNSmjl_Fz.pgp
Description: PGP signature
--- End Message ---
