4 Commits

Include renames

Author	SHA1	Message	Date
agw	d880e6748c	Bundle our own R 4.5.3 instead of building against Arch's R ... Arch ships R 4.6.1, but JASP pins its R packages against a frozen CRAN snapshot (2026-03-31 for 0.98.1) that targets R 4.5. Configuring against Arch's R fails at Rcpp 1.1.1, which cannot compile on R 4.6 since R_NamespaceRegistry was removed; the Rcpp release that fixes it is newer than the pinned snapshot, so the lockfile cannot reach it either. Build R 4.5.3 into /opt/jasp-desktop/R and point R_HOME at it, matching what upstream CI does. This drops 'r' from depends entirely, so an Arch R upgrade can no longer break an installed JASP, and the rebuild triggers become Qt6 and ICU - the libraries actually still linked against.	2026-09-01 21:40:00 +02:00
agw	3ad88f9b0d	Rename GITEA_TOKEN secret to STATE_PUSH_TOKEN ... Gitea rejects secret names starting with the reserved GITEA_ prefix.	2026-09-01 21:20: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