Your message dated Sat, 25 Jun 2016 18:26:31 +0000
with message-id <[email protected]>
and subject line Bug#796705: fixed in zfs-fuse 0.7.0-13.1
has caused the Debian Bug report #796705,
regarding zfs-fuse: 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.)
--
796705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796705
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: zfs-fuse
Severity: important
User: [email protected]
Usertags: init-rcs-service
Hi,
Your package zfs-fuse 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: zfs-fuse
Source-Version: 0.7.0-13.1
We believe that the bug you reported is fixed in the latest version of
zfs-fuse, 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 zfs-fuse 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:42:09 +0200
Source: zfs-fuse
Binary: zfs-fuse
Architecture: source amd64
Version: 0.7.0-13.1
Distribution: unstable
Urgency: medium
Maintainer: Asias He <[email protected]>
Changed-By: Andreas Henriksson <[email protected]>
Description:
zfs-fuse - ZFS on FUSE
Closes: 796705
Changes:
zfs-fuse (0.7.0-13.1) unstable; urgency=medium
.
* Non-maintainer upload with maintainer approval.
* Add debian/zfs-fuse.service (Closes: #796705)
- this is a simple wrapper around the init script with room for
improvement. Mostly copied from the by systemd-sysv-generator
autogenerated unit with minor modifications. Future work would be
to split out the program parts of the init script
(upgrade_zpool_cache_location(), et.al.), run that from
ExecStartPre= and turn the rest into a real native unit file
supporting monitoring/restarting of the daemon, etc.
* Add dh-systemd build-dependency and --with systemd to debian/rules.
- to activate helpers that takes care of the above unit file.
* debian/rules: install zfs-fuse bash completion into new directory
under /usr/share instead of deprecated /etc/bash_completion.d.
* Use dpkg-maintscript-helper to rm_conffile in preinst, postinst
and postrm to properly clean up /etc/bash_completion.d/zfs-fuse
Checksums-Sha1:
4ca9640a0e8549701e0e0bccab8c4c15d1d3e0f5 1978 zfs-fuse_0.7.0-13.1.dsc
7dfc63b2bf93b54778dbc6888e48e69ac435f0af 25616
zfs-fuse_0.7.0-13.1.debian.tar.xz
a94b454fa456f66059e0f470d327d74870f5ae9c 3309882
zfs-fuse-dbgsym_0.7.0-13.1_amd64.deb
ce3c18bdda7896dfcfb17ccd3438b3cd9a95a8a2 712884 zfs-fuse_0.7.0-13.1_amd64.deb
Checksums-Sha256:
1b79a8e43185c2d6810db83ff7058070c0d90d95fd47f34b2c44450476ba7d2a 1978
zfs-fuse_0.7.0-13.1.dsc
f3ee8a3c7622e7e006fffec76b9389a8618068f16c4c7162fef8ab337b74f3d8 25616
zfs-fuse_0.7.0-13.1.debian.tar.xz
0425e63bb67f5f143fdf0be5a82a30c327721130209e584dce1b741912d7dc87 3309882
zfs-fuse-dbgsym_0.7.0-13.1_amd64.deb
8f7d91273e477c31a517bfc97aca5250327de5061130a2675845213cf712197b 712884
zfs-fuse_0.7.0-13.1_amd64.deb
Files:
5326d482b8efbfd6e64c32ce2f41fa9a 1978 otherosfs optional
zfs-fuse_0.7.0-13.1.dsc
aa25c72cb8c64d5deecb8af6c55f4294 25616 otherosfs optional
zfs-fuse_0.7.0-13.1.debian.tar.xz
1632668a1179fed86f006838e93f11e9 3309882 debug extra
zfs-fuse-dbgsym_0.7.0-13.1_amd64.deb
78d71831f83ccc2a5d47f94c522ff524 712884 otherosfs optional
zfs-fuse_0.7.0-13.1_amd64.deb
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJXbsf1AAoJEAvEfcZNE1MGNgUP/3IdQ2CUYV4eR+w4tGvud/wu
+z4S5iPP5cmNspHbafsWqJvLjtDWHVQlNHQ1rQ/jehLmEbepdxuJNC7KKrU/TszN
aEFBG/+E1JrsGpL60Jfv/9fbFEDqiVzB5aAX0kmFHFQ+CxN0/pTRal5TCJVdufIU
Lk4S7HNnSkM/iN/dZDB8kt0YH+04KmwjJifmq4gyM1C9SLq8D4Xa2HiMD/HRrPIA
vO218e63r43LnvxLHcGnnEhvU8GGiigKZqd+BYS5vAG2BMOfZSQTFq/+GKcgNkE0
tBsoIlVF8p9Fdf/wdxK0tl+dzQ4JahRH5hyEtoKk5UvbeVsMGi0eCFyL0xJpvvLP
QnCBwixgE2WNbsE0DonaWYay0lDxV/z9J7lxn6gknATRBtQP3O9gVWOqytQ01dhu
PTmMMLpxBE86z0XjNAPYJ3sEYtunDBtRgEwB8qrF+prGmnYerV+3EhdpeExLqZvc
MySFI0oI1Hxa/XOw2UEBoF6Nn8Q+o2EVvaW/h3MZY3g0xIEtyLeMmAHozAG3hbSX
CBiX74bYNYc367YHxUc0vKuGr757RjsdjezgH2VonOvuJfbMO20+AuxRbYra6YYN
zetSUrxBSv/YuMkAP9KaWZhmOUKakUOaXIpZC/+KnSTooytmshW2FQ4bk02r09H0
7KZcR5zAmpwjbzNagHtj
=o33Q
-----END PGP SIGNATURE-----
--- End Message ---
