Bug 609962 – [youbroketheinternet] Ebuild failures occuring in global scope

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Michał Górny 2017-02-18 22:53:57 UTC]

Our automated repository checks [1] have detected that the
'youbroketheinternet' 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/youbroketheinternet.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 lynX 2017-02-20 10:32:18 UTC]

Dear Michał, I don't understand the problem. I assume it has something to do with the divergences between our fork of git-r3.class and the one in portage. I suggest we merge our changes into the official one so ours is no longer needed. Here's the reason why our git-r3.class is different:

# Patched by symlynX to allow for gits via Tor. Why Tor? Because
# unlike HTTPS it provides end-to-end authenticity which is not
# susceptible to man-in-the-middle attacks, so all gits should
# migrate to Tor, cjdns or gnunet-vpn. But the latter two do
# not need custom changes to this file to do their job.

git blame should easily help you see which changes I made for onion-based
repositories to work out of the box.

[Comment 2 Michał Górny 2017-02-20 14:30:28 UTC]

*   inherit for mozconfig-v5.31 failed

That is the eclass that's no longer in gentoo. Once you fix that, the latter error should disappear or become clearer.

[Comment 3 lynX 2017-03-02 05:11:02 UTC]

Ok, done. Would you please consider including onion support in git-r3.class so we avoid diverging code at that point?

[Comment 4 Michał Górny 2017-03-06 05:58:54 UTC]

(In reply to lynX from comment #3)
> Ok, done. Would you please consider including onion support in git-r3.class
> so we avoid diverging code at that point?

Please open a bug or pull request for that and attach a patch.

[Comment 5 Michał Górny 2017-03-18 10:43:52 UTC]

The bug seems to be fixed in the repository. Closing.