Bug#1039284: netkit-rwho: ships sysv-init script without systemd unit
The new implementation of rwho, see #1013361, does come with a systemd unit, it's waiting in the new queue.
Bug#489787: rwho -a fails when >1000 users logged in
The new rwho from ruptime, https://bugs.debian.org/1013361 has no such limit. It is waiting in the new queue to get processed.
Bug#360884: rwhod: There should be an option to configure the alarm interval
With the new ruptime, see https://bugs.debian.org/1013361 you can easily configure this option.
Bug#1039456: apt-xapian-index: missing depedency on python3-six
Package: apt-xapian-index Version: 0.53 Severity: normal apt-xapian-index uses python3-six in a single place but forget to declare a depedency on it apt-xapian-index would better be ported to properly use the "io" module dirrectly (one line change) $ grep ' six' /bin -r 2>/dev/null | grep import /bin/axi-cache:from six import StringIO $ dpkg -S axi-cache apt-xapian-index: /usr/bin/axi-cache Greetings, -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (450, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/6 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt-xapian-index depends on: ii python3 3.11.2-1+b1 ii python3-apt 2.6.0 ii python3-debian 0.1.49 ii python3-xapian 1.4.22-1 apt-xapian-index recommends no packages. Versions of packages apt-xapian-index suggests: ii python3-xdg 0.28-2 -- no debconf information
Bug#1039065: Removed package(s) from unstable
Version: 0.28.debian-7+rm Dear submitter, as the package human-icon-theme has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1039065 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1039065: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: human-icon-theme | 0.28.debian-7 | source, all --- Reason --- RoQA; Obsolete, unmaintained, alternatives exist -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1039...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1039065 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1039065: Removed package(s) from unstable
Version: 0.26.debian-6+rm Dear submitter, as the package tangerine-icon-theme has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1039065 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1039065: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: tangerine-icon-theme | 0.26.debian-6 | source, all --- Reason --- RoQA; Obsolete, unmaintained, alternatives exist -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1039...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1039065 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#520780: marked as done (please remove dependency on tangerine-icon-theme)
Your message dated Mon, 26 Jun 2023 00:03:34 +
with message-id
and subject line Bug#1039065: Removed package(s) from unstable
has caused the Debian Bug report #520780,
regarding please remove dependency on tangerine-icon-theme
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 ow...@bugs.debian.org
immediately.)
--
520780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: human-icon-theme
Version: 0.28.debian-3
Severity: normal
Tags: patch
Please could you remove the dependency on tangerine-icon-theme? This package
appears to be perfectly usable without it.
If tangerine-icon-theme provides some improvement, you could put it in
Recommends, or in Suggests, depending on how relevant it is.
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -ur human-icon-theme-0.28.debian.old/debian/control.in human-icon-theme-0.28.debian/debian/control.in
--- human-icon-theme-0.28.debian.old/debian/control.in 2009-03-22 18:26:34.0 +0100
+++ human-icon-theme-0.28.debian/debian/control.in 2009-03-22 18:39:49.0 +0100
@@ -23,7 +23,6 @@
Package: human-icon-theme
Architecture: all
Depends: ${misc:Depends},
- tangerine-icon-theme,
gnome-icon-theme
Section: non-free/x11
Description: Human Icon theme
--- End Message ---
--- Begin Message ---
Version: 0.28.debian-7+rm
Dear submitter,
as the package human-icon-theme has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1039065
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1039421: wvstreams: ships sysv-init script without systemd unit
Package: wvstreams Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), wvstreams 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/wvstreams In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039415: watchcatd: ships sysv-init script without systemd unit
Package: watchcatd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), watchcatd 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/watchcatd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039414: vzctl: ships sysv-init script without systemd unit
Package: vzctl Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), vzctl 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/vzctl In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039397: tircd: ships sysv-init script without systemd unit
Package: tircd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), tircd 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/tircd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039393: tetrinetx: ships sysv-init script without systemd unit
Package: tetrinetx Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), tetrinetx 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/tetrinetx In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039392: tenshi: ships sysv-init script without systemd unit
Package: tenshi Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), tenshi 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/tenshi In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039391: tcpspy: ships sysv-init script without systemd unit
Package: tcpspy Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), tcpspy 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/tcpspy In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039388: sysrqd: ships sysv-init script without systemd unit
Package: sysrqd Severity: important User: bl...@debian.org 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!
Bug#1039374: snmptrapfmt: ships sysv-init script without systemd unit
Package: snmptrapfmt Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), snmptrapfmt 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/snmptrapfmt In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039370: sleepd: ships sysv-init script without systemd unit
Package: sleepd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), sleepd 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/sleepd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039365: sendmail: ships sysv-init script without systemd unit
Package: sendmail Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), sendmail 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/sendmail In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039348: rinetd: ships sysv-init script without systemd unit
Package: rinetd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), rinetd 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/rinetd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039338: qpsmtpd: ships sysv-init script without systemd unit
Package: qpsmtpd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), qpsmtpd 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/qpsmtpd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039330: proxsmtp: ships sysv-init script without systemd unit
Package: proxsmtp Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), proxsmtp 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/proxsmtp In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039326: powerman: ships sysv-init script without systemd unit
Package: powerman Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), powerman 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/powerman In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039309: partimage: ships sysv-init script without systemd unit
Package: partimage Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), partimage 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/partimage In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039307: pads: ships sysv-init script without systemd unit
Package: pads Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), pads 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/pads In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039296: olpc-powerd: ships sysv-init script without systemd unit
Package: olpc-powerd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), olpc-powerd 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/olpc-powerd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039297: omnievents: ships sysv-init script without systemd unit
Package: omnievents Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), omnievents 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/omnievents In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039295: olpc-kbdshim: ships sysv-init script without systemd unit
Package: olpc-kbdshim Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), olpc-kbdshim 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/olpc-kbdshim In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039284: netkit-rwho: ships sysv-init script without systemd unit
Package: netkit-rwho Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), netkit-rwho 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/netkit-rwho In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039272: mpt-status: ships sysv-init script without systemd unit
Package: mpt-status Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), mpt-status 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/mpt-status In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039266: mini-httpd: ships sysv-init script without systemd unit
Package: mini-httpd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), mini-httpd 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/mini-httpd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039263: masqmail: ships sysv-init script without systemd unit
Package: masqmail Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), masqmail 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/masqmail In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039262: mason: ships sysv-init script without systemd unit
Package: mason Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), mason 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/mason In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039256: lprng: ships sysv-init script without systemd unit
Package: lprng Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), lprng 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/lprng In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039249: latd: ships sysv-init script without systemd unit
Package: latd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), latd 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/latd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039243: isakmpd: ships sysv-init script without systemd unit
Package: isakmpd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), isakmpd 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/isakmpd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039238: iptotal: ships sysv-init script without systemd unit
Package: iptotal Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), iptotal 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/iptotal In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039223: httpry: ships sysv-init script without systemd unit
Package: httpry Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), httpry 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/httpry In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039216: gsm0710muxd: ships sysv-init script without systemd unit
Package: gsm0710muxd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), gsm0710muxd 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/gsm0710muxd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039201: freewnn: ships sysv-init script without systemd unit
Package: freewnn Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), freewnn 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/freewnn In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039200: freelan: ships sysv-init script without systemd unit
Package: freelan Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), freelan 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/freelan In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039192: esekeyd: ships sysv-init script without systemd unit
Package: esekeyd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), esekeyd 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/esekeyd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039190: elida: ships sysv-init script without systemd unit
Package: elida Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), elida 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/elida In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039178: dnprogs: ships sysv-init script without systemd unit
Package: dnprogs Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), dnprogs 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/dnprogs In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039177: dmucs: ships sysv-init script without systemd unit
Package: dmucs Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), dmucs 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/dmucs In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039170: dhis-server: ships sysv-init script without systemd unit
Package: dhis-server Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), dhis-server 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/dhis-server In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039169: dhis-client: ships sysv-init script without systemd unit
Package: dhis-client Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), dhis-client 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/dhis-client In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039156: cpufreqd: ships sysv-init script without systemd unit
Package: cpufreqd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), cpufreqd 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/cpufreqd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039155: couriergraph: ships sysv-init script without systemd unit
Package: couriergraph Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), couriergraph 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/couriergraph In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039152: c-icap: ships sysv-init script without systemd unit
Package: c-icap Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), c-icap 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/c-icap In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039148: canna: ships sysv-init script without systemd unit
Package: canna Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), canna 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/canna In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039144: bwbar: ships sysv-init script without systemd unit
Package: bwbar Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), bwbar 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/bwbar In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039139: bluemon: ships sysv-init script without systemd unit
Package: bluemon Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), bluemon 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/bluemon In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039135: bandwidthd: ships sysv-init script without systemd unit
Package: bandwidthd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), bandwidthd 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/bandwidthd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039133: avr-evtd: ships sysv-init script without systemd unit
Package: avr-evtd Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), avr-evtd 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/avr-evtd In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039127: apf-firewall: ships sysv-init script without systemd unit
Package: apf-firewall Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), apf-firewall 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/apf-firewall In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
Bug#1039124: amavisd-milter: ships sysv-init script without systemd unit
Package: amavisd-milter Severity: important User: bl...@debian.org Usertags: missing-systemd-service Dear Maintainer(s), amavisd-milter 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/amavisd-milter In case this is a false positive, please add a Lintian override to silence it and then close this bug. Thanks!
binutils-msp430_2.24~ti3_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 25 Jun 2023 14:06:39 -0700 Source: binutils-msp430 Architecture: source Version: 2.24~ti3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Vagrant Cascadian Closes: 1039064 Changes: binutils-msp430 (2.24~ti3) unstable; urgency=medium . * debian/rules: Pass libdir to configure. (Closes: #1039064) * debian/control: Apply "wrap-and-sort -st" to Build-Depends. * Remove needless debian/dirs file. * Remove empty patchlist file. * debian/rules: Drop unused VERSION variable. Checksums-Sha1: dd5f61570f34d313cb84b674b2bf2e837ac02ab5 1190 binutils-msp430_2.24~ti3.dsc 747cc2c322081cd46a09fda68e798a0df96079d5 3424 binutils-msp430_2.24~ti3.tar.xz Checksums-Sha256: b0eb34b6af8338f5eb1c17279686a4ab174ca742291eee3c014fcbab6799ddbc 1190 binutils-msp430_2.24~ti3.dsc ad0fb9c21d558a8917b66b3d2dc189cbbaa73fa1cf827f1c9886cc02543a56cd 3424 binutils-msp430_2.24~ti3.tar.xz Files: ad4b9997579b49765d3a25ada9c454c2 1190 devel optional binutils-msp430_2.24~ti3.dsc 954bec48377e2564a501db0960f6968a 3424 devel optional binutils-msp430_2.24~ti3.tar.xz -BEGIN PGP SIGNATURE- iJYEARYKAD4WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCZJitZyAcdmFncmFudEBy ZXByb2R1Y2libGUtYnVpbGRzLm9yZwAKCRDcUY/If5cWqm9rAP9F1x5uijN0jSAm 4eMtIp0JYrdEsiC/GZyWpYDg6PcedgD6As/vdDPpFHUXYfVWGMGXDsMmAOqanacP LU0ISVvqdQQ= =uWnx -END PGP SIGNATURE-
Processing of binutils-msp430_2.24~ti3_source.changes
binutils-msp430_2.24~ti3_source.changes uploaded successfully to localhost along with the files: binutils-msp430_2.24~ti3.dsc binutils-msp430_2.24~ti3.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1039086: collada2gltf: Embed yajl
Source: collada2gltf Severity: serious Justification: devref Dear Maintainer, Your package embed a copy a yajl Could you: - build against yajl package - remove by repacking the code copy in order to avoid in the future accidental code compilation against the embed code copy Thanks Bastien -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 6.1.0-9-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1039080: antigrav: FTBFS with libsdl1.2-compat-dev: missing build-dependencies
Source: antigrav Version: 0.0.3-10 Severity: important Tags: ftbfs trixie sid I tried recompiling antigrav with libsdl1.2-compat-dev instead of libsdl1.2-dev, in preparation for having src:sdl12-compat take over the libsdl1.2-dev package name. I found that antigrav failed to build from source due to several missing build-dependencies: it requires pkg.m4 macros, and , leading to errors such as: > ./configure: line 5844: syntax error near unexpected token `SDL,' > ./configure: line 5844: `PKG_CHECK_MODULES(SDL, sdl >= $min_sdl_version,' or after installing pkgconf: > checking for sdl >= 1.1.5... yes > checking for GL/gl.h... no > configure: error: *** OpenGL not found *** I'm going to work around this by adding dependencies to libsdl1.2-compat-dev, but please add explicit build-dependencies on any packages that antigrav explicitly checks for. Thanks, smcv
Bug#1038017: adplay: Depends on SDL 1.2
On Thu, 15 Jun 2023 at 12:29:14 +0100, Simon McVittie wrote: > 4. Install libsdl1.2-compat-dev and recompile the package. I tried this on a porterbox and it seems to build fine, other than the missing build-dependency on pkgconf that I reported as #1039074 (which I intend to work around by making libsdl1.2-compat-dev depend on pkgconf). I didn't test the resulting binaries. smcv
Bug#1038016: adlibtracker2: Depends on SDL 1.2
On Thu, 15 Jun 2023 at 12:28:56 +0100, Simon McVittie wrote: > 4. Install libsdl1.2-compat-dev and recompile the package. I tried this on a porterbox and it seems to build fine. I didn't test the resulting binaries. smcv
Bug#1038015: achilles: Depends on SDL 1.2
On Thu, 15 Jun 2023 at 12:28:35 +0100, Simon McVittie wrote: > 4. Install libsdl1.2-compat-dev and recompile the package. I tried this on a porterbox and it seems to build fine, other than the missing build-dependency on libglu1-mesa-dev reported as #1039072 (which I'm going to work around by making libsdl1.2-compat-dev depend on libsdl2-dev). I didn't test the resulting binaries. smcv
Bug#1039074: adplay: FTBFS with libsdl1.2-compat-dev: missing build-dependency on pkgconf
Source: adplay Version: 1.8.1-3 Severity: important Tags: ftbfs trixie sid I tried compiling adplay on a porterbox with libsdl1.2-compat-dev instead of libsdl1.2-dev, in preparation for having a future version of sdl12-compat take over the libsdl1.2-dev name. I found that adplay FTBFS with: > configure.ac:19: error: possibly undefined macro: AC_CHECK_LIB > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > configure.ac:19: error: possibly undefined macro: AC_MSG_ERROR > configure.ac:21: error: possibly undefined macro: AC_MSG_WARN > autoreconf: error: /usr/bin/autoconf failed with exit status: 1 > dh_autoreconf: error: autoreconf -f -i returned exit code 1 This appears to be fixable by installing pkgconf, which this package requires for the pkg.m4 macros. With the old libsdl1.2-dev, pkgconf was pulled in by this dependency chain: libsdl1.2-dev -> libpulse-dev -> libglib2.0-dev -> pkg-config -> pkgconf As a pragmatic workaround for legacy software I'm going to make libsdl1.2-dev depend on pkgconf, but please fix this properly by adding Build-Depends on all the components that this package explicitly uses. Thanks, smcv
Bug#1039072: achilles: Missing build-dependency on libglu1-mesa-dev
Source: achilles Version: 2-12 Severity: important Tags: trixie sid ftbfs achilles includes but does not have the corresponding build-dependency on libglu1-mesa-dev. At the moment it compiles successfully anyway, because libsdl1.2-dev pulls in libglu1-mesa-dev; but it fails to build when libsdl1.2-compat-dev is installed, because libsdl1.2-compat-dev does not have that dependency. I'm going to add a dependency on libsdl2-dev to libsdl1.2-compat-dev as a workaround, but please give achilles explicit build-dependencies on all the libraries that it requires. Thanks, smcv
