Our automated repository checks [1] have detected that the 'arrans- overlay' 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/arrans-overlay.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
I have fixed the issue. I haven't yet put something to prevent it form happening in the future. What's the process?
Fix in commit ~15 minutes for it to be mirrored: https://github.com/arran4/arrans_overlay/commit/f18213d84f3f1d5cb507148e0019243d10cfd6a9 I will figure out a way of prevent these getting though.
(In reply to Arran Ubels from comment #1) > I have fixed the issue. I haven't yet put something to prevent it form > happening in the future. What's the process? We run these QA checks against overlays periodically, and if an issue is found we file these bugs. The bugs are to help inform the overlay owners and track the status, and it's only really a problem if issues aren't resolved. Don't worry about the bugs being filed, it did the job and notified you and I'm happy that you responded so quick :-) The best tooling for committing ebuilds I can recommend is pkgcheck/pkgdev as they will run the same checks for you locally.
Will it close itself or should I? Is there any process documentation?
It'll get closed the next time I run the QA checks, but you're welcome to close it when fixed. There's some documentation here: https://wiki.gentoo.org/wiki/Project:Repository_mirror_and_CI
