current amanda ebuild triggers systemd warnings like: (journalctl -b0 | grep amanda) -> Configuration file /usr/lib64/systemd/system/amanda.socket is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. Configuration file /usr/lib64/systemd/system/amanda@.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. Configuration file /usr/lib64/systemd/system/amanda@.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. We should set the correct permissions at install time.
@robbat : could you help getting this solved?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b740f33032923e18de20051c88669c583af7d6fb commit b740f33032923e18de20051c88669c583af7d6fb Author: Robin H. Johnson <robbat2@gentoo.org> AuthorDate: 2017-11-13 20:35:06 +0000 Commit: Robin H. Johnson <robbat2@gentoo.org> CommitDate: 2017-11-13 20:44:57 +0000 app-backup/amanda: fix systemd perms. Fixes: https://bugs.gentoo.org/530150 Package-Manager: Portage-2.3.8, Repoman-2.3.3 Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> app-backup/amanda/{amanda-3.5.ebuild => amanda-3.5-r1.ebuild} | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
