Our automated repository checks [1] have detected that the 'jsteward' 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/jsteward.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
Acknowledged. Is this due to python 3.4 / 3.5 removal from main tree? Anyway I'll set out to upgrade (or remove) the affected packages later this month once I'd have some time to work. Quoting the fatal lines below for easy tracking. $ pmaint regen --use-local-desc --pkg-desc-index -t 1 jsteward * dev-python/aiozmq-0.7.1: failed sourcing ebuild: No supported implementation in PYTHON_COMPAT. [FATAL] * dev-python/april-0.0.1_alpha4: failed sourcing ebuild: No supported implementation in PYTHON_COMPAT. [FATAL] * dev-python/fuocore-0.0.5_alpha5-r1: failed sourcing ebuild: No supported implementation in PYTHON_COMPAT. [FATAL] * dev-python/quamash-0.5.5: failed sourcing ebuild: No supported implementation in PYTHON_COMPAT. [FATAL] * media-sound/feeluown-1.0.5.3: failed sourcing ebuild: No supported implementation in PYTHON_COMPAT. [FATAL] * media-sound/feeluown-1.1.0_alpha2: failed sourcing ebuild: No supported implementation in PYTHON_COMPAT. [FATAL]
(In reply to Pengcheng Xu from comment #1) > Acknowledged. Is this due to python 3.4 / 3.5 removal from main tree? Yes, 3.5. > Anyway I'll set out to upgrade (or remove) the affected packages later this > month once I'd have some time to work. Thank you. > Quoting the fatal lines below for easy tracking. Hmm, I should probably make my script do that in the future.
Ping.
(In reply to Michał Górny from comment #3) > Ping. Should be fixed by https://github.com/KireinaHoro/jsteward/commit/b70002d9fb68d2799b30c0ed3aead7983c21feb5 and https://github.com/KireinaHoro/jsteward/commit/c41361e3b7b67f7026da44c6cf2257a97af1426d Regards,
The bug seems to be fixed in the repository. Closing.