Your message dated Sun, 19 Oct 2025 11:18:58 +0000
with message-id <[email protected]>
and subject line Bug#1039129: fixed in apt-cacher 1.7.32
has caused the Debian Bug report #1039129,
regarding apt-cacher: 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.)
--
1039129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039129
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apt-cacher
Severity: important
User: [email protected]
Usertags: missing-systemd-service
Dear Maintainer(s),
apt-cacher 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/apt-cacher
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: apt-cacher
Source-Version: 1.7.32
Done: Mark Hindley <[email protected]>
We believe that the bug you reported is fixed in the latest version of
apt-cacher, 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.
Mark Hindley <[email protected]> (supplier of updated apt-cacher 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: SHA256
Format: 1.8
Date: Sun, 19 Oct 2025 11:43:25 +0100
Source: apt-cacher
Architecture: source
Version: 1.7.32
Distribution: unstable
Urgency: medium
Maintainer: Mark Hindley <[email protected]>
Changed-By: Mark Hindley <[email protected]>
Closes: 1039129
Changes:
apt-cacher (1.7.32) unstable; urgency=medium
.
* Add systemd unit. (Closes: #1039129)
Checksums-Sha1:
6cb621ae029e2ad93e47e46db931a77159457ab1 1605 apt-cacher_1.7.32.dsc
067001c9309e24fbe0c520143a8736e34b1b3412 97352 apt-cacher_1.7.32.tar.xz
f713a1aeaeba8213e226ce77603b852beadf40f1 5230 apt-cacher_1.7.32_amd64.buildinfo
Checksums-Sha256:
0e835832c2dcaf63bc319002f4541353a4d56aafd120c561a7bd92d41014c385 1605
apt-cacher_1.7.32.dsc
9c219812cfe12cce257aff46157d834088691d913d4aeb97eebb349c726e2b82 97352
apt-cacher_1.7.32.tar.xz
bc97a2ce2250a844a30c67720ca2665f1ab23a97f9c889f967c758b4d3dd90d2 5230
apt-cacher_1.7.32_amd64.buildinfo
Files:
b1e6e20b28c3a8044e9d0c54f4d9164e 1605 net optional apt-cacher_1.7.32.dsc
8289287f45615cff6ec674290cba19cc 97352 net optional apt-cacher_1.7.32.tar.xz
f0a7a41e6cc30ef425d51f0b20c7e6ff 5230 net optional
apt-cacher_1.7.32_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEUGwVpCsK9aCoVCPu0opFvzKH1kkFAmj0w5wACgkQ0opFvzKH
1kl/Rg/+LZ08bQjiaeQvUgsGFPW/MlLsediB/pzxcsyuBYcJ25QaUOV+Th8GQs6m
us1NyfQnT0AEQF31vjcvwL/VZZZt+gUytQayWSrsmbLCY5xzJaY+mpx9GJ9twXEb
QkR4MLJ9sROOKxG2NNbYYs0LCUyxAaxJn9N15cpEEnRC3UHN7l78asMKLE0ErNzW
JVoA7HMcSnizdti9KCUxVoOy/zhTV4OCrcB3bYpkolDQD5TEcredAcHAUIfQEVti
WzTRSFiGuMQwTvllcJhHP0eWYtvYOFx8sVHKT14x7ekKdtBW9k+UzT/SMniAf3P7
oWWSfQd5+kezUoGHGYZA1W83qdPAFW0kpJStgxcbw7ZQWP4Sb5MkCjXlt8dv9x3n
COE4TWCQvmwH4QEEpviMIk06vr2yTBW/bMXQGlNhUy2qH0Sq1KtGn1OoVKf3g8d4
2Ck7nb+FFstH5wrEMo6MLzHLEnjvbcxx4UEAsPLY+9dEu7xKwm5KV/o01bcTxnhY
tsl/PlHXZZNjGUBMGzHWpoYor800RhZB6xPb/XsqYsNpxsUuA9oSocQpbgpwmphA
j9+907dONr7uQz/Q4SwPzi7ci63KDtdw9aIxLY/73Hkgl+09eAXJoyFZN+azgT75
ESEJ/U7MSfc8mZnuCHwJO6Zo0wzoQba50ggb7lyGUxH1V6yJT9Y=
=38XR
-----END PGP SIGNATURE-----
pgpDs3RHb_LMJ.pgp
Description: PGP signature
--- End Message ---
