The upload steps named the web host by its internal address. It now comes
from the TARBALLZ_TARGET repository variable, so the public workflow carries
no infrastructure details.
Claude-Session: https://claude.ai/code/session_01GGe7kUhooMFuzY6GaDb2w9
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
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