Your message dated Fri, 07 Nov 2025 00:09:13 +0100
with message-id <[email protected]>
and subject line lintian doesn't currently produce the claimed error
has caused the Debian Bug report #1039167,
regarding debian-edu-install: 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.)
--
1039167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039167
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debian-edu-install
Severity: important
User: [email protected]
Usertags: missing-systemd-service
Dear Maintainer(s),
debian-edu-install 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/debian-edu-install
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 ---
I thought I'd try fixing this myself, so built the latest version, and
lintian (2.127.0) does not actually tag this package with the claimed
error.
That being the case, it seems there's no need to add an override (as
suggested in the original report) so I guess one should just close the
bug and thus allow the package back into testing (so I'm doing that
here).
Cheers, Phil.
--
Philip Hands -- https://hands.com/~phil
--- End Message ---
