Test Rubik

[samfreund]

Qualcomm added some new files, so now we install them. Sadly, it means we run out of space 😢. This fixes that.

We also drop installing the dev version of PV, and default to the latest version.

[samfreund]

Per claude:

The root cause is clear. Here's what's different between the two runs:

The failure is a disk-full error during package installation. Specifically, libsnpe1 (42 MB) failed to unpack with:

cannot copy extracted data for './usr/lib/libSnpeHtpPrepare.so': failed to write (No space left on device)

Here's what changed between the working run (#5) and the failing run (#13) that likely caused this:

New/larger packages being installed in run #13:

• linux-firmware-dragonwing — a new package (1.0.0+20260204) that wasn't present in run Update config.txt #5. It's 65.4 MB, and it appeared in the Qualcomm PPA for the first time around 2026-02-04.
• qcom-adreno1 was upgraded from 1.808.7 to 1.838.2, which may also be larger.
• libqnn1 (59.8 MB) and libsnpe1 (42.0 MB) appear to be new installs in run updated OPi5 and OPi5+base_image to v1.33 #13 as well.

In total, run #13 fetched 759 MB of packages, which apparently exhausted the runner's disk. The working run #5 didn't install linux-firmware-dragonwing or the libqnn1/libsnpe1 packages at all.

Also worth noting: the GITHUB_TOKEN permissions are dramatically different — run #5 had write on almost everything, run #13 has read only (and "Secret source: None"). This suggests run #13 may be triggered from a fork or an untrusted PR, which wouldn't explain the disk space issue but could matter for other things.

To fix the disk space issue, you likely need to free up disk space before the apt install step. A common approach in GitHub Actions is to add a step early in the job:

- name: Free disk space
  run: |
    sudo rm -rf /usr/share/dotnet /usr/local/lib/android /opt/ghc
    df -h

The linux-firmware-dragonwing package (65.4 MB) was published on 2026-02-04 and is the new addition that pushed the build over the edge.