Bug 859127 – [webos] Ebuild failures occuring in global scope

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Thomas Bracht Laumann Jespersen 2022-07-18 18:55:04 UTC]

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

In particular, please look for highlighted error messages.

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 Maksym Sditanov 2022-07-19 21:05:48 UTC]

I will take a look and fix ebulids (EAPI-5 is deprecated). 

Is it possible to change Status to "In progress" somehow?

Thanks

[Comment 2 Maksym Sditanov 2022-07-21 20:33:09 UTC]

Fixes are done. 

@Thomas Please, may your trigger QA repository check

Thanks

[Comment 3 Thomas Bracht Laumann Jespersen 2022-07-21 21:32:41 UTC]

(In reply to Maksym Sditanov from comment #2)
> Fixes are done. 
Thanks!

> @Thomas Please, may your trigger QA repository check

They run by themselves, I just run some scripts periodically to file bugs. But it all looks good, I'll run the scripts tomorrow. Thanks again!

[Comment 4 Maksym Sditanov 2022-07-21 22:00:33 UTC]

Thanks for help