Our automated repository checks [1] have detected that the 'lisp' 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/lisp.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. Please note that due to technical limitations of pkgcore, the processing stops on the first error found. Once solved, please wait ~30 minutes for the report to refresh in case new errors may appear. 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
Ping.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/lisp.git/commit/?id=95c7e8ec0ef6b07ebb83ba35d174bb35b647f83c commit 95c7e8ec0ef6b07ebb83ba35d174bb35b647f83c Author: Ulrich Müller <ulm@gentoo.org> AuthorDate: 2019-08-08 21:23:10 +0000 Commit: Ulrich Müller <ulm@gentoo.org> CommitDate: 2019-08-08 21:23:10 +0000 subversion.eclass: Re-add support for old EAPIs. Bug: https://bugs.gentoo.org/690646 Signed-off-by: Ulrich Müller <ulm@gentoo.org> eclass/subversion.eclass | 29 +++++++++++++++++++---------- 1 file changed, 19 insertions(+), 10 deletions(-) https://gitweb.gentoo.org/proj/lisp.git/commit/?id=e9e354f4f1185174f954786937f9093f27c53015 commit e9e354f4f1185174f954786937f9093f27c53015 Author: Ulrich Müller <ulm@gentoo.org> AuthorDate: 2019-08-08 21:18:32 +0000 Commit: Ulrich Müller <ulm@gentoo.org> CommitDate: 2019-08-08 21:18:32 +0000 subversion.eclass: Copied from Gentoo repository. Bug: https://bugs.gentoo.org/690646 Signed-off-by: Ulrich Müller <ulm@gentoo.org> eclass/subversion.eclass | 542 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 542 insertions(+)
For now, I have added a local copy of subversion.eclass that supports these old EAPIs. These ebuilds have more QA issues and should be fixed properly, in the long term (after which the local eclass can be removed again). * dev-chicken/unix-test-9999: failed sourcing ebuild: subversion: EAPI 0 is not supported * dev-scheme/kawa-9999: failed sourcing ebuild: subversion: EAPI 1 is not supported * dev-scheme/mosh-9999: failed sourcing ebuild: subversion: EAPI 2 is not supported
