Bug 613010 – [AstroFloyd] Ebuild failures occuring in global scope

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Michał Górny 2017-03-18 10:40:29 UTC]

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

  https://qa-reports.gentoo.org/output/repos/AstroFloyd.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 Marc van der Sluys 2017-04-01 14:06:41 UTC]

I have undertaken the following actions
* some obsolete ebuilds have been removed
* global use of the use() function has been removed
* use of the distutil eclass has been upgraded to the distutil-r1 eclass

I believe this should solve the issues, but this is currently hard to check since the last QA check only shows a git push of my last commit.

[Comment 2 Marc van der Sluys 2017-04-01 14:09:16 UTC]

(In reply to AstroFloyd from comment #1)
> I believe this should solve the issues, but this is currently hard to check
> since the last QA check only shows a git push of my last commit.

I overlooked the last lines of the QA check:
$ pmaint regen --use-local-desc --pkg-desc-index -t 1 AstroFloyd
 * Cache regenerated successfully
Does this mean all is well?

[Comment 3 Michał Górny 2017-04-01 16:15:40 UTC]

> * Cache regenerated successfully

This indicates it's all OK.