Our automated repository checks [1] have detected that the 'ppc64le' 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. 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/ppc64le.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. While at it, please consider fixing global-scope 'use' call warnings (if any). They are not fatal but are considered a serious QA violation. 'use' functions must not ever be called outside of phase functions. 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
While the report is actually pointing to an issue within pkgcore, the root issue is: you are missing profiles/repo_name.
(In reply to Michał Górny from comment #1) > While the report is actually pointing to an issue within pkgcore, the root > issue is: you are missing profiles/repo_name. Your automatic bug-o-matic hit me up twice, you may want to see why. Anyhow thanks it fixed. *** This bug has been marked as a duplicate of bug 587672 ***
(In reply to Anthony Basile from comment #2) > (In reply to Michał Górny from comment #1) > > While the report is actually pointing to an issue within pkgcore, the root > > issue is: you are missing profiles/repo_name. > > Your automatic bug-o-matic hit me up twice, you may want to see why. Anyhow > thanks it fixed. > > *** This bug has been marked as a duplicate of bug 587672 *** It's not automatic ;-). I just fixed it to report appropriate issues, so I confirmed opening the new bug. It can't check this one until the more important one is fixed, so when you fixed that, it would be able to confirm this one and close it ;-P.
(In reply to Michał Górny from comment #3) > (In reply to Anthony Basile from comment #2) > > (In reply to Michał Górny from comment #1) > > > While the report is actually pointing to an issue within pkgcore, the root > > > issue is: you are missing profiles/repo_name. > > > > Your automatic bug-o-matic hit me up twice, you may want to see why. Anyhow > > thanks it fixed. > > > > *** This bug has been marked as a duplicate of bug 587672 *** > > It's not automatic ;-). I just fixed it to report appropriate issues, so I > confirmed opening the new bug. It can't check this one until the more > important one is fixed, so when you fixed that, it would be able to confirm > this one and close it ;-P. okay. it wasn't clear what was going on.
