azy5030 34d769625a
CI / lint (push) Successful in 20s
CI / build (push) Successful in 6m2s
ci: keep curl+tar checkout in the build job (no node in stage3 container)
actions/checkout can't run in the build job: the Gitea runner executes JS
actions via `docker exec node …` inside the job container, and gentoo/stage3
ships no node, so checkout died with `exec: "node": ... not found` (exit 127)
in run 111. Revert the build job to the node-free curl+tar checkout (restore
net-misc/curl, /var/db/repos/azy5030 paths) and document why.

The lint job keeps actions/checkout — it has no container: and runs in the
runner's default node-capable image, where plain checkout works on this SHA-1
repo (confirmed green in run 111's lint job).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018MsAYv5RhNLE54fPrviVgS
2026-06-19 20:46:02 -05:00
2026-05-20 20:51:48 -05:00

azy5030 overlay

CI

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.yaml builds each package in a gentoo/stage3 container on every push and asserts the resulting binary runs.
  • .gitea/workflows/bump.yaml runs scripts/bump-version.sh daily: 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 a BUMP_TOKEN repository secret (scopes: repository read/write, write release).
S
Description
Collection of packages that I couldn't find anywhere else
Readme 180 KiB
2026-09-25 00:10:42 -05:00
Languages
Shell 74.9%
Just 25.1%