[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1039128: marked as done (aprx: ships sysv-init script without systemd unit)

Your message dated Thu, 13 Jun 2024 09:49:08 +0000
with message-id <E1sHh4u-00E9jo-0v@fasolo.debian.org>
and subject line Bug#950952: fixed in aprx 2.9.1-2
has caused the Debian Bug report #950952,
regarding aprx: 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 owner@bugs.debian.org
immediately.)


-- 
950952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950952
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: aprx
Severity: important
User: bluca@debian.org
Usertags: missing-systemd-service

Dear Maintainer(s),

aprx 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/aprx

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: aprx
Source-Version: 2.9.1-2
Done: Christoph Berg <myon@debian.org>

We believe that the bug you reported is fixed in the latest version of
aprx, 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 950952@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Berg <myon@debian.org> (supplier of updated aprx 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 13 Jun 2024 11:03:51 +0200
Source: aprx
Architecture: source
Version: 2.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org>
Changed-By: Christoph Berg <myon@debian.org>
Closes: 950952
Changes:
 aprx (2.9.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Install aprx.service, thanks Andreas Henriksson. (Closes: #950952)
   * Drop lsb-base dependency.
Checksums-Sha1:
 a77bcbd6a70a33011654c24a7a3c4777f9e3834b 1922 aprx_2.9.1-2.dsc
 7d9e80d35c54f828fbc6d08b69ec872327bc6929 8888 aprx_2.9.1-2.debian.tar.xz
Checksums-Sha256:
 cfc5db6d7c129c0017349eb5fb9038d099d0282d5399b2005b29fc45fb7f5469 1922 aprx_2.9.1-2.dsc
 5184e3a34c1f4c6dae9be6193122ed688a599c498da69942ae94378bd07db195 8888 aprx_2.9.1-2.debian.tar.xz
Files:
 423a989b1e3203ddcdd1b231e590dd8c 1922 hamradio optional aprx_2.9.1-2.dsc
 c92503c3de5a6ece42cfe038d11ffca8 8888 hamradio optional aprx_2.9.1-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmZqwAoACgkQTFprqxLS
p67I+RAArWPfpHud2VRCy/6+8ruqRd33J1BQgV+otAviB5WFI0vip3+g87YCGd71
UPgN1iOQOjFr8Z+fV03XsAdgoPDf/ndZVxHiOn/cUBN4NdNIEd5NdCHHRXhMLUXI
PhNmB7G58HRqm6fOjSdEUcsT0DHd1x/6fuXUE6948UsF+ghRWnOV/MfxFs1RrrVp
zll6ARXnDmPNu954SAYy8m35Pc80AItjKzStPAIcVXqwZCChmCFqK8tIQEdhnIUq
3tNWaQ/UHRPN43JcbIopiqvFoDqynIC0rvLv748Mx7uTfY0FTGZel4wGCB2dVr53
jc1W/tptTv4Mtv6XQJ4iZws75U2/eTIF1bhZ7hXlHkKIiOjLCC/8+mo5N9pp+XMW
AfrnYgLSOgLk3z4vRuiHaZonuzDsQMCuIOdvH3jgju0Pl76xsgEXIH1a68Oa/XV/
aDYnsfbNyCiuL5aCV6hwAFIqXAwfMJb4ogmxpKfPlncnN+BADC8qNXxgrZWl6y1z
xUhf2unfHsoOtXpCXfcs1Z8SymtLmy2WefXryzpBExr+oP9At0bkf+uUHnOdGqOM
e0ZXx1dudPHYTaSINvHZ3IVEzZZFiQMe3ZE8XeY8V3Kcg1eVMNgTj/tSZ8GT6nRa
fc9+BiB4wNkiP5kmHOVOSepScgwEgBZo4mcpFR9pmpm8SRPtUvI=
=dOa2
-----END PGP SIGNATURE-----

Attachment: pgp0lcGzwFwXD.pgp
Description: PGP signature


--- End Message ---
Reply to: