Your message dated Thu, 21 Nov 2024 15:53:40 +0000
with message-id <e1te9uy-00fvxv...@fasolo.debian.org>
and subject line Bug#1039265: fixed in minicoredumper 2.0.7-4
has caused the Debian Bug report #1039265,
regarding minicoredumper: 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 ow...@bugs.debian.org
immediately.)
--
1039265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: minicoredumper
Severity: important
User: bl...@debian.org
Usertags: missing-systemd-service
Dear Maintainer(s),
minicoredumper 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/minicoredumper
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: minicoredumper
Source-Version: 2.0.7-4
Done: John Ogness <john.ogn...@linutronix.de>
We believe that the bug you reported is fixed in the latest version of
minicoredumper, 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 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
John Ogness <john.ogn...@linutronix.de> (supplier of updated minicoredumper
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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 14 Nov 2024 12:52:38 +0100
Source: minicoredumper
Architecture: source
Version: 2.0.7-4
Distribution: unstable
Urgency: medium
Maintainer: John Ogness <john.ogn...@linutronix.de>
Changed-By: John Ogness <john.ogn...@linutronix.de>
Closes: 1039265
Changes:
minicoredumper (2.0.7-4) unstable; urgency=medium
.
* Add systemd init service files (Closes: #1039265)
* Fix use of obsolete pkg-config as build dependency
* Mark man page patch as not-needed upstream
* Specify source package for libminicoredumper2
* Update to standards version 4.7.0
Checksums-Sha1:
d339a3571d3d8e27a4d160a60cf224ca09ce6e9b 2519 minicoredumper_2.0.7-4.dsc
36962d3000eed291a07d5d4f684769ec0f4a48b2 8652
minicoredumper_2.0.7-4.debian.tar.xz
Checksums-Sha256:
187665465a22ba20a2c810bda3e37d534ae2b23acf23a2e1173194eac590a402 2519
minicoredumper_2.0.7-4.dsc
cc3430fbd9a2f5e029eb69bd15097caa1073385a6412bda67c1fe41700dfd388 8652
minicoredumper_2.0.7-4.debian.tar.xz
Files:
45f92d939d9e94d1c6e58f933f80dd89 2519 devel optional minicoredumper_2.0.7-4.dsc
72c2087332a6884f36ffbd7f99d6ebab 8652 devel optional
minicoredumper_2.0.7-4.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEZCVGlf/wqkRmzBnme5boFiqM9dEFAmc/T9oACgkQe5boFiqM
9dGHtw/6A5yaK0lvlJmu7pCfKWGr3RuL/iwB+v1ZcE/iteTox5Tanfyrlg5P5T1E
5OaJFGQNtCmURAU1GD6vGWaFrQTybWPn3/OsRkEO0qACydwhsAZQ+GUth99yQEPX
9YXpKM9TLHEyerkygLsB0MO4GkLBDchDqX6fDFe2WNit/n78WmsK00v8R1X23TYy
XjHesZNbShaQm+BCvjlJct9WgEpIYt3Ii+a3vQOvGPSSS3mMz9wPoJnLzP3zifmZ
ah8wNov2Xd86p3kbIaa+wNlOMt7hwrIspSkVSB0tL7WsSZV1RvAKsQiJxjr0iTUM
/NXMNR6Q9gpwAcGgzIucciJ+6clHNchWUytwZWhxWr70ijv5vH9aG/fSlEeNmmCg
12bi+ZA1HiaAe9QelCYTThxrOVQutekc0ewz1YrfyRLUAozRG2Pf99KFvLWFHsGq
74Awq9+DctZK6dWe+/WR7qNxyi8d8kZQHuMHQQAGznVaMfBt96OcNBNSV9TJruK8
Rptc4/Pmz1HnIZutDfKZnXtuv81QX6HPcfWpJEN2HRudi/+OvajYiX1a+UE7roJA
OUCgYQLXvypmih+3FaO5i+D40ezTmOCsBKJ7Vi9GbzWRdhiEPqzPNmqwyHtrK/m2
7DwIw/SEgOIGVC6veo5bKGi6HR4NZ0a0jZQWP0TNYZ/OYOAWH44=
=jPwV
-----END PGP SIGNATURE-----
pgp6N6WCb1jTy.pgp
Description: PGP signature
--- End Message ---
