Summary: | [salfter] Ebuild failures occuring in global scope | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
Component: | Overlays | Assignee: | Scott Alfter <scott> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | t |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://qa-reports.gentoo.org/output/repos/salfter.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 552950 |
Description
Michał Górny
2021-05-29 15:17:24 UTC
ping ping. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/data/api.git/commit/?id=31746197a97eb70829afb75db3dcd19d37448ae4 commit 31746197a97eb70829afb75db3dcd19d37448ae4 Author: Thomas Bracht Laumann Jespersen <t@laumann.xyz> AuthorDate: 2022-04-13 15:51:57 +0000 Commit: Jakov Smolić <jsmolic@gentoo.org> CommitDate: 2022-04-14 07:26:07 +0000 repositories.xml: remove 'salfter' overlay Longstanding CI failures, repository appears to be maintained, but the failures haven't been addressed. Bug: https://bugs.gentoo.org/792843 Signed-off-by: Thomas Bracht Laumann Jespersen <t@laumann.xyz> Closes: https://github.com/gentoo/api-gentoo-org/pull/507 Signed-off-by: Jakov Smolić <jsmolic@gentoo.org> files/overlays/repositories.xml | 10 ---------- 1 file changed, 10 deletions(-) This morning was the first I'd heard of any issues...don't know how that happened, and the error log mentioned in the first message is no longer accessible. With a little bit of poking around, though, it appears that the errors may have had to do with some ebuilds still using EAPI 4 or 5. I found them all, deleted most as I no longer needed them, and the relative handful that I wanted to keep have been updated to EAPI 8. The most recent commit (e5cc352b) fixed the last of the old ebuilds to bring it up to EAPI 8. How do I get my overlay reinstated? (In reply to Scott Alfter from comment #4) > This morning was the first I'd heard of any issues...don't know how that > happened, and the error log mentioned in the first message is no longer > accessible. Sorry that you've missed them! > With a little bit of poking around, though, it appears that the errors may > have had to do with some ebuilds still using EAPI 4 or 5. I found them all, > deleted most as I no longer needed them, and the relative handful that I > wanted to keep have been updated to EAPI 8. The most recent commit > (e5cc352b) fixed the last of the old ebuilds to bring it up to EAPI 8. How > do I get my overlay reinstated? I think the simplest thing is just to open a PR against [1] that effectively reverts [2]. [1]: https://github.com/gentoo/api-gentoo-org [2]: https://github.com/gentoo/api-gentoo-org/pull/507 (In reply to Thomas Bracht Laumann Jespersen from comment #5) > (In reply to Scott Alfter from comment #4) > > How do I get my overlay reinstated? > > I think the simplest thing is just to open a PR against [1] that effectively > reverts [2]. Got it...it's already in the works. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/data/api.git/commit/?id=85bf6a2cb30ac659fa0655af2fae0a093df0f771 commit 85bf6a2cb30ac659fa0655af2fae0a093df0f771 Author: Scott Alfter <scott@alfter.us> AuthorDate: 2022-04-18 14:26:52 +0000 Commit: Jakov Smolić <jsmolic@gentoo.org> CommitDate: 2022-04-18 19:06:53 +0000 Revert "repositories.xml: remove 'salfter' overlay" This reverts commit 31746197a97eb70829afb75db3dcd19d37448ae4. EAPI 4/5 ebuilds either updated or removed. Bug: https://bugs.gentoo.org/792843 Signed-off-by: Scott Alfter <scott@alfter.us> Closes: https://github.com/gentoo/api-gentoo-org/pull/510 Signed-off-by: Jakov Smolić <jsmolic@gentoo.org> files/overlays/repositories.xml | 10 ++++++++++ 1 file changed, 10 insertions(+) Reopening. The QA reports mention EAPI 0, 2 and 4, also some PYTHON_COMPAT: https://qa-reports.gentoo.org/output/repos/salfter.html ping The remaining issues should be fixed as of the most recent commit: https://gitlab.com/salfter/portage/-/commit/4f24250466db32a2a388d663bc03dc3cb0477b06 The bug seems to be fixed in the repository. Closing. Thanks! |