Our automated repository checks [1] have detected that the 'youbroketheinternet' 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/youbroketheinternet.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
The errors look like terribly malformed metadata.xml.
Hi, thanks for this QA report. I am busy on other projects but I should manage to clean this up in the next 3 weeks, I have noticed some of these errors myself before your report did. The report does not look like my change in the ebuild headers was recognized as an error. I don't want to sign over my copyright to Gentoo Foundation by default, but your lint via repoman complaints every time. I assume we are free in what goes into the header as long as it conforms? Unmaintained ebuilds: I already started cleaning the overlay up a few weeks ago, it takes time.
I have fixed the first metadata.xml issues in commit e9508e493b372b4d3c8ecb4c98a36fafb7e397d6, I'll continue to fix when I have the time for it. This was not checked in gentoo, but the syntax is correct.
Looks like this commit fixed it: https://qa-reports.gentoo.org/output/repos/youbroketheinternet.html reports no warnings.
If there are no failures I missed, I will mark this resolved & fixed after your feedback.
The bug seems to be fixed in the repository. Closing.
