stage-packages do not honor --target-arch
Metadata
Current evaluation
Cross-building stage-packages pulls host architecture packages instead of target architecture. Issue is 8.7 years old with no maintainer interaction or comments. Old cross-build mode deprecated in favor of core24/craft-parts architecture.
Suggested action: close stale
Reason: Issue is 8.7 years old with 0 comments and no maintainer interaction. The old cross-build mode (classic mode) has been deprecated in favor of the core24/craft-parts architecture which handles cross-building differently. Similar issues (1788654, 1817288) have been closed as abandoned, indicating the old cross-build mode is no longer maintained.
Impact:
30
Quick Win:
18.0
Staleness:
95
Complexity:
40
Confidence:
65
Support Request:
10
Issue body
Hi,
When cross-building, stage-packages are pulled for the host architecture instead of the target architecture.
Best,
- Loïc
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
18.0
Staleness:
95
Complexity:
40
Confidence:
65
Support Request:
10
|
close stale | Cross-building stage-packages pulls host architecture packages instead of target architecture. Issue is 8.7 years old with no maintainer interaction or comments. Old cross-build mode deprecated in favor of core24/craft-parts architecture. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Cross-building stage-packages pulls host architecture packages instead of target. Issue is over 8 years old with no maintainer interaction or comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
30
Confidence:
85
Support Request:
10
|
close stale | Cross-building pulls stage-packages for the host architecture instead of the target architecture. The report has no labels, zero comments, and has been inactive for over eight years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
10
|
close stale | Cross-building with stage-packages pulls host architecture packages instead of target architecture. Issue is completely inactive for over 8 years with no maintainer response or labels. | |
| qwen3.6-35b-moe-q4 |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
10
|
close stale | Cross-building stage-packages pulls host architecture packages instead of target architecture. Issue has been inactive for over 8 years with no maintainer comments or reproduction steps. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft#1788654
(confidence 70%)
Similar cross-compile stage-packages issue, closed as abandoned
-
Related To:
snapcraft#1817288
(confidence 60%)
Related cross-build architecture issue, closed as abandoned
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. | |
| #1686481 stage-packages does not handle unmet dependencies | snapcraft (launchpad) | closed | stage-packages ignored target architectures, downloading dependencies for the build host instead. Closed without comments or resolution after 288 days, effectively abandoned. | |
| #4542 When cross-compiling incorrect architecture `stage-packages` are fetched | snapcraft | closed | Closed without resolution. Internal ticket CRAFT-2620 tracks the bug where cross-compilation fetches host architecture stage-packages instead of the target. Manual repository configuration and explicit architecture variables work around it. | |
| #1767 stage-packages does not respect architectures | snapcraft | closed | Superseded by PR #1788, which addresses related functionality but does not fully resolve the architecture handling bug. The core issue remains unfixed and requires a dedicated follow-up report. |