breadlock ci.yml tries to pacman-install a nonexistent clippy package #8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
The "Install build deps" step in .forgejo/workflows/ci.yml pacman-installs a package literally named
clippy, which does not exist as a separate Arch package (clippy ships as a rustup component or bundled differently, not a pacman target). Every push to main and every PR fails ci.yml's check job instantly with "error: target not found: clippy", before rustfmt/clippy/test/build ever run.Found while promoting breadlock to v0.3.0 for BOS 0.6.2. Does not block releases: package.yml (the actual release build) has its own separate deps list that does not include "clippy" and builds fine. This only breaks the PR/branch CI gate, which has presumably been red for a while.
Fix: compare against how bread-ecosystem or another repo's ci.yml installs clippy (likely
rustup component add clippyafter installing rustup, or just drop the pacman clippy target and usecargo clippyfrom whatever toolchain rust/cargo already provides if it's bundled).This fix is already present on origin/main in commit
8a7a570162. It removes clippy and rustfmt from the pacman install list, since Arch's rust package provides both. The current main commit05574a0has a successful CI push check (run 28, 4m53s), confirming the workflow now passes. No new branch or PR is needed.