Our automated repository checks [1] have detected that the 'ssnb' repository contains ebuilds that trigger fatal errors during the cache regeneration. This usually means that the ebuilds call 'die' in global scope indicating serious issues or have other serious QA violations. Global-scope failures prevent the ebuild not only from being installed but also from being properly processed by the Package Manager. Since metadata can not be obtained for those ebuilds, no cache entries are created for them and the Package Manager needs to retry running them every time it stumbles upon them. This involves both a serious slowdown and repeating error output while performing dependency resolution. The most common cause of global-scope failures is use of removed or banned APIs in old ebuilds. In particular, this includes eclasses being removed or removing support for old EAPIs. Nonetheless there are also other issues such as performing illegal operations in global scope (external program calls), malformed bash in ebuilds or malformed metadata.xml. The error log for the repository can be found at: https://qa-reports.gentoo.org/output/repos/ssnb.html In particular, please look for highlighted '!!! ERROR' and '!!! caught exception' lines. The former usually mean failures coming from eclasses and the ebuild itself, while exceptions usually mean malformed ebuilds or metadata.xml. Please note that due to technical limitations of pkgcore, the processing stops on the first error found. Once solved, please wait ~30 minutes for the report to refresh in case new errors may appear. Please fix the issue ASAP, possibly via removing unmaintained, old ebuilds. We reserve the right to remove the repository from our list if we do not receive any reply within 4 weeks. [1]:https://wiki.gentoo.org/wiki/Project:Repository_mirror_and_CI
With eix-update the mentioned errors don't appear. Is there any reference in documentation for QA procedure? The errors seems strange * ERROR: www-apps/gitlabhq-8.16.6 failed (depend phase): * External commands disallowed during metadata regen: getent passwd git * * ERROR: www-apps/gitlabhq-8.16.6 failed (depend phase): * External commands disallowed during metadata regen: cut -d: -f6 Is there any information for the EAPI related to "External commands disallowed during metadata regen"? I never saw that error before.
(In reply to Samuel Bernardo from comment #1) > With eix-update the mentioned errors don't appear. > > Is there any reference in documentation for QA procedure? You can use the Portage patch now on gentoo-portage-dev ml. We're not pushing it yet to give people some time to prepare before everything explodes in their faces. > The errors seems strange > > * ERROR: www-apps/gitlabhq-8.16.6 failed (depend phase): > * External commands disallowed during metadata regen: getent passwd git > * > * ERROR: www-apps/gitlabhq-8.16.6 failed (depend phase): > * External commands disallowed during metadata regen: cut -d: -f6 > > Is there any information for the EAPI related to "External commands > disallowed during metadata regen"? https://dev.gentoo.org/~ulm/pms/head/pms.html#x1-12400011.3 The second sentence. We're starting to take steps to enforce it. Long story short, you have to make do with pure bash in global scope and not access any system state. Whatever you do there, it belongs in a phase function, if at all.
Since there is another overlay maintaining the gitlabhq ebuild, I just removed the outdated version I was sharing in my overlay. Thanks Michał Górny for your explanation about the new portage roadmap!