vim-plugin.eclass relies on PORTAGE_GRPNAME / PORTAGE_USERNAME being the default of "portage" / "portage". Excerpt: $ grep 'find.*portage' vim-plugin.eclass find "${S}" -user 'portage' -exec chown root '{}' \; || die "chown failed" find "${S}" -group 'portage' -exec chgrp wheel '{}' \; || die "chgrp failed" find "${S}" -group 'portage' -exec chgrp root '{}' \; || die "chgrp failed" Reproducible: Always
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bb7f724185f344a656bbaf1df19f00f8265ea76d commit bb7f724185f344a656bbaf1df19f00f8265ea76d Author: Patrice Clement <monsieurp@gentoo.org> AuthorDate: 2017-11-05 21:16:43 +0000 Commit: Patrice Clement <monsieurp@gentoo.org> CommitDate: 2017-11-05 21:17:32 +0000 vim-plugin.eclass: simplify permission setting logic. We don't use Portage internal variables. Instead, we do away with that chunk of code and invoke fperms recursively on the directory with the right permission flags. Closes: https://bugs.gentoo.org/469400 eclass/vim-plugin.eclass | 17 ++--------------- 1 file changed, 2 insertions(+), 15 deletions(-)