Our automated repository checks [1] have detected that the 'fkmclane' 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/fkmclane.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
Fixed in b03f460
More to go. Please see the previous-to-last paragraph.
That was my mistake; I believe it is fixed in 945e6b1. Also, thanks for running this QA bot!
You're welcome. However, I'm afraid there's more where they come from.
I cannot reproduce this locally with `egencache`. I borrowed those ebuilds from another source and never ended up removing the global `cut` calls. I've replaced both of those with bash substrings. I could be mistaken but it appears your QA bot did not run when pushed 945e6b1. It has since run for 48db5f0 and appears to succeed.
If you want to try to reproduce it locally, you can get the relevant Portage patch from [1] or gentoo-portage-dev mailing list. Or [2] if you prefer pkgcore. [1]:https://github.com/gentoo/portage/pull/199 [2]:https://github.com/pkgcore/pkgcore/pull/240
The bug seems to be fixed in the repository. Closing.
