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 | ||
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
2019-12-14 12:27:51 UTC
This is the complete error log referenced below: salfter {'description': {'en': "Scott Alfter's ebuilds"}, 'homepage': 'https://gitlab.com/salfter/portage', 'name': 'salfter', 'owner': [{'email': 'scott@alfter.us', 'name': 'Scott Alfter', 'type': 'person'}], 'quality': 'experimental', 'source': [{'type': 'git', 'uri': 'https://gitlab.com/salfter/portage.git'}], 'status': 'unofficial'} $ pmaint sync salfter Already up to date. *** syncing salfter *** synced salfter * Sync succeeded $ git log --format=%ci -1 $ git show -q --pretty=format:%G? HEAD $ pmaint regen --use-local-desc --pkg-desc-index -t 1 salfter * Cache regenerated successfully There's nothing in there that looks like an error. Is this a false alarm? If not, is there something that indicates which ebuild is to blame? Before receiving this bug, I did notice that the mediaelch ebuild was triggering an error pertaining to it still using EAPI 5 when I went to update one of my machines. I tweaked it to use EAPI 6 and committed the change. Might that have been what the repo checks were complaining about? It's possible. I could check git log but since it's happy now, I don't think it's worth the effort. The bug seems to be fixed in the repository. Closing. |