Bug 906417 – [gerislay] Ebuild failures occuring in global scope

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Thomas Bracht Laumann Jespersen 2023-05-15 12:35:36 UTC]

Our automated repository checks [1] have detected that the 'gerislay'
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/gerislay.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 Larry the Git Cow 2023-05-24 02:19:56 UTC]

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/user/gerislay.git/commit/?id=01f93ef13d7c43dfe729a6b6602ba2092d5f9ed7

commit 01f93ef13d7c43dfe729a6b6602ba2092d5f9ed7
Author:     Gerion Entrup <[e-mail]>
AuthorDate: 2023-05-21 11:02:54 +0000
Commit:     Gerion Entrup <[e-mail]>
CommitDate: 2023-05-21 11:02:54 +0000

    dev-python/plirc: +python 3.11
    
    Closes: https://bugs.gentoo.org/906417
    
    Signed-off-by: Gerion Entrup <[e-mail]>

 app-misc/plirc/Manifest          | 2 +-
 app-misc/plirc/plirc-9999.ebuild | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

[Comment 2 Thomas Bracht Laumann Jespersen 2023-05-24 19:24:08 UTC]

Thanks! sorry for reopening, but it appears there's a PYTHON_COMPAT issue with dev-python/brokenaxes-9999 as well.

[Comment 3 Larry the Git Cow 2023-05-24 23:06:09 UTC]

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/user/gerislay.git/commit/?id=e0a6d6a058b3be8651f20d09a7c386b190631b04

commit e0a6d6a058b3be8651f20d09a7c386b190631b04
Author:     Gerion Entrup <[e-mail]>
AuthorDate: 2023-05-24 23:05:09 +0000
Commit:     Gerion Entrup <[e-mail]>
CommitDate: 2023-05-24 23:06:00 +0000

    dev-python/brokenaxes: drop, unused
    
    Closes: https://bugs.gentoo.org/906417
    Signed-off-by: Gerion Entrup <[e-mail]>

 dev-python/brokenaxes/Manifest               |  1 -
 dev-python/brokenaxes/brokenaxes-9999.ebuild | 20 --------------------
 2 files changed, 21 deletions(-)

[Comment 4 gerion 2023-05-24 23:06:46 UTC]

Hmm, missed that. Hopefully fixed now.