wrong architecture of stage-snaps when cross building
Metadata
Current evaluation
Cross-building with stage-snaps downloads the wrong architecture snap (tested on snapcraft 4.6). No comments, no activity for ~5 years, tracked under Jira label craft-415.
Suggested action: close stale
Reason: The issue was tested against snapcraft 4.6 (circa 2021) and has had zero comments or activity for ~5 years (last activity 1858 days ago). The tested version is long out of support and the cross-build architecture handling code has undergone significant refactoring in subsequent major releases. Without any maintainer acknowledgement or reproduction on a current version, the issue is no longer actionable in its original form.
Impact:
45
Quick Win:
20.25
Staleness:
92
Complexity:
55
Confidence:
55
Support Request:
5
Issue body
when using stage-snaps and building snap for different than native arch, wrong stage snap is downloaded.
There are two use cases this should be considered under:
- cross building with: --target-arch=<>
- cross building through architecture definition e.g.
architectures:
- build-on: amd64
run-on: arm64
Tested with snapcraft 4.6 rev 6281
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
45
Quick Win:
20.25
Staleness:
92
Complexity:
55
Confidence:
55
Support Request:
5
|
close stale | Cross-building with stage-snaps downloads the wrong architecture snap (tested on snapcraft 4.6). No comments, no activity for ~5 years, tracked under Jira label craft-415. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
50
Confidence:
85
Support Request:
10
|
close stale | Bug report from 5 years ago describing incorrect stage-snaps architecture selection during cross-compilation. No maintainer comments or activity since opening. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
65
Confidence:
85
Support Request:
10
|
close stale | Reports incorrect stage-snap architecture selection during cross-architecture builds using --target-arch or build-on/run-on definitions. Tested on snapcraft 4.6. No maintainer engagement or updates in over five years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
55
Confidence:
80
Support Request:
10
|
close stale | Reports incorrect architecture selection for stage-snaps during cross-compilation in snapcraft 4.6. Issue has been inactive for nearly 5 years with no maintainer response or updates. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
65
Confidence:
90
Support Request:
10
|
close stale | Reports incorrect stage-snap architecture selection during cross-architecture builds in snapcraft 4.6. No maintainer response or activity in nearly 5 years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2012503 wrong arch of stage packages | snapcraft (launchpad) | open | Snapcraft 7.3 picks host architecture for stage packages when cross-building (build-on amd64, build-for arm64). No maintainer response in 3.4 years. Nearly identical issue #5335 was closed as expected behavior requiring explicit :$CRAFT_ARCH_BUILD_FOR suffix on stage packages. | |
| #1655797 Set arch for stage packages | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft rejected architecture qualifiers in stage-packages, causing download failures. With zero comments and no fix, the report was abandoned. | |
| #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. | |
| #1885074 stage-packages behaviour inconsistent | snapcraft (launchpad) | open | Snapcraft 4.0.7: stage-packages with :arm64 suffix cross-compile fine but native arm64 build yields an empty snap. Reported ~6 years ago, no maintainer response, no labels, zero comments. | |
| #1520248 snap with only scripts gets wrongs architecture set | snapcraft (launchpad) | closed | Closed without comments or resolution. Snapcraft 0.5 incorrectly flagged script-only snaps as missing amd64 binaries. The issue was abandoned and likely resolved in later snapcraft versions. | |
| #2015091 snapcraft download debian package from incorrect arch | snapcraft (launchpad) | open | Cross-architecture gadget snap downloads wrong arch deb (amd64 instead of arm64). Issue is 1249 days old with no maintainer engagement, labels, or assignee. | |
| #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. | |
| #1560481 snapcraft prints 'architectures' when trying to build a gadget snap | snapcraft (launchpad) | closed | Closed without resolution. The report noted snapcraft printing 'architectures' during gadget snap builds but received no comments or follow-up. | |
| #1660302 foreign architecture builds doesn't work with classic snaps | snapcraft (launchpad) | open | Cross-arch builds (--target-arch) of classic snaps fail because the build environment lacks the core snap. Reported 2016 against snapcraft 2.x; 0 comments, no maintainer response; codebase since fully rewritten. | |
| #5843 Snapcraft uses the wrong project model for non-app snaps | snapcraft | closed | Closed without resolution. An internal Jira ticket (SNAPCRAFT-1252) was created to track incorrect project model assignment for non-app snaps, causing a build-for architecture error. No fix was implemented. |