Our automated repository checks [1] have detected that the 'netcrave' 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/netcrave.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
Hi Michal, I'm working on getting you unblocked on this now.
Hi again Michal, I have attempted to resolve the problem in this commit: https://github.com/cloudkitsch/netcrave/commit/9c47c149bc0f30fb9c719988e09de484099f7309 however I am not familiar yet with the pkgcore / pmaint tooling enough to test it myself yet. My apologies for letting things go for so long. Could you please take a look at the description of the work done in the commit log linked above and confirm that this unblocks you? If it does, please mark this ticket resolved and close it. In the meantime I will come up with a plan for what to do about this repository. I will also take some time to familiarize myself with the pkgcore tooling. Thank you -Paige
The bug seems to be fixed in the repository. Closing.
