Our automated repository checks [1] have detected that the 'qsx' 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/qsx.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
The reported failure is: > $ pmaint regen --use-local-desc --pkg-desc-index -t 1 qsx > * sys-kernel/dracut-049_p20191222: failed sourcing ebuild: returned val from gen_metadata was 'False' [FATAL] > * Cache regen failed with 1 I’m sorry, but I can’t reproduce that locally with portage (assuming the egencache command is equivalent): > qsx@coruscant ~/src/overlay (git)-[main] > % git status --ignored --short > qsx@coruscant ~/src/overlay (git)-[main] > % git rev-parse HEAD > 782104b415e584cb29219bd9ed38559476514187 > qsx@coruscant ~/src/overlay (git)-[main] > % egencache --update-pkg-desc-index --update-use-local-desc --repo qsx > qsx@coruscant ~/src/overlay (git)-[main] > % echo $? > 0 Also, I don’t know how the ebuild in question can trigger an error, as it’s a quite small patch to sys-kernel/dracut-049-r2 from gentoo.
$ ebuild dracut-049_p20191222.ebuild setup Appending /tmp/gentoo-overlay to PORTDIR_OVERLAY... * dracut-049_p20191222.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] /tmp/gentoo-overlay/sys-kernel/dracut/dracut-049_p20191222.ebuild: line 59: no match: README.* /tmp/gentoo-overlay/sys-kernel/dracut/dracut-049_p20191222.ebuild: line 59: no match: README.* You've got a failing glob in global scope, apparently.
Filed a pkgcore bug to improve the error message.
(In reply to Michał Górny from comment #2) > You've got a failing glob in global scope, apparently. Huh, I see. No idea why I’ve done that, and how I’ve never noticed it. Fixed in https://github.com/qsuscs/gentoo-overlay/commit/ee5a73c57d0a50002f900e73a38bbff0b9903cab
(In reply to Thomas Schneider from comment #4) > No idea why I’ve done that > FileNotFoundError: [Errno 2] No such file or directory: b'README' Ahem. Maybe I should test before committing (or just go to bed). Fixed in https://github.com/qsuscs/gentoo-overlay/commit/306c6be866ccc8ec0c9b6e5954e70999c0827620, I swear.
