Received-SPF: pass (zohomail.eu: domain of gentoo.org designates 140.211.166.183 as permitted sender) client-ip=140.211.166.183; envelope-from=bugzilla-daemon@gentoo.org; helo=smtp.gentoo.org;
From: bugzilla-daemon@gentoo.org
To: einfair@zoho.eu
Subject: [Bug 913273] New: [einflay] Ebuild failures occuring in global scope
Date: Wed, 30 Aug 2023 07:52:45 +0000
Reply-To: "DO NOT REPLY" <devnull@localhost.invalid>
Message-ID: <bug-913273-99646@http.bugs.gentoo.org/>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
MIME-Version: 1.0

DO NOT REPLY TO THIS EMAIL. Also, do not reply via email to the person
whose email is mentioned below. To comment on this bug, please visit:

https://bugs.gentoo.org/show_bug.cgi?id=3D913273

            Bug ID: 913273
           Summary: [einflay] Ebuild failures occuring in global scope
           Product: Gentoo Linux
           Version: unspecified
          Hardware: All
               URL: https://qa-reports.gentoo.org/output/repos/einflay.htm
                    l
                OS: Linux
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: Overlays
          Assignee: einfair@zoho.eu
          Reporter: t@laumann.xyz
            Blocks: 552950

Our automated repository checks [1] have detected that the 'einflay'
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/einflay.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


Referenced Bugs:

https://bugs.gentoo.org/show_bug.cgi?id=3D552950
[Bug 552950] [TRACKER] Repository QA issues
--=20
You are receiving this mail because:
You are the assignee for the bug.=