Our automated repository checks [1] have detected that the 'alxu' 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/alxu.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
* dev-java/openj9-openjdk-11.0.41.0: failed sourcing ebuild: java-vm-2: EAPI 7 not supported, (java-vm-2.eclass, line 15: called die) * dev-java/openj9-openjdk-17.0.41.0: failed sourcing ebuild: java-vm-2: EAPI 7 not supported, (java-vm-2.eclass, line 15: called die) upgraded to eapi 8 https://cgit.alxu.ca/gentoo-overlay.git/commit/dev-java/openj9-openjdk?id=968122b6356dff143231c5aedfc2ca24728c7e12
hello, reopened as autotools.eclass dropped EAPI 6 support
updated to EAPI 8
