Stable 1.5.14 produces the warning /lib/systemd/system/cron-failure@.service:11: Special user nobody configured, this is not safe! every time a mail-on-failure service is run. Moreover, I have seen systemd-crontab-generator occasionally report global exception: [Errno 2] No such file or directory: '/run/systemd/generator/cron-crontab-/bin/rm-0.sh' and subsequently exit with code 1. In contrast, 1.5.17 uses dynamic users in cron-failure@.service instead and I have yet to seen the aforementioned generator error.
I'd also really encourage stabilisation more often. The last time was a year ago. ~arch is for testing already-suitable software for a little while before it officially is marked stable, not for things to soak forever ;)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fbbaed3076ee73c8c5d644e0582480d2de03c5e1 commit fbbaed3076ee73c8c5d644e0582480d2de03c5e1 Author: Richard Freeman <rich0@gentoo.org> AuthorDate: 2021-05-10 18:58:03 +0000 Commit: Richard Freeman <rich0@gentoo.org> CommitDate: 2021-05-10 18:58:03 +0000 sys-process/systemd-cron: amd64 stable Bug: https://bugs.gentoo.org/788601 Package-Manager: Portage-3.0.18, Repoman-3.0.2 Signed-off-by: Richard Freeman <rich0@gentoo.org> sys-process/systemd-cron/systemd-cron-1.5.17.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
x86 stable
sparc done all arches done
