diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-19 11:52:32 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-19 11:52:32 -0500 |
| commit | db851ffba560272f1e813dd13d09fb9f88d0faff (patch) | |
| tree | aa836d45d5ba4984fae6c9ea7707b4a64b624667 /scripts | |
| parent | b4c0f72235383c33d2b7ce82d8ae4e397f04a6eb (diff) | |
| download | archangel-db851ffba560272f1e813dd13d09fb9f88d0faff.tar.gz archangel-db851ffba560272f1e813dd13d09fb9f88d0faff.zip | |
fix(build): drop cached archzfs packages before mkarchiso runs
The upstream archzfs mirror has handed us corrupted .pkg.tar.zst files several times now. Past builds aborted at pacstrap with "File X is corrupted (invalid or corrupted package (checksum))". The cached package sits in /var/cache/pacman/pkg/ between builds, so once it's bad every subsequent build fails until someone manually deletes it.
I added a step right before mkarchiso that rm -f's the archzfs entries (zfs-dkms-*, zfs-utils-*) from the host pacman cache. Pacstrap fetches fresh copies on the next build. Costs ~30s of bandwidth on a warm mirror. Saves debugging a baffling pacstrap abort.
The proper permanent fix is a local caching proxy (pacoloco or flexo). That lives on the Medium Lifts backlog. This commit is the cheap interim that addresses the recurring failure mode without new infrastructure.
Shellcheck reports clean. The rm -f globs handle empty-match cleanly (silent return). I skipped a full build re-run since the parent commit (b4c0f72) already verified the surrounding mkarchiso path. This is a defensive prepend with no interaction surface.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
