Our automated repository checks [1] have detected that the 'jorgicio' 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/jorgicio.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
Ping.
https://github.com/gentoo-mirror/jorgicio/ 404 Is the person still alive?
Sorry, but I thought you read the description in the mirror but I'll resume: I'm not using Gentoo anymore but I won't delete the mirror, so I requested that the interested people who want to collaborate, please, send a PR and I'll check it. Sorry for the inconveniences. I don't know how to do this in other distro which is not Gentoo (I'm in Manjaro)
(In reply to jorgicio from comment #3) > Sorry, but I thought you read the description in the mirror but I'll resume: > I'm not using Gentoo anymore but I won't delete the mirror, so I requested > that the interested people who want to collaborate, please, send a PR and > I'll check it. > > Sorry for the inconveniences. I don't know how to do this in other distro > which is not Gentoo (I'm in Manjaro) Your repo branch is master. But README.md says main.
(In reply to jospezial from comment #4) > (In reply to jorgicio from comment #3) > > Sorry, but I thought you read the description in the mirror but I'll resume: > > I'm not using Gentoo anymore but I won't delete the mirror, so I requested > > that the interested people who want to collaborate, please, send a PR and > > I'll check it. > > > > Sorry for the inconveniences. I don't know how to do this in other distro > > which is not Gentoo (I'm in Manjaro) > > Your repo branch is master. But README.md says main. Actually, the repo is main since I change it and mentioned in the README about it. Check it again. https://github.com/jorgicio/jorgicio-gentoo-overlay
Ah,ok, I was looking at https://github.com/gentoo-mirror/jorgicio then I saw it at https://github.com/jorgicio/jorgicio-gentoo-overlay
I've opened a PR to remove the overlay from repositories.xml as the QA issues aren't being addressed (even if the overlay is still being developed). PR here: https://github.com/gentoo/api-gentoo-org/pull/487
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/data/api.git/commit/?id=332f21bb458c6d79a5e1e216186d2e9ea4a5e8fb commit 332f21bb458c6d79a5e1e216186d2e9ea4a5e8fb Author: Thomas Bracht Laumann Jespersen <t@laumann.xyz> AuthorDate: 2022-03-30 09:01:34 +0000 Commit: Jakov Smolić <jsmolic@gentoo.org> CommitDate: 2022-03-30 17:21:25 +0000 repositories.xml: Remove 'jorgicio' overlay Longstanding CI failures. Owner doesn't use Gentoo anymore. Overlay is being updated, but the failures haven't been addressed. Closes: https://bugs.gentoo.org/772656 Signed-off-by: Thomas Bracht Laumann Jespersen <t@laumann.xyz> Closes: https://github.com/gentoo/api-gentoo-org/pull/487 Signed-off-by: Jakov Smolić <jsmolic@gentoo.org> files/overlays/repositories.xml | 12 ------------ 1 file changed, 12 deletions(-)
Removing overlay from gentoo-mirror makes portage misbehave on "emerge --sync". It requires user input but due to parallel fetching of many overlays the true error message gets lost in the mess. Anyway, emerge --sync shouldn't wait on user input. === Sync completed for gentoo >>> Syncing repository 'steam-overlay' into '/var/db/repos/steam-overlay'... >>> Syncing repository 'jorgicio' into '/var/db/repos/jorgicio'... /usr/bin/git fetch origin /usr/bin/git fetch origin Username for 'https://github.com': remote: Enumerating objects: 13, done. remote: Counting objects: 100% (13/13), done. remote: Compressing objects: 100% (2/2), done. remote: Total 7 (delta 4), reused 7 (delta 4), pack-reused 0 Unpacking objects: 100% (7/7), 572 bytes | 190.00 KiB/s, done. From https://github.com/gentoo-mirror/steam-overlay 56ef383..837ac93 master -> origin/master Updating 56ef383..837ac93 Fast-forward metadata/md5-cache/media-libs/jpeg-compat-2.0.6-r800 | 2 +- metadata/timestamp.chk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) === Sync completed for steam-overlay ^C Exiting on signal Signals.SIGINT Task was destroyed but it is pending! task: <Task pending name='Task-11' coro=<ForkProcess._proc_join() done, defined at /usr/lib/python3.9/site-packages/portage/util/_async/ForkProcess.py:75> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7fee8b816be0>()]> cb=[ForkProcess._proc_join_done(<Process name...tcode=-SIGINT>)()]> Task was destroyed but it is pending! [...] Note that the relevant part is "Username for 'https://github.com':" which is difficult to notice and emerge looks like it hung. I ended up pressing ^C and got obscure portage errors. If I just pressed enter twice (for username and password), I would see access denied message and the emerge would end work gracefully.
