Homebrew could not clone the Gitea tap (git over HTTP is disabled), so
brew tap agw/ahfail never worked. The formula now lives in
asger-weirsoee/homebrew-tap, and releases update it with a deploy key.
Claude-Session: https://claude.ai/code/session_012LCTmU2ewo8tnM1dByYAoG
A second AUR package with the same release prebuilt. The workflow
builds the tag into a staged meson install tree (--prefix=/usr, no
update check), names the tarball after its sha256 so a published name
never changes bytes, uploads it to asger.weirsoe.dk/tarballz with a key
that may only write ahfail-* tarballs, checks that the public URL serves
the same bytes, and only then pushes ahfail-bin to the AUR. A manual run
can now publish source, bin or both.
Claude-Session: https://claude.ai/code/session_012LCTmU2ewo8tnM1dByYAoG
The Maintainer line uses the usual AUR form (asger at weircon dot dk)
instead of a raw address that spam crawlers harvest. The AUR workflow
can now also be started by hand with a version and pkgrel, so a fix to
the PKGBUILD alone can be published without a new upstream release.
Claude-Session: https://claude.ai/code/session_012LCTmU2ewo8tnM1dByYAoG
Gitea refuses secret names starting with GITEA_, so GITEA_TOKEN could
never be set and every release failed; it is RELEASE_TOKEN now. git over
HTTP is disabled on this Gitea, so the tap formula is updated through
the contents API instead of a clone and push.
Claude-Session: https://claude.ai/code/session_012LCTmU2ewo8tnM1dByYAoG
The runner rewrites Gitea URLs to SSH on port 2222, and without openssh
git falls back to the 'simple' SSH variant, which cannot set a port, so
checkout failed.
Claude-Session: https://claude.ai/code/session_012LCTmU2ewo8tnM1dByYAoG
The locker needs gtk-session-lock, which Ubuntu does not package, and
Arch is where the AUR package is built. The release tarball now carries
the ahfail binary and its PAM file as well.
Claude-Session: https://claude.ai/code/session_012LCTmU2ewo8tnM1dByYAoG
Four cargo builds with four target directories compiled the GTK and
GStreamer bindings four times; one build with a shared target directory
takes a package build from about an hour to about seven minutes.
Adds the ahfail binary and /etc/pam.d/ahfail to the install, the
update_check option, an AUR PKGBUILD (offline build after cargo fetch
--locked) and a tag-triggered workflow that publishes it and mirrors the
PKGBUILD to the tarballz index.
Claude-Session: https://claude.ai/code/session_012LCTmU2ewo8tnM1dByYAoG
After uploading the release asset, the workflow now:
1. Computes the SHA256 of the source tarball from the Gitea archive endpoint
2. Clones homebrew-ahfail via token auth, patches url + sha256 in Formula/ahfail.rb
3. Commits and pushes — so `brew upgrade ahfail` works without any manual steps
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Replaces the manual curl-based release creation with the standard action,
consistent with other Gitea repos. Also bumps checkout to @v4.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
ahfail_tests.rs calls on_activation which initialises GTK — needs a virtual
display in CI just like the Meson test step.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
ubuntu-latest now resolves to Ubuntu 24.04 which ships meson 1.3.2 (satisfies
>=1.3.0) and enforces PEP 668, blocking pip3 install without --break-system-packages.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Asger Geel Weirsøe