knot package with the systemd flag installs /lib/systemd/system/knot instead of /lib/systemd/system/knot.service. The content is right, the file name is wrong. As a consequence, knot won't start at system bootup. This has caused by DNSSEC signatures to expire without me noticing, and my zones became unusable for hours. Earlier versions of systemd were more tolerant and could use file names without ".service" as a workaround. Reproducible: Always Steps to Reproduce: # systemctl status knot Actual Results: Unit knot.service could not be found. Expected Results: The status of the knot program. All ebuilds of knot seem to have the same problem. Classifying as Major because knot won't start after a systemd upgrade because a bug in knot filename (the bug is not in systemd).
I confirm the bug and was able to reproduce it. I introduce it in the following commit: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=91cdae70f2fa6322ff9b38336b24312bdd3c3810 A patch is on the way.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4803ed1237ca22cda7fcb55b7d517d6cf3e5df02 commit 4803ed1237ca22cda7fcb55b7d517d6cf3e5df02 Author: Pierre-Olivier Mercier <nemunaire@nemunai.re> AuthorDate: 2017-11-14 19:47:24 +0000 Commit: David Seifert <soap@gentoo.org> CommitDate: 2017-11-17 18:41:47 +0000 net-dns/knot: fix systemd service's filename Closes: https://bugs.gentoo.org/637504 Package-Manager: Portage-2.3.8, Repoman-2.3.3 net-dns/knot/knot-2.6.1-r1.ebuild | 102 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 102 insertions(+)
