Architectures keyword incorrectly interpreted by remote-build
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Abandoned without a code fix. The remote-build command misinterpreted the architectures keyword, only processing i386 and failing. A CLI workaround using --build-on is recommended instead.
Suggested action: —
No scores available.
Issue body
I am using snapcraft remote-build.
I first set:
architectures:
- build-on: [s390x, ppc64el, arm64, armhf, amd64, i386]
In my snapcraft.yaml.
But when I ran snapcraft remote-build only i386 was building, none of the other architectures.
At the end it then says "Skipping unknown artifact: {url}" from https://github.com/snapcore/snapcraft/blob/534ee1c1f015a560783c825b11d9d07071f9119c/snapcraft/internal/remote_build/_launchpad.py#L426, the location of the i386 build log, and build complete. There is no snap.
I dropped architectures from snapcraft.yaml and changed to using --build-on https://github.com/sirredbeard/nim_lang_snap/commit/81cfca0edc2e7ab96e821311d352fcd19ac9f86b and it seemed to build all the architectures.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Abandoned without a code fix. The remote-build command misinterpreted the architectures keyword, only processing i386 and failing. A CLI workaround using --build-on is recommended instead. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed with a workaround. The architectures keyword in snapcraft.yaml incorrectly restricted remote builds to i386. Use the --build-on CLI flag instead to build multiple architectures. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without an official fix. The snapcraft remote-build command ignored the architectures directive in snapcraft.yaml, only building i386. The author resolved the issue by switching to the --build-on CLI flag instead. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4780 remote build: fails with some architecture definitions | snapcraft | closed | Remote build failures with specific architecture definitions or comma-separated --build-for flags were fixed via PR #4793 and craft-application#343. | |
| #4543 fix(remote): parse comma-separated architectures | snapcraft | merged | Merged after approval. Resolves #4516 by enforcing mutual exclusivity between --build-for and --build-on, and adding comma-separated architecture parsing for remote builds. Proceeded despite unrelated spread test failures. |