azy5030
98ed1c32ce
Run 110's lint job failed at checkout ("couldn't find remote ref <sha>")
because GIT_DEFAULT_HASH: sha256 — copied from the SHA-256 homeserver repo —
made git init create a SHA-256 repo that can't resolve this repo's SHA-1
commits. This overlay is a plain SHA-1 repo, so checkout needs no hash override.
- lint job: drop the bogus GIT_DEFAULT_HASH: sha256 override.
- build job: replace the curl+tar checkout with actions/checkout into
$GITHUB_WORKSPACE, registered with portage via repos.conf; pull dev-vcs/git
in Configure portage (stage3 has no git, which checkout shells out to) and
drop net-misc/curl (only the old checkout used it). QA scan / verify steps
now reference $GITHUB_WORKSPACE.
- CLAUDE.md: correct the SHA-256 claim and rewrite the CI section for the
two-job lint-gate + actions/checkout setup.
just lint passes; ci.yaml passes actionlint.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018MsAYv5RhNLE54fPrviVgS
azy5030 overlay
A personal Gentoo ebuild repository (overlay) for packages not in the main ::gentoo tree.
Packages
| Package | Description |
|---|---|
dev-util/gitea-runner |
Gitea Actions runner (formerly act_runner), built from upstream source with a vendored Go module tree. |
Using the overlay
eselect repository add azy5030 git https://git.azy.dev/azy5030/azy5030-overlay.git
emaint sync -r azy5030
echo 'dev-util/gitea-runner ~amd64' >> /etc/portage/package.accept_keywords/gitea-runner
emerge dev-util/gitea-runner
Maintenance
.gitea/workflows/ci.yamlbuilds each package in agentoo/stage3container on every push and asserts the resulting binary runs..gitea/workflows/bump.yamlrunsscripts/bump-version.shdaily: it checks the upstream releases feed and, when a newer version exists, regenerates + uploads the vendor tarball, bumps the ebuild, and opens a pull request. Requires aBUMP_TOKENrepository secret (scopes: repository read/write, write release).