Architectures keyword incorrectly interpreted by remote-build
Metadata
Current evaluation
Remote-build treated the combined build-on list as alternatives; maintainers acknowledged an artifact-detection bug, but no fix or closing reference was recorded before #1870730 went stale.
Resolution: closed stale
Reason: Comments from April 2020 clarified the architecture semantics and acknowledged a remaining artifact bug, but linked no resolving PR or commit. The issue was closed roughly 26 days after its last activity, indicating inactivity rather than a documented fix.
Evaluated by: mr-cal-bot
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Remote-build treated the combined build-on list as alternatives; maintainers acknowledged an artifact-detection bug, but no fix or closing reference was recorded before #1870730 went stale. | |
| stealth/space-bunny-alpha | — | closed resolved | Remote-build clarified that one build-on list lets Launchpad choose one architecture; separate entries request all. PR #3021 fixed artifact rejection by removing the faulty sanity check. | |
| stealth/space-bunny-alpha | — | closed stale | Remote-build mishandled the YAML architectures list and produced no snap; using --build-on worked around the problem. No linked fix was found. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. The architectures keyword in snapcraft.yaml caused remote-build to only process i386. The author confirmed using the --build-on CLI flag successfully built all target architectures as a workaround. | |
| 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
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4495 remote build: odd errors for certain `architectures:` setups | snapcraft | closed | Remote-build architecture handling was improved; #4994 (5cd480725) fixed CLI validation and #5005 (ad3b54bbd) rejected unsupported duplicate build-on artifacts. | |
| #4995 remote build: error if multiple artefacts can be built on the same architecture | snapcraft | closed | Fixed by merged PR #5005 (commit ad3b54bbd): remote builds now fail early when multiple artifacts share a build-on architecture. | |
| #2042167 remote-build doesn't support shorthand architecture format | snapcraft (launchpad) | closed | Remote-build now handles shorthand architectures consistently; PR #4793 fixed the underlying bug in commit 53ec55cef. |