Your message dated Sun, 10 Jan 2016 21:40:49 +0000
with message-id <[email protected]>
and subject line Bug#796694: fixed in shorewall-init 5.0.3.1-1
has caused the Debian Bug report #796694,
regarding shorewall-init: Has init script in runlevel S but no matching service
file
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.)
--
796694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796694
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: shorewall-init
Severity: important
User: [email protected]
Usertags: init-rcs-service
Hi,
Your package shorewall-init has an initscript that is enabled in
runlevel S, but it does not provide a corresponding systemd service
unit.
Systemd generates units for all sysv init scripts that do not have a
corresponding systemd unit. By default, it sets
DefaultDependencies=yes, which means they get ordered after early
boot has finished.
The problem is that to preserve the runlevel S semantics, systemd in
debian is currently[1] ordering all S services Before=sysinit.target.
This target is particularly early in the boot sequence, which means
that it is most of the time too strict. In turn, this means it is
fairly easy to end up with dependency cycles. For an example, see bug
[763315]. Do note that the cycle still exists with sysvinit, it is
just that systemd complains more loudly.
Please add a systemd unit for the given service with the appropriate
dependencies, which most of the time will be less strict than
Before=sysinit.target. In other cases, the script is simply not
applicable in systemd, in which case the package should ship a
symlink to /dev/null as /lib/systemd/system/<initscript>.service.
We have prepared a transition wiki page[2] explaining the issue in
more detail, and outlining some general guidance. Please refer to it
as it will have useful information.
If you have any other doubts, feel free to ask in
[email protected]
--
[1]
http://sources.debian.net/src/systemd/222-2/debian/patches/Add-support-for-rcS.d-init-scripts-to-the-sysv-gener.patch/
[763315] https://bugs.debian.org/763315
[2] https://wiki.debian.org/Teams/pkg-systemd/rcSMigration
--- End Message ---
--- Begin Message ---
Source: shorewall-init
Source-Version: 5.0.3.1-1
We believe that the bug you reported is fixed in the latest version of
shorewall-init, 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.
Roberto C. Sanchez <[email protected]> (supplier of updated shorewall-init
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, 10 Jan 2016 15:45:33 -0500
Source: shorewall-init
Binary: shorewall-init
Architecture: source all
Version: 5.0.3.1-1
Distribution: unstable
Urgency: low
Maintainer: Roberto C. Sanchez <[email protected]>
Changed-By: Roberto C. Sanchez <[email protected]>
Description:
shorewall-init - Shorewall initialization
Closes: 796694
Changes:
shorewall-init (5.0.3.1-1) unstable; urgency=low
.
* New Upstream Version (Closes: #796694)
Checksums-Sha1:
da100764eef6fc756f7c676abfeeea5e9662b150 1892 shorewall-init_5.0.3.1-1.dsc
96a6270426bfb19a8080122e19d02d28cc7774ce 35236
shorewall-init_5.0.3.1.orig.tar.gz
d5eeeb2b7282547d1dd8ed2d192e567057b71af9 3008
shorewall-init_5.0.3.1-1.debian.tar.xz
b5da1026d48d3acde6a78fe075ca5df191bbcb53 14064 shorewall-init_5.0.3.1-1_all.deb
Checksums-Sha256:
caa9a8235ae269f819d3fd302fa0506c87dc447f9eae730425851c27990c48e0 1892
shorewall-init_5.0.3.1-1.dsc
1326ffe77faa28de87c7e1b66f21324dfd724c546c2e9383afee12c9e8ef8d27 35236
shorewall-init_5.0.3.1.orig.tar.gz
f5c8d428ef6f17748dedb415a5c59b6fc9e3d909ded7cb841ea769d1cddaf047 3008
shorewall-init_5.0.3.1-1.debian.tar.xz
3071eee3c49793b70763b6c32a24452c18eddeb2ef6af2da57d07078f881232e 14064
shorewall-init_5.0.3.1-1_all.deb
Files:
4f9e62e88510e5be08656da7cd70d602 1892 net optional shorewall-init_5.0.3.1-1.dsc
bcd9e1d169ae692d14b926464859c4f0 35236 net optional
shorewall-init_5.0.3.1.orig.tar.gz
c54cfd99d824be7b3fedb6dca5e4a2a3 3008 net optional
shorewall-init_5.0.3.1-1.debian.tar.xz
95f30d6f229e58fe24ac880280e4979a 14064 net optional
shorewall-init_5.0.3.1-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJWks0iAAoJECzXeF7dp7IPC44P/1U4gucmGlTMr3RW1Bphg/Ay
gY5f7z4tiMswSy0PercaNv4/hG7B0A1Zz0HL+245Iyt9htS1t3IWG8BnAFdPJqfd
3HmSfLZbHHNUdFgaB9DS/ukLiGBdOgkUVzVn8atgdPQYQdkygqQCxPmdagy1WPwK
54O+1FTrLHBJ49JdRvWiaUNeDvK+y5Fitcizhe4OI/+GmRX/PLIBA48oSHEhs6a0
uqQR74lW0xUvLng3dEWIZ8JTnbD/XKV2NhNCH/aJJfq+Hb1euJOasHGzE/xKCG93
Za35lAQRkdXUMhNuTHVVxMmXTo58XlfdjjNs73JxnVIVcqZmnP6mQXLKjAeutCOT
c/ds/UJ8evXLuVyn92EHBrlZjkpr+9D9m8sf/vNGA5nlPLjE1LZFVgZkMXaIpsTb
in8nbQqEBYO0RPPVuDSiS9P0rWScjosSRLbWVKhuxj3r+5s2e5NIh0/soA5gqgz5
r12hscEtxkmmDwPzqsZPptvdfJIFeiIylvHusnP1D1ciGkO1F7oWeD0IyYscDN2p
ElSCcQvCXsIV3uQoS1y2tfYUfRL0KM7CFQWwWTziXMikwJow+irekcY8RXqA/8xP
H6eJk3Jkwwx3138TwELdYPT5ugkprdsfQrQTsAeUWaAmEg+QCy47HZhCcH+R8/Tb
ypN5ibgrJKGxiwtl/A9n
=oM9w
-----END PGP SIGNATURE-----
--- End Message ---
