* The tmpfiles processor exited with a non-zero exit code ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1-j4-20221117-080008 ------------------------------------------------------------------- The log matches a QA pattern or a pattern requested by a Gentoo developer.
Created attachment 833285 [details] emerge-history.txt
Created attachment 833287 [details] etc.portage.tar.bz2
Created attachment 833289 [details] sys-auth:munge-0.5.15:20221118-045327.log
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fbe8861b0c541ee7fabc1c196d414450906575a6 commit fbe8861b0c541ee7fabc1c196d414450906575a6 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-11-20 04:05:09 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-11-20 04:05:25 +0000 sys-auth/munge: restore tmpfiles Upstream dropped it apart from for CentOS 7, but let's keep it as it's easier than trying to handle in init scripts. Closes: https://bugs.gentoo.org/881781 Signed-off-by: Sam James <sam@gentoo.org> sys-auth/munge/files/munged.tmpfiles.conf | 1 + sys-auth/munge/munge-0.5.15.ebuild | 4 +++- 2 files changed, 4 insertions(+), 1 deletion(-)
