Your message dated Sat, 25 Jun 2016 18:04:05 +0000
with message-id <[email protected]>
and subject line Bug#796687: fixed in scsitools 0.12-2.3
has caused the Debian Bug report #796687,
regarding scsitools: 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.)
--
796687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796687
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: scsitools
Severity: important
User: [email protected]
Usertags: init-rcs-service
Hi,
Your package scsitools 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: scsitools
Source-Version: 0.12-2.3
We believe that the bug you reported is fixed in the latest version of
scsitools, 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.
Andreas Henriksson <[email protected]> (supplier of updated scsitools 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: SHA512
Format: 1.8
Date: Sat, 25 Jun 2016 19:13:32 +0200
Source: scsitools
Binary: scsitools
Architecture: source amd64
Version: 0.12-2.3
Distribution: unstable
Urgency: medium
Maintainer: Eric Delaunay <[email protected]>
Changed-By: Andreas Henriksson <[email protected]>
Description:
scsitools - Collection of tools for SCSI hardware management
Closes: 686881 796687
Changes:
scsitools (0.12-2.3) unstable; urgency=medium
.
* Non-maintainer upload.
.
[ Andreas Henriksson ]
* Add debian/scsitools.links to create symlinks masking the
scsitools.sh and scsitools-pre.sh init scripts under systemd.
- these scripts are likely not useful at all on modern systems.
(Closes: #796687)
* Add dh_link command to debian/rules for the above.
* Demote tk to a Suggests instead of Recommends to avoid pulling in
X11 when installing these otherwise low-level tools.
- the tools should already handle and give useful help/output
when run and tk/wish is missing.
* Drop util-linux versioned dependency as the version are already
new enough since ages and util-linux is Essential: yes anyway.
* Source /lib/lsb/init-functions in init scripts to allow
LSB hooks to work correctly.
* Add lsb-base dependency for the above.
.
[ Daniel Kahn Gillmor ]
* Make postinst less brittle by accepting failure to create /dev/scsi/
(Closes: #686881)
- Note that this attempt to create /dev/scsi isn't going to persist on
modern systems with a tmpfs mounted on /dev, so whatever is relying on
that directory being there is going to need some other way to deal after
a reboot anyway.
Checksums-Sha1:
93c7bdf1d4c3e892b540766403c44d4207cda9d7 1672 scsitools_0.12-2.3.dsc
165b75629f0e154a50d196afb66fca1e6318d80b 29752 scsitools_0.12-2.3.debian.tar.xz
bd4e88129d76ddd3f7c4e6c2e90d5b0af9fd493b 89008
scsitools-dbgsym_0.12-2.3_amd64.deb
7f612cfb4aa6f90fffca93ae3f09834ab4f6be50 116902 scsitools_0.12-2.3_amd64.deb
Checksums-Sha256:
a1189f1c690ee06ea94f6a6b15c670c65d34377c3f5a6e5f6347893422ecce38 1672
scsitools_0.12-2.3.dsc
0d35fdd780145e182d2646268bdedeb818c02cc3d83c81a605e73d33e551e5fa 29752
scsitools_0.12-2.3.debian.tar.xz
42a14277350859c8792098d901aecdd736b0be4c0292b04b1e63fda3fccd8dac 89008
scsitools-dbgsym_0.12-2.3_amd64.deb
8c0cc1274634f1e2e128531a84fe8ab7d42336c4a7a136237ead92fe03e81c19 116902
scsitools_0.12-2.3_amd64.deb
Files:
ddbc7e80c4236108fea74675a3503860 1672 utils optional scsitools_0.12-2.3.dsc
09fdb6b32267e9ff74dcd997f1d3b0ee 29752 utils optional
scsitools_0.12-2.3.debian.tar.xz
8fc9229addce19f6069a68d16ce1f64d 89008 debug extra
scsitools-dbgsym_0.12-2.3_amd64.deb
fbbd859db436fce2f11fd431dc260a27 116902 utils optional
scsitools_0.12-2.3_amd64.deb
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJXbsCQAAoJEAvEfcZNE1MGF6kQAIVMEr51Kh4ZSEDJCT31bYLR
xPnvfLAk+uRu8PlwXH1K0RCBNLt2Ny1OM7MIaK4+qqtKSBQWr0KpXm1DQv8zTkKJ
ws2kcOrcVm3U5l/IFH63aWYzoE7jyLgsog90jMZ8NSZ6ka6e1Fme0RDBsbej0UaF
c+N3PA/BgZvcf1Z8f0eH96ae55hS6FyW1sBhyQlWgsOKVfXX3xL7R4cjxu5vEt6+
VfSLDPWNJ1Aewt+99+lPYfdFTknXtcAcfnmOK95ZtlFcHqhBLdcp6YXZOcUQcobp
5PkrrScCBZhYxWVac4Bote7YigynEWXx/X18D+o2l1L0k/7+P41BhFZ5qMewFpEn
ZBj/p/QNvxqo7xwcw26LjYN+/+k0zpIA+H99Pmktp0kMcHTLZ28B8lD8/En5VygL
bjZLFY/E90/KA5xbwxP8hbxhnd9WcqStItRUijiLINnnyjpFE1paKlUVIXNJp5A3
WitykmppXikFWjdXXg9ntjOIXBs6wy/dwI/nckg1kZfS/kCZ2lI/UZ3NdOriedMW
6JsuMM+wiNttM9FELApyxa9niVJ7dscZpOroa3hi5k3/FyNYByWLyYy8Yd2qy7hO
TSpfF7AtPUY0/LtrLyIOca4uCuOa5bSI8cO0zWNW+BafdfFq+jc+6KB7gtEbiFaw
iLy6ejrxn9OJGDauGeio
=mAYN
-----END PGP SIGNATURE-----
--- End Message ---