diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-22 20:28:15 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-22 20:28:15 -0500 |
| commit | bed054f46e3b41aae0d599ed7fbc3e1e42d6ddd7 (patch) | |
| tree | 81a3a1fa97e44bb445bdf43877feeaffac1e4bff /docs | |
| parent | 0f8bbc7c1e2c2f6fec0b17753ac0d9c4a3ad4317 (diff) | |
| download | archangel-bed054f46e3b41aae0d599ed7fbc3e1e42d6ddd7.tar.gz archangel-bed054f46e3b41aae0d599ed7fbc3e1e42d6ddd7.zip | |
fix(build): clear stale archzfs from the pacoloco cache too
archzfs re-uploads its GitHub release assets under the same filename, so pacoloco keeps serving a zfs-dkms/zfs-utils it cached earlier while pacman fetches a fresh archzfs.db with a new checksum. The two mismatch and pacstrap aborts with "invalid or corrupted package." build.sh already drops the stale packages from the host pacman cache, but it never cleared the pacoloco layer, which the VM test installs route through too, so test-install.sh kept hitting the corruption (four times in one session).
build.sh runs as root, so it now clears /var/cache/pacoloco/pkgs/archzfs/zfs-* alongside the host cache, which makes the build-then-test flow self-healing. The pacoloco cache is root-owned and test-install.sh runs as the user, so it can't clear it unattended. Instead, test-install.sh now recognizes the corruption (is_archzfs_cache_corruption) and prints how to clear it, the way it already names the SSH_PORT override on a port collision. A retry alone won't help since it hits the same cached file, so this fails fast with the hint rather than retrying.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions
