The eapi-per-eclass at $URL recently broke. It currently says that every eclass is inherited by 0 packages.
The script still works locally and there have been no changes to the repo recently, so I suspect there something is not correct on the infra side of things.
<snip> Error in configuration: Failed instantiating default domain 'livefs domain' Failed instantiating section 'livefs domain' Failed instantiating section 'livefs domain': exception caught from 'pkgcore.ebuild.domain.domain' failed parsing profile '/usr/portage/profiles/eapi-5-files', file 'eapi'. error: unsupported eapi: 5 </snip> I updated pkgcore to 0.8.6 but still the same. portage is up2date (2.1.11.55).
Thanks for looking into it, it makes sense that it broken with the introduction of the EAPI 5 profile stuff. For the record, it is working with pkgcore-9999 currently.
Maybe pkgcore maintainers could make a bump including eapi5 support from their version control system :/ OK to CC them here?
(In reply to Pacho Ramos from comment #4) > Maybe pkgcore maintainers could make a bump including eapi5 support from > their version control system :/ OK to CC them here? I have spoken to them previously, and they said they are expecting to do a release very soon.
Any word on a snapshot? It would be nice to have these back.
Assign back to infra when there is an in-tree solution. Thanks.
Assigning back to infra since whatever machine that runs the qa-reports stuff should sync and install pkgcore-0.9 and everything should work again. If not, please file some bugs upstream.
updated on scrubfowl, the qa-reports host
