Our automated repository checks [1] have detected that the 'archenroot' 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/archenroot.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. Please note that due to technical limitations of pkgcore, the processing stops on the first error found. Once solved, please wait ~30 minutes for the report to refresh in case new errors may appear. 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
will fix this issue, but in next week, being on vacation now...
Ping.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/data/api.git/commit/?id=e8b06ae8ee6ee5160b1490a8dbdb33a1ce98e8e5 commit e8b06ae8ee6ee5160b1490a8dbdb33a1ce98e8e5 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2018-01-12 12:23:15 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2018-01-12 12:23:15 +0000 repositories: Remove archenroot b/ of QA issues Closes: https://bugs.gentoo.org/630154 files/overlays/repositories.xml | 10 ---------- 1 file changed, 10 deletions(-)
Ajajaj, going to look at that :-)
The QA report is not available anymore, what can I do for undoing the action? I was quite busy with new artefact releases into overlay and actually forgot about fixing some Gentoo QA stuff, sorry. Thanks for hints, I was running repoman, but it reported lots of fatal issues, which are actually not fatal (as per my understanding)
The error in the log was: * Source: /dbus-cpp-5.0.0_p20160809_p0_p02 * ERROR: dev-libs/dbus-cpp-5.0.0_p20160809_p0_p02 failed (depend phase): * External commands disallowed during metadata regen: sed s,/*[^/]\+/*$,, Preferably just upgrade to newest Portage and do 'ebuild foo.ebuild setup' for every *.ebuild in there -- if it doesn't explode, you should be good.
Nice, thx for hints!
Well, this artefact doesn't scream anything to me: mobile-server /var/lib/layman/archenroot/dev-libs/dbus-cpp # ebuild dbus-cpp-5.0.0_p20160809_p0_p02.ebuild setup * dbus-cpp_5.0.0+16.10.20160809.orig.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * Source: /var/tmp/portage/dev-libs/dbus-cpp-5.0.0_p20160809_p0_p02/work/dbus-cpp-5.0.0_p20160809_p0_p02 * Source: /var/tmp/portage/dev-libs/dbus-cpp-5.0.0_p20160809_p0_p02/work * Source: /var/tmp/portage/dev-libs/dbus-cpp-5.0.0_p20160809_p0_p02/work/dbus-cpp-5.0.0_p20160809_p0_p02 * Source: /var/tmp/portage/dev-libs/dbus-cpp-5.0.0_p20160809_p0_p02/work
The repository has been removed, rendering this bug obsolete.
