Your message dated Mon, 09 Jan 2017 04:50:24 +0000 with message-id <e1cqrua-00070v...@fasolo.debian.org> and subject line Bug#796617: fixed in fsprotect 1.0.7 has caused the Debian Bug report #796617, regarding fsprotect: 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 ow...@bugs.debian.org immediately.) -- 796617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: fsprotect Severity: important User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: init-rcs-service Hi, Your package fsprotect 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 pkg-systemd-maintain...@lists.alioth.debian.org -- [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: fsprotect Source-Version: 1.0.7 We believe that the bug you reported is fixed in the latest version of fsprotect, 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 796...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefanos Harhalakis <v...@v13.gr> (supplier of updated fsprotect 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: SHA256 Format: 1.8 Date: Sun, 01 Jan 2017 22:14:30 +0000 Source: fsprotect Binary: fsprotect Architecture: source Version: 1.0.7 Distribution: unstable Urgency: medium Maintainer: Stefanos Harhalakis <v...@v13.gr> Changed-By: Stefanos Harhalakis <v...@v13.gr> Description: fsprotect - Helper scripts to make filesystems immutable Closes: 796617 819992 Changes: fsprotect (1.0.7) unstable; urgency=medium . * Depend on aufs-dkms now that it's back in Debian (Closes: #819992) * Privide a systemd service file (Closes: #796617) * Fix for systemd: Mark / as a private mount momentarily in order to move partitions under it * Fix debian/rules to use binary-install instead of binary * Suffix DEBIAN_DH_ vars with package name in debian/rules * Add Vcs-Git * Depend on lsb-base * Bump compatibility level to 10 * Bump standards version to 3.9.8 * Ignore init.d-script-does-not-implement-optional-option since status makes little sense for the init script, plus systemd provides this already Checksums-Sha1: 1dcf7bd920e37e78a5d816c6efc918fbd4294b77 1488 fsprotect_1.0.7.dsc 3a1e38dc8dac828a19f5994415bcab09e0cca4d3 131844 fsprotect_1.0.7.tar.xz Checksums-Sha256: 3da6d04811bae1029a7e54572a60ce1904d2f84aa9ec541fb3afb26cdf6d3e60 1488 fsprotect_1.0.7.dsc 175b6c11cebf437d056bd11f76b812afb3cb591f4acf8362ccd9f89ff625f625 131844 fsprotect_1.0.7.tar.xz Files: ed056726ce730fe0044ab90222932265 1488 admin extra fsprotect_1.0.7.dsc 7578002b0a05b363862fc88abee550ae 131844 admin extra fsprotect_1.0.7.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAlhzEfcACgkQMRa6Xp/6 aaP4Pg//a4b3Fh5O3PIenT6Os3rX7jDk+I4wVFXJAwSftxQN5DXXIVGrijng4bMo s/HV27RRwwTVxG+Gq2u+xaLduKiEyhQqeVE7GR5kDWdlToUVcv0z1yumVeRBqDgQ Jp/KPDqS01uFlpAuUlDmpCw20TaqY3bT3pK+vBLkUtFggpT4T50hXs1AXfWzCukX ADOS5TTw5fb6T2XE8qch5YtZkZuktVi2zkkbCrgBMj+jL054D6trQ78KdJFUU43E CNQXwHDxXrIMbNulVlg33/lIOZ5nfEsArW6EVRkl6p/34UiiHr/AKLfB6+LfrYQo v+shfV/gLzFEG6fpvrrK3G9rsYVOC+S5GDAi2VFunCGui2GfDJGEjvfiH9wKJ60y WSzhano4jwH3xYb3XrHtpssVak0jC8mtSn6vdE6aEjdJDlZh43qgih/eRYMVulC9 SgTD/u38D4cOZTnjB/XcZU22hMrN1Bws7JG/efLKX1mdl97JTVQCIUenzpJqkVfV FGdG2ajbtLXEwpJzO/5vkyOg5RsrW85IpNzEb1S5XekwRweUK0l16SRIwOunoarO CKGOwQi8eCDpqP1uf6VNIv9EDxL3E25554HrCB21eGkVHw812HkyFZEsWrKduUJW H0oQDf9Mzev6HIfnexU9z0Ig/nhQHw3cdwJDuNGZtt+l126GBWA= =Ia7b -----END PGP SIGNATURE-----
--- End Message ---
