Cannot use --build-on, architecture list is already set in snapcraft.yaml.
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without fix due to inactivity. The --build-on CLI flag remains ignored when architectures is defined in snapcraft.yaml, requiring manual YAML edits for architecture-specific builds.
Suggested action: —
No scores available.
Issue body
If my snap has no 'architectures' entry, I can happily do
snapcraft remote-build --build-on=armhf
However as soon as I add something like, say
architectures:
- build-on: armhf
- build-on: amd64
then I can no longer ask for just the armhf build from the commandline; I need to edit the yaml directly.
This is awkward when I'm trying to fix build errors in particular architectures in my snap.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without fix due to inactivity. The --build-on CLI flag remains ignored when architectures is defined in snapcraft.yaml, requiring manual YAML edits for architecture-specific builds. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The --build-on CLI flag remains incompatible with architectures defined in snapcraft.yaml. Issue abandoned due to inactivity. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The --build-on CLI flag remains ignored when architectures are defined in snapcraft.yaml, requiring manual YAML edits for targeted builds. No fix or workaround was implemented. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2020138 Exclude architectures | snapcraft (launchpad) | open | Feature request to add 'build-not-on' or architecture exclusion support in snapcraft YAML. Currently only whitelist (build-on/build-for) is available. Issue is 3+ years old with no maintainer response or activity. | |
| #5335 `build-on` when running snapcraft locally uses stage packages from the wrong architecture | snapcraft | closed | Closed as expected behavior. Snapcraft uses the build-on architecture for stage-packages. Cross-compilation requires suffixing packages with :$CRAFT_ARCH_BUILD_FOR. Correct usage is now documented in the official Snapcraft guides. | |
| #4150 meta: use build-for in snap.yaml architecture | snapcraft | merged | Merged fix correcting snap.yaml architecture generation. When build-for is set to all, the file now correctly outputs architectures: all instead of the previous incorrect build-on value. Resolves CRAFT-1535. | |
| #2086482 No way to express different build dependencies on different architectures without repetition of the list of dependencies | snapcraft (launchpad) | open | Feature request: snapcraft YAML grammar lacks support for architecture-specific build dependencies without repetition. No maintainer response after 671 days. |