Our automated repository checks [1] have detected that the 'AlexandreFournier' 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/AlexandreFournier.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
Last commit should fix most of it. Is it possible to run the QA localy ?
The bug seems to be fixed in the repository. Closing.
(In reply to Alexandre Fournier from comment #1) > Last commit should fix most of it. > > Is it possible to run the QA localy ? Sure, it's just "pmaint regen" (the command is listed in the QA report). I would also recommend getting into "pkgcheck scan". I think in this particular case there was very little time between the EAPIs being dropped, and me running the bug reporting tool (literally scraping the QA reports and filing bugs when errors are found), so there was a short window of time where you'd have caught the sourcing errors yourself before I filed the bug.
Ok cool. I looked at "pmaint regen" and "pkgcheck scan", and it looks promising. Thank you for your feedback.
(In reply to Alexandre Fournier from comment #4) > Ok cool. > > I looked at "pmaint regen" and "pkgcheck scan", and it looks promising. > > Thank you for your feedback. np, happy to help!