Bug 557966 – [xelnor] Ebuild failures occuring in global scope

• Product: Gentoo Infrastructure
• Status: RESOLVED FIXED

[Description Michał Górny 2015-08-16 22:03:25 UTC]

Our automated repository checks [1] have detected that the 'xelnor'
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.

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:

  http://gentoo.github.io/repo-qa-check-results/xelnor.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.

While at it, please consider fixing global-scope 'use' call warnings (if
any). They are not fatal but are considered a serious QA violation.
'use' functions must not ever be called outside of phase functions.

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

[Comment 1 Raphaël Barrois 2015-09-02 23:34:12 UTC]

Hi,

Thanks for the notice; I have removed the outdated ebuild, no errors remain.


By the way, where could I find the QA tools you're using? I'd like to run those tests before committing to my overlay to avoid future breakage.

Thanks,

[Comment 2 Michał Górny 2015-09-03 05:29:13 UTC]

The scripts used to run the thing are at https://bitbucket.org/mgorny/repo-mirror-ci.

However, this particular kind of errors can be triggered via cache regen using 'pmaint regen' (pkgcore) or 'egencache --update' (portage).