Summary: | [jellybean] Ebuild failures occuring in global scope | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
Component: | Overlays | Assignee: | Hyogeon Gi <qi777xj> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://qa-reports.gentoo.org/output/repos/jellybean.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 552950 |
Description
Michał Górny
2018-08-19 07:59:50 UTC
(In reply to Michał Górny from comment #0) > Our automated repository checks [1] have detected that the 'jellybean' > 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/jellybean.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. > > Please note that due to technical limitations of pkgcore, the processing > stops on the first error found. Once solved, please wait ~30 minutes for > the report to refresh in case new errors may appear. > > 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 Removed some packages, fixed some metadata. The bug seems to be fixed in the repository. Closing. |