Our automated repository checks [1] have detected that the 'bubba' 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/bubba.html In particular, please look for highlighted error messages. 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
ping
Yeah... Holiday time is not exactly the best time ever to push an eclass update that enforces a higher EAPI than required by system.
(In reply to Gordon Bos from comment #2) > Yeah... Holiday time is not exactly the best time ever to push an eclass > update that enforces a higher EAPI than required by system. Thanks for getting back. I had a similar thought when it was pushed, but don't worry about them. If you intend to push a fix, I'll just leave the bug open until that time.
I'm on it. It's not a big deal, just some minor linguistics. Unable to push atm though because the machine I have access to does not have the github token.
resolved...
(In reply to Gordon Bos from comment #5) > resolved... Awesome, thanks! I'll let the scripts close this.
The bug seems to be fixed in the repository. Closing.
