Our automated repository checks [1] have detected that the 'powerman' 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/powerman.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
How to reproduce this issue locally, to make sure it's fixed? I've tried this: # emerge pkgcore $ pmaint sync powerman *** syncing powerman Already up to date. *** synced powerman $ pmaint regen --use-local-desc --pkg-desc-index -t 32 powerman $ And as you see I didn't get that error. Maybe I need to use unstable/latest pkgcore or some extra setup? P.S. The ebuild mentioned in QA report is for sure outdated and can be removed, but I'd like to make sure there are no other errors before reporting it as fixed.
(In reply to Alex Efros from comment #1) > How to reproduce this issue locally, to make sure it's fixed? I've tried > this: > > # emerge pkgcore > $ pmaint sync powerman > *** syncing powerman > Already up to date. > *** synced powerman > $ pmaint regen --use-local-desc --pkg-desc-index -t 32 powerman > $ > > And as you see I didn't get that error. Maybe I need to use unstable/latest > pkgcore or some extra setup? I think you may need to emerge --sync first, as the change only recently landed in the Gentoo repository: https://github.com/gentoo/gentoo/commit/12b96919c87fe9391c5ed4afb87838f6981c4d3d#diff-f191f2aaf5c4eeec1dfbe942bdccc39344df438ed700dd48a1458a96f63dc2c3. > > P.S. The ebuild mentioned in QA report is for sure outdated and can be > removed, but I'd like to make sure there are no other errors before > reporting it as fixed.
(In reply to Sam James from comment #2) > I think you may need to emerge --sync first, as the change only recently > landed in the Gentoo repository: Thanks! Fixed.
