Bug#796611: marked as done (ferm: Has init script in runlevel S but no matching service file)
Your message dated Sat, 23 Apr 2016 06:05:00 + with message-id and subject line Bug#796611: fixed in ferm 2.2-5 has caused the Debian Bug report #796611, regarding ferm: 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.) -- 796611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ferm Severity: important User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: init-rcs-service Hi, Your package ferm 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/.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: ferm Source-Version: 2.2-5 We believe that the bug you reported is fixed in the latest version of ferm, 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. Alexander Wirt (supplier of updated ferm 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: SHA1 Format: 1.8 Date: Sat, 23 Apr 2016 07:54:53 +0200 Source: ferm Binary: ferm Architecture: source all Version: 2.2-5 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt Changed-By: Alexander Wirt Description: ferm - maintain and setup complicated firewall rules Closes: 796611 Changes: ferm (2.2-5) unstable; urgency=medium . * Reimport changes from 2.2-3.2 Closes: #796611 Checksums-Sha1: 500d9f90756e647173a20699f7c86bbe55e69847 1756 ferm_2.2-5.dsc 4de9c73cacc7c9a28e170f7284ed7a3fbb2db0de 15853 ferm_2.2-5.diff.gz 218ba493e840306ca1f9a1c1a72b6168df032681 105202 ferm_2.2-5_all.deb Checksums-Sha256: 29b68eb167e64844075dfc6ce65af93d202137e5dd4c5fa98f2b54edc9744b31 1756 ferm_2.2-5.dsc e69512a5cf049f4cbdacd7155d4958ac59c4864315ea15f09c483f75aa3646fc 15853 ferm_2.2-5.diff.gz 429790acb8b693e7689b121070a9e81f5a234def3780eb916e1092d21cf132da 105202 ferm_2.2-5_all.deb Files: edad9a20de6b4b14afb44f6b69d3894d 1756 net optional ferm_2.2-5.dsc fb8371b991ce7dcb176a6910b6d4b5a2 15853 net optional ferm_2.2-5.diff.gz 38e0e4143a76e1e86a51bac070b60987 105202 net optional ferm_2.2-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJXGw7kAAoJEB5F+Mqd4jsWeWwP/icapL/ZxCX5xR1c6mZ/TGVl k43Lx6Nv9XMZrHkt5PwDK8XyNST7U9ixRAw43jb5WfVkFwuLZ5emzCM6qnvKWdiJ LAun3VIZ4v8LmhAAFrUcUShlGq+IjAss4w3toK5K2ALGbpd29Rbk+LN3k73Fe9CP A7Mllrb7stcvnnQSObxfqhcOLUG6AyPs3RqUfT4yP7LUfppLxX6eFySTWWecajIQ Usj4jCbwH9gqcauAN3KqmlpQYFJKyctkU+vJJoG1m+NUMU4vrjT1+bzULf6W8oxn zRGigP6WarVWr08aszrhHxQN5d39mifABKkCy+0+F3onisMZBM/ub4h9cb2Rq/GW FYSHWAEkSIplpkUXJZDXQidOHP4DttXJjoGqRNNT/2s09gz6uTL9h+vbz2/
Bug#796611: marked as done (ferm: Has init script in runlevel S but no matching service file)
Your message dated Tue, 29 Mar 2016 00:05:05 + with message-id and subject line Bug#796611: fixed in ferm 2.2-3.1 has caused the Debian Bug report #796611, regarding ferm: 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.) -- 796611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ferm Severity: important User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: init-rcs-service Hi, Your package ferm 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/.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: ferm Source-Version: 2.2-3.1 We believe that the bug you reported is fixed in the latest version of ferm, 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. Felipe Sateler (supplier of updated ferm 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: Mon, 28 Mar 2016 20:36:07 -0300 Source: ferm Binary: ferm Architecture: source all Version: 2.2-3.1 Distribution: unstable Urgency: medium Maintainer: Alexander Wirt Changed-By: Felipe Sateler Description: ferm - maintain and setup complicated firewall rules Closes: 796611 Changes: ferm (2.2-3.1) unstable; urgency=medium . * Non-maintainer upload. * Add native systemd unit, to break ordering cycle. (Closes: #796611) Checksums-Sha1: 0681ec1ea70549f3410fea7715520825274f9a25 1766 ferm_2.2-3.1.dsc e7f8980554da57fc7cef004d2bbc617997717e9b 15661 ferm_2.2-3.1.diff.gz e3ad99093260231cdbdb47e9d5c5aebb4e7aa1b7 104876 ferm_2.2-3.1_all.deb Checksums-Sha256: 8cb8b26419247e4a3c553fdb937c03869e3878036446acb23aaf7ea3a85bc9fa 1766 ferm_2.2-3.1.dsc 7dce288edb21a982af478fc4ca5b549f0d0f7ec87bbce21361e6f42a536d 15661 ferm_2.2-3.1.diff.gz 15274887be4f32698b7bfa7db46fa5be4cad24467fb49061ca7c9fc871ba0249 104876 ferm_2.2-3.1_all.deb Files: 4e159254eab3c435c1b1de7d7ca6d7db 1766 net optional ferm_2.2-3.1.dsc b7e44e146d74b0a3b14c3804a7f3b30f 15661 net optional ferm_2.2-3.1.diff.gz 278956114ddf858fbcdf3bf4fb2bfa9f 104876 net optional ferm_2.2-3.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJW+cRIAAoJEKO6uuJAjdbP09QP/1sUYR76WXXskEFSF09SHJZW T12sMBXxwaidoLDoD5zk3L9IGDAXUMj+Kfo3KIdQPo0rgwMunwjamXZUP0cBhoZN BkFYml0kZR8oChhTnNDiQo7cqldZQu7GBzOO5wE5kqE3XB7vVWVD2owxtw6ybOE0 MCBqmMzg912YzfC7dqU0w50D+H8B9h4G1gth51ENfU8D5/xgKW5cMm3qukOu7jbO 4EZgkN48Przydw/tkaYPfrdCM+PhL7if9ZpahLjKqjZs8OYZ15aoXHBB2nDymDkA mfWmwJ8hn5vOTaWtYDuSHhLqvnnsjRe+GbUawRasrlrLkH0Jwtd
