Bug 566302 – [sabayon-tools] Ebuild failures occuring in global scope

• Product: Gentoo Infrastructure
• Status: RESOLVED FIXED

[Description Michał Górny 2015-11-20 07:16:55 UTC]

Our automated repository checks [1] have detected that the 'sabayon-
tools' 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/sabayon-tools.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 Michał Górny 2015-11-20 07:17:29 UTC]

> caught exception 'junk after document element: line 12, column 0' while processing 'ebuild src: x11-wm/moksha-0.1.0'
> caught exception 'junk after document element: line 12, column 0' while processing 'ebuild src: x11-wm/moksha-9999'

Those are metadata.xml problems.

[Comment 2 fuse809 2015-11-20 08:04:10 UTC]

Well this overlay is mostly just me trying to develop my ebuild-writing skills in a safe way, as I only just started using Gentoo-based systems in August this year and my knowledge of bash scripting before that was minimal. So I'm guessing that merely removing metadata.xml in the x11-wm/moksha directory will probably be sufficient, seeing how that seems to be generating these errors.

[Comment 3 Michał Górny 2015-11-20 14:34:07 UTC]

Please don't do that. In your metadata.xml you've got premature </pkgmetadata> before second maintainer.

[Comment 4 fuse809 2015-11-21 00:34:18 UTC]

OK, I believe I have fixed the metadata issue. How do I confirm this?

[Comment 5 Michał Górny 2015-11-21 07:11:07 UTC]

You can use 'xmllint --noout metadata.xml' to verify the XML correctness locally. After pushing, the linked check results should be updated in ~20 minutes.

[Comment 6 Michał Górny 2015-11-28 20:53:40 UTC]

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