Every time acct-user/root is installed emerge complains about incorrect path being used: >>> Emerging (1 of 1) acct-user/root-0-r1::gentoo >>> Unpacking source... >>> Source unpacked in /dev/shm/portage/acct-user/root-0-r1/work >>> Preparing source in /dev/shm/portage/acct-user/root-0-r1/work ... >>> Source prepared. >>> Configuring source in /dev/shm/portage/acct-user/root-0-r1/work ... >>> Source configured. >>> Compiling source in /dev/shm/portage/acct-user/root-0-r1/work ... >>> Source compiled. >>> Test phase [not enabled]: acct-user/root-0-r1 >>> Install acct-user/root-0-r1 into /dev/shm/portage/acct-user/root-0-r1/image >>> Completed installing acct-user/root-0-r1 into /dev/shm/portage/acct-user/root-0-r1/image * Final size of build directory: 0 KiB * Final size of installed tree: 4 KiB * The ebuild is installing to one or more unexpected paths: * * /root * * Please fix the ebuild to use correct FHS/Gentoo policy paths. >>> Installing (1 of 1) acct-user/root-0-r1::gentoo * checking 2 files for package collisions >>> Merging acct-user/root-0-r1 to / --- /root/ >>> /root/.keep_acct-user_root-0 --- /usr/ --- /usr/lib/ --- /usr/lib/sysusers.d/ >>> /usr/lib/sysusers.d/acct-user-root.conf >>> Safely unmerging already-installed instance... No package files given... Grabbing a set. --- replaced obj /usr/lib/sysusers.d/acct-user-root.conf --- replaced dir /usr/lib/sysusers.d --- replaced dir /usr/lib --- replaced dir /usr --- replaced obj /root/.keep_acct-user_root-0 --- replaced dir /root >>> Regenerating /etc/ld.so.cache... >>> Original instance of package unmerged safely. >>> acct-user/root-0-r1 merged. * Messages for package acct-user/root-0-r1: * Log file: /bound/build-logs/acct-user:root-0-r1:20210602-062543.log * The ebuild is installing to one or more unexpected paths: * * /root * * Please fix the ebuild to use correct FHS/Gentoo policy paths.
I don't see any way to resolve this in the acct-user/root ebuild itself. Possible solutions: 1. Modify acct-user.eclass to not call keepdir /root. 2. Modify 08gentoo-paths to silence the warning. It would probably be a good idea to introduce a QA variable to allow individual ebuilds to silence the QA check as needed. Personally I prefer solution 2.
python-3.12_tinderbox has reproduced this issue with version 0-r2 - Updating summary.
