wrong arch of stage packages
Metadata
Current evaluation
Confirmed cross-build stage packages are fetched for amd64 instead of arm64; no fix or verification is recorded, so the valid cross-compilation bug remains open.
Suggested action: keep open
Reason: The reporter identified amd64 libcryptsetup12 in prime on an amd64 host, and a maintainer explicitly confirmed that Snapcraft does not consider the target architecture when fetching stage-packages. The YAML and Snapcraft version provide a solid reproducer; although current code passes project.get_build_for() into the lifecycle architecture, no linked resolving commit or verification is available to close the issue.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
64
Quick Win:
27
Complexity:
52
Confidence:
87
Actionability:
88
|
keep open | Confirmed cross-build stage packages are fetched for amd64 instead of arm64; no fix or verification is recorded, so the valid cross-compilation bug remains open. | |
| stealth/space-bunny-alpha |
Impact:
68
Quick Win:
35
Complexity:
45
Confidence:
96
Actionability:
93
|
keep open | Cross-building for arm64 on amd64 stages amd64 stage-packages instead of target packages. A maintainer reproduced the bug, and a newer report identifies host_arch being used instead of target_arch. | |
| qwen/qwen3.6-35b-a3b |
Impact:
10
Quick Win:
9
Complexity:
5
Confidence:
90
Actionability:
90
|
close not a bug | Cross-architecture stage packages use wrong arch; closed as expected behavior in #5335. Users must suffix packages with :$CRAFT_ARCH_BUILD_FOR for cross-compilation. | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
13
Staleness:
90
Complexity:
15
Confidence:
72
Support Request:
80
|
close not a bug | 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. | |
| qwen/qwen3.8-27b |
Impact:
55
Quick Win:
19
Staleness:
90
Complexity:
65
Confidence:
55
Support Request:
5
|
needs triage | Snapcraft 7.3 picks host architecture for stage packages during non-native builds (build-on amd64, build-for arm64), producing snaps with wrong-arch staged packages. Reported ~3.4 years ago, zero comments, no labels, no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
65
Confidence:
80
Support Request:
10
|
close stale | Bug report claiming Snapcraft incorrectly selects stage package architecture during cross-compilation. Untriaged, zero comments, and over three years old with no maintainer engagement. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
60
Confidence:
85
Support Request:
10
|
close stale | Snapcraft incorrectly selects host architecture for stage packages during cross-compilation builds. Reported against version 7.3 with no maintainer interaction or updates in over three years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
45
Confidence:
80
Support Request:
10
|
close stale | Snapcraft incorrectly selects host architecture for stage packages during cross-arch builds. Issue is over three years old with zero maintainer response or labels. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1655797
(confidence 86%)
That closed bug added support for architecture-qualified stage-package names, but does not document a fix for selecting packages using the build-for architecture.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2015091 snapcraft download debian package from incorrect arch | snapcraft (launchpad) | open | Cross-building for arm64 on amd64 resolved explicitly qualified bsdmainutils:arm64 to an amd64 package; the valid report remains untriaged and a similar bug is still open. |