Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 840098 - [odroidc4] Ebuild failures occuring in global scope
Summary: [odroidc4] Ebuild failures occuring in global scope
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Overlays (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Sven Schwyn (svoop)
URL: https://qa-reports.gentoo.org/output/...
Whiteboard:
Keywords:
Depends on:
Blocks: repository-qa-issues
  Show dependency tree
 
Reported: 2022-04-22 11:01 UTC by Thomas Bracht Laumann Jespersen
Modified: 2022-09-05 13:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Bracht Laumann Jespersen 2022-04-22 11:01:27 UTC
Our automated repository checks [1] have detected that the 'odroidc4'
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/odroidc4.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 Thomas Bracht Laumann Jespersen 2022-04-29 11:44:19 UTC
ping
Comment 2 Thomas Bracht Laumann Jespersen 2022-05-23 12:39:41 UTC
ping
Comment 3 Sven Schwyn (svoop) 2022-05-23 14:26:01 UTC
pong

I'm inundated with work, but my yearly four month sabbatical begins in three weeks, the plan is to go over the overlays and bring them up to speed then.
Comment 4 Thomas Bracht Laumann Jespersen 2022-05-23 14:35:00 UTC
(In reply to Sven Schwyn (svoop) from comment #3)
> pong
> 
> I'm inundated with work, but my yearly four month sabbatical begins in three
> weeks, the plan is to go over the overlays and bring them up to speed then.
Nice, thanks for the heads up. I won't remove the repo then :-)
Comment 5 Sven Schwyn (svoop) 2022-05-23 14:36:52 UTC
Btw, same goes for the "bitcetera" overlay. You've already removed that one, sure understand why. I'll ping you when they're in an acceptable state again.
Comment 6 Thomas Bracht Laumann Jespersen 2022-05-23 14:39:08 UTC
(In reply to Sven Schwyn (svoop) from comment #5)
> Btw, same goes for the "bitcetera" overlay. You've already removed that one,
> sure understand why. I'll ping you when they're in an acceptable state again.
Just open a PR against https://github.com/gentoo/api-gentoo-org/ to have bitcetera added back when it's ready.
Comment 7 Thomas Bracht Laumann Jespersen 2022-08-16 13:01:23 UTC
ping
Comment 8 Sven Schwyn (svoop) 2022-08-16 21:44:41 UTC
Finally working on it. I've upped to EAPI 8 which shouldn't cause any trouble. I can't really test the two ebuilds for now because my ODROID C4 at home caved under the heatwave and I'm some 2000 miles away. I'll see whether the cache rebuild works again.

Do you know how QA reports are triggered? On commits or time based?
Comment 9 Sven Schwyn (svoop) 2022-08-18 21:52:52 UTC
All green again, sorry for the delay!
Comment 10 Thomas Bracht Laumann Jespersen 2022-08-19 10:25:42 UTC
Cool, thanks for fixing!
Comment 11 Thomas Bracht Laumann Jespersen 2022-09-05 13:06:01 UTC
The bug seems to be fixed in the repository. Closing.