fix(ci): skip prepare() in publish-aur metadata container #51
Reference in New Issue
Block a user
Delete Branch "fix/aur-skip-prepare"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Third in a chain of fixes after #49 and #50. With ownership and quoting resolved, the next run (24199871832) got all the way to `makepkg` and failed with:
```
/pkg/PKGBUILD: line 34: cargo: command not found
==> ERROR: A failure occurred in prepare().
```
Root cause
The publish job's container only installs `binutils git sudo` because its only purpose is to regenerate `.SRCINFO`. But `makepkg -od` still runs `prepare()`, which invokes `cargo`. The sibling `validate` job sidesteps this with `--noprepare` (and installs `rust` anyway).
Fix
Add `--noprepare` to the metadata-generation invocation. In makepkg's pipeline, `pkgver()` runs before `prepare()`, so `.SRCINFO` still captures the computed version — and we avoid dragging a ~100 MB rust toolchain into a container that only needs to parse PKGBUILD metadata.
Test plan
🤖 Generated with Claude Code