jasp-desktop-bin

33 Commits 1 Branch 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
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 Build JASP binary and publish to AUR / build (push) Failing after 12s Details Build JASP binary and publish to AUR / check (push) Successful in 10s Details 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

Author

SHA1

Message

Date

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

Build JASP binary and publish to AUR / build (push) Failing after 12s

Details

Build JASP binary and publish to AUR / check (push) Successful in 10s

Details

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