Your message dated Thu, 07 Nov 2024 16:49:02 +0000
with message-id <[email protected]>
and subject line Bug#1039172: fixed in dibbler 1.0.1-2
has caused the Debian Bug report #1039172,
regarding dibbler: 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.)
--
1039172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039172
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dibbler
Severity: important
User: [email protected]
Usertags: missing-systemd-service
Dear Maintainer(s),
dibbler 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/dibbler
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: dibbler
Source-Version: 1.0.1-2
Done: наб <[email protected]>
We believe that the bug you reported is fixed in the latest version of
dibbler, 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.
наб <[email protected]> (supplier of updated dibbler 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: Thu, 07 Nov 2024 15:22:27 +0100
Source: dibbler
Architecture: source
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Package Salvaging Team <[email protected]>
Changed-By: наб <[email protected]>
Closes: 894556 1039172
Changes:
dibbler (1.0.1-2) unstable; urgency=medium
.
* QA upload.
* Adopt to the Salvage Team for removal in forky (Closes: #894556)
* d/NEWS: add upstream orphaning and downstream removal-in-forky notice
* d/dibbler-{client,relay,server}.service: add (Closes: #1039172)
Checksums-Sha1:
d42714004ff164d9912b662dbf8292ea7faea4ac 2278 dibbler_1.0.1-2.dsc
5253323d3e6cfbbc62d0dfbc061cc6096072ad6e 21032 dibbler_1.0.1-2.debian.tar.xz
ceeacc387bad6f1af6c34c66be79545e128e1d13 7550 dibbler_1.0.1-2_amd64.buildinfo
Checksums-Sha256:
16f34f04c5145371bca20753de27dd7500f107c7b28a659a9bb26e85fecc8b40 2278
dibbler_1.0.1-2.dsc
cf3b4dbb2102dea58eab8dc79e1fe57fe6deb9482b374b7e1768cbb0a4093711 21032
dibbler_1.0.1-2.debian.tar.xz
012ddd15cf0fe297c5d0b90f5c856241d4c76ceeedf109a6ef05dcc7c4bfd961 7550
dibbler_1.0.1-2_amd64.buildinfo
Files:
3b7a31bbcdccd878f60f00e5cc79462c 2278 admin optional dibbler_1.0.1-2.dsc
11dd55d20b68f0550b02955464dc50d2 21032 admin optional
dibbler_1.0.1-2.debian.tar.xz
bca868e6c1dc0cb495c18f6e6c8f7727 7550 admin optional
dibbler_1.0.1-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmcs7FIRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGHxQ/9HKWNAiMjKBTsSZ3h0P9KNYfNKKy9cJB0
Ne4JoJvUCL8Mk/B3Y+3bKWryf7xFm4AV1L60D4LgpDqMX62Qs73qJl/76zESkfcN
sn6T9yk+jxHt6Sy6Q39aqEZXLaLHpCkQRcSrHXQ09ZxPIWsVTNfa4nTR8o8nkp7D
OFF0m/LiSoEetmQ4eU+RyZt6HtkAIqOm+OMiuPQmiDFQXkWuKsEKGUxUnOTK8xoT
kGmwLM2Cgo5bwVQ0N/Us5grlRyWVnMd9btPXP2NvMIDIH9SvT6q6zQnpcAZxDdlt
e2ZIqS3R0uYX/bKhOS3vgKuGhpu8NnYjO3ugYGznAGdS6lksOOZ6iCjapazWDK0n
e9GmYUM0slsUoI8MeR7mgDIDHdy7JTfxziHoLiSLo7wEoLeuyuo9jwlBve2+h5CU
ThkIwbEwv4Wy+qRBj3wGVxLvvW+iV0/750nJLfnLskRZU/u95opEWiXqCCa+U5pf
xCttAXaEp1pJ2NDqThrL7reUKKqAmQoOIf1z1/fl9GKQWNxHRWDctoIqMeVR8GqY
FTP5FJJ/GBHTP6Mq/97oFvp+JG0VJJwi9ZbpP885AHH3UApi+iVnsP9S79Du9MpU
CPXJYsWaeK2T80FRlUCxyYLnALcRfVO2i3xEMuwUyPIMQzgGSuJTOdmzKseSkYZ8
kRz9EHhEX6c=
=36RR
-----END PGP SIGNATURE-----
pgpe80gvkc46K.pgp
Description: PGP signature
--- End Message ---
