4 Commits

Include renames

Author	SHA1	Message	Date
agw	bdbd6f5978	Fix the two publishing steps that had never run for real ... push-aur.sh: mktemp -d creates the work directory as 0700 root, so the builder user could not enter it to run makepkg ('cd: Permission denied'), and the git steps afterwards would refuse a tree owned by another user. Give builder the whole tree for makepkg and hand it back to root before git. record-state.sh: 'git diff --quiet' ignores untracked files, so the first state.json was reported as unchanged and never committed, which would have rebuilt and republished every night. Stage it before comparing. Both were found by the first publishing run; push-aur.sh was then tested end to end in a clean Arch container with a dummy key. Claude-Session: https://claude.ai/code/session_01GGe7kUhooMFuzY6GaDb2w9	2026-10-03 20:47:43 +02:00
agw	440cf8c475	Push HEAD:master to the AUR rather than a branch name ... Cloning a package that does not exist on the AUR yet gives an empty repo whose initial branch follows the runner's init.defaultBranch, which is not guaranteed to be master. Verified against the real AUR remote: auth works, the empty clone yields a .git, and 'git diff --staged --quiet' correctly reports changes there - so the first publish commits instead of exiting early with 'nothing to push'.	2026-09-01 23:05:00 +02:00
agw	92961bd7b3	Align AUR publishing with the existing pi3-smart-workspace pattern ... Reuse the established conventions rather than inventing new ones: the AUR_SSH_PRIVATE_KEY secret name, pushing from an archlinux:base-devel job container instead of docker-in-docker, and the existing git identity. The AUR job only needs the PKGBUILD, so the 1.5 GB tarball never crosses a job boundary - it goes straight to GitHub Releases from the build job. Also correct the Gitea job-timeout setting name to ENDLESS_TASK_TIMEOUT.	2026-09-01 21:10:00 +02:00
agw	0d4db32d5c	Automated Arch binary builds of JASP for the AUR ... Upstream JASP ships no Linux binary, so the existing AUR package builds everything from source including several hundred R packages. This builds that once in CI and publishes the result as jasp-desktop-bin. JASP links against the system R and Qt6 rather than bundling them, so a rebuild is triggered by an Arch r/qt6-base bump as well as by a new JASP release, and the generated PKGBUILD pins depends to the versions actually built against.	2026-09-01 20:30:00 +02:00