When building prior to bug #740418 fix, e.g. USE=caps I followed final advice: if [[ -n ${REPLACING_VERSIONS} ]] && use caps && ! ${HAD_CAPS}; then ewarn "Please adjust permissions on ${EROOT}/var/{lib,log}/chrony to be owned by ntp:ntp" ewarn "e.g. chown -R ntp:ntp ${EROOT}/var/{lib,log}/chrony" ewarn "This is necessary for chrony to drop privileges" fi -rebuilding USE=-caps didn't reset /var/lib/chrony ownership from net:net to root:root -removing the package didn't help either, likely because out of build contents remained in the directory, e.g.: var/lib/chrony: -rw-r--r-- 1 net net 42 sept. 5 18:42 drift So I removed once again, deleted the dir, i.e.: rm var/lib/chrony -rf Then reinstalled to finally have it set back to root:root, which seems to be to correct value: So as of now, to put things back to order user switching from USE=caps to USE=-caps might have to do: chown -R root:root /var/lib/chrony Reproducible: Always
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=010d17c7b421a0fa06ecd2430913f04ea5f47562 commit 010d17c7b421a0fa06ecd2430913f04ea5f47562 Author: Sam James <sam@gentoo.org> AuthorDate: 2021-02-08 14:14:24 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-02-08 14:54:02 +0000 net-misc/chrony: add notice when switching USE=caps -> USE=-caps Closes: https://bugs.gentoo.org/740550 Package-Manager: Portage-3.0.14, Repoman-3.0.2 Signed-off-by: Sam James <sam@gentoo.org> net-misc/chrony/chrony-4.0-r1.ebuild | 12 ++++++++---- net-misc/chrony/chrony-9999.ebuild | 12 ++++++++---- 2 files changed, 16 insertions(+), 8 deletions(-)