base core20: wrong arch triplet
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without a fix or resolution, likely abandoned due to inactivity. The report indicated Snapcraft incorrectly sets SNAPCRAFT_ARCH_TRIPLET when building on a mismatched host architecture. No comments or patches were submitted.
Suggested action: —
No scores available.
Issue body
Snapcraft sets the wrong arch triplet when only a single target is supported, but building on a different target
snapcraft: 7.2.8
e.g.
architectures:
- build-on: [amd64, arm64, armhf]
run-on: armhf
test snap
https://paste.ubuntu.com/p/MNJnf3qvmX/
Actual SNAPCRAFT_ARCH_TRIPLET in the created snap is whatever host arch triplet is
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without a fix or resolution, likely abandoned due to inactivity. The report indicated Snapcraft incorrectly sets SNAPCRAFT_ARCH_TRIPLET when building on a mismatched host architecture. No comments or patches were submitted. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without comments or resolution, likely abandoned. The report detailed Snapcraft incorrectly setting SNAPCRAFT_ARCH_TRIPLET during cross-architecture builds. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Snapcraft incorrectly set SNAPCRAFT_ARCH_TRIPLET based on the host architecture rather than the target. The report appears abandoned or superseded by the craft project, indicated by the craft-1498 label. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned. Closed without comments or resolution. SNAPCRAFT_ARCH_TRIPLET incorrectly matched the host architecture instead of the target during cross-arch builds. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1973376 SNAPCRAFT_ARCH_TRIPLET not usable with core22 base | snapcraft (launchpad) | closed | Closed without resolution. The report details a core22 build failure where snapcraft rejects SNAPCRAFT_ARCH_TRIPLET in layout mount points during packing. Core20 remains compatible. | |
| #1943603 snapcraft --target-arch=i386 does not build i386 images, because core20 does not support i386 and yet the build starts and wastes time | snapcraft (launchpad) | open | Reports that snapcraft --target-arch=i386 on a core20 base silently builds an amd64 snap instead of failing early, wasting build time. Unlabelled, 0 comments, inactive ~5 years; a related core20/i386 bug was closed as superseded by improved arch parsing. | |
| #1862256 snapcraft should complain loudly when building base: core20 snap on i386 | snapcraft (launchpad) | closed | Closed as superseded. Improved architecture parsing in snapcraft now correctly rejects unsupported base-architecture combinations, addressing the original request without requiring explicit i386 core20 checks. | |
| #4697 The partial organize operations of parts are missing | snapcraft | open | Core20 cross-arch build: organize with ${SNAPCRAFT_ARCH_TRIPLET} misses files without --target-arch flag. Maintainer asked in Jan 2026 if still reproducible in Snapcraft 8; no response. Core20 has since been dropped. | |
| #1674828 SNAPCRAFT_SETUP_CORE=1 doesn't work for foreign architectures | snapcraft (launchpad) | closed | SNAPCRAFT_SETUP_CORE=1 failing for foreign architectures during classic snap builds was closed without resolution. Zero comments and no fixes indicate the report was abandoned due to inactivity. | |
| #4486 $CRAFT_ARCH_TRIPLET_BUILD_FOR doesn't work on core22 | snapcraft | closed | Resolved. The $CRAFT_ARCH_TRIPLET_BUILD_FOR substitution failure in core22 environment blocks was fixed in snapcraft 8. A maintainer confirmed the fix with a working test case demonstrating correct variable replacement. | |
| #4770 Wrong arch being used in core24 project variables | snapcraft | closed | The CRAFT_ARCH_TRIPLET_BUILD_FOR variable incorrectly used the host architecture instead of the target when using --build-for on core24. The bug was resolved and merged via pull request #4779. | |
| #1817288 snapcraft cleanbuild produces incorrect architecture snap | snapcraft (launchpad) | closed | Abandoned and closed without resolution. The legacy mode cleanbuild multi-arch naming bug remains unfixed due to lack of activity and deprecation of legacy mode. | |
| #1999580 core22: wrong arch in snap.yaml when building for all archs | snapcraft (launchpad) | closed | Abandoned. Reported incorrect architecture mapping in core22 snap.yaml for architecture-independent snaps, where build-for all incorrectly set the architecture to amd64. | |
| #2009520 core18/20: inconsistent architecture parsing | snapcraft (launchpad) | closed | Abandoned. The reported YAML architecture parsing inconsistency in snapcraft was closed without resolution or fix. |