Our automated repository checks [1] have detected that the 'ikelos' 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: http://gentoo.github.io/repo-qa-check-results/ikelos.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
Thanks very much for filing this bug. I've removed a number of the old ebuilds that were causing problems, and bumped a few others. Could you please point me at the mailing list post on -dev-announce that indicates all EAPI<4 are officially no longer supported in the tree or overlays please? It seems like a bit of a surprise to me...
(In reply to Mike Auty from comment #1) > Could you please point me at the mailing list post on -dev-announce that > indicates all EAPI<4 are officially no longer supported in the tree or > overlays please? It seems like a bit of a surprise to me... Well, if you mean the reported failures, then they aren't that much about EAPIs being no longer supported but eclasses removing support for them. And this happens for two reasons: 1. because maintaining support for old EAPIs is cumbersome (extra conditionals, sometimes some eclass features can't be expressed in old EAPIs), 2. because it helps forcing developers to use newer EAPI when they need to use an additional eclass. As for the generic deprecation of old EAPIs: from layout.conf, this was pretty much a Council decision: # Bug #470670 - gentoo's council says to deprecate EAPIs 1 and 2. # 2014-02-25 council meeting deprecated EAPIs 0 and 3. eapis-deprecated = 0 1 2 3 But it follows the generic policy of 'always use latest EAPI'. Which aims towards a better world where developers don't have to remember how 6 EAPIs differ one from another, and users can use the newest features provided by the PM.
Thanks very much, I must have missed that at the time. All outstanding errors resolved now. 5:)