Fail to fetch packages for non-host architecture
Metadata
Current evaluation
Cross-arch stage-packages fetch fails for ros-jazzy-ros-base:arm64. Maintainer and reporter traced it to ROS 2 repo deps marked Architecture: All, i.e. likely upstream, not snapcraft. Triaged as a question (SNAPCRAFT-1026) with no resolution since Apr 2025.
Suggested action: keep open
Reason: The issue is triaged: labelled 'Type: Question', acknowledged by mr-cal, who spot-checked the ROS 2 packages and found them all marked 'All' while the reporter then conceded 'I think the issue lies with the ROS2 package repo and not snapcraft'. An internal ticket SNAPCRAFT-1026 was created and mr-cal asked for a working comparison environment, but the reporter could not produce one and no maintainer conclusion was ever posted, so the residual question — whether craft-parts should handle architecture-independent (:all) dependencies during cross-arch fetching — remains unanswered. The reporting case is likely upstream, but the general cross-arch behaviour is a real, recurring class of problem, so the issue should stay open for a maintainer decision rather than be closed.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
8
Complexity:
50
Confidence:
66
Actionability:
50
|
keep open | Cross-arch stage-packages fetch fails for ros-jazzy-ros-base:arm64. Maintainer and reporter traced it to ROS 2 repo deps marked Architecture: All, i.e. likely upstream, not snapcraft. Triaged as a question (SNAPCRAFT-1026) with no resolution since Apr 2025. | |
| qwen/qwen3.6-35b-a3b |
Impact:
70
Quick Win:
20
Complexity:
65
Confidence:
75
Actionability:
80
|
keep open | Snapcraft fails to fetch cross-architecture stage-packages when dependencies include architecture-independent packages (:all). Maintainer identified root cause; issue is under investigation. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
12
Staleness:
55
Complexity:
70
Confidence:
55
Support Request:
30
|
keep open | Cross-compile (amd64 build-on, arm64 build-for) fails to fetch stage-packages with :arm64 suffix (e.g. ros-jazzy-ros-base) even though present in repo; maintainer reproduced apt unmet-deps on arch-All python deps; reporter suspects ROS2 repo, not snapcraft. Awaiting reporter's working dpkg repro. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
65
Confidence:
85
Support Request:
40
|
close stale | Snapcraft fails to fetch arm64 stage packages during amd64 builds. Maintainer requested a reproducible environment; reporter could not provide one and suspects upstream ROS2 repo. Inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
60
Confidence:
75
Support Request:
20
|
close stale | Snapcraft fails to fetch cross-architecture stage packages due to dependency resolution issues. Maintainer requested a reproducible environment, but the reporter could not provide one and suspects an upstream ROS2 repository problem. Issue has been inactive for over a year. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft (launchpad)#1827067
(confidence 72%)
Launchpad bug 'need a way to add foreign architecture to sources.list for build-packages/stage-packages' covers the same unresolved foreign-architecture package fetching problem, with a 2023 core22 reproducer still open.
-
Related To:
craft-parts#258
(confidence 65%)
Merged craft-parts change that made stage-packages fetch from the host architecture's repo; the relevant fetching logic (apt_cache._populate_stage_cache_dir, which only sets APT::Architecture and never adds the target arch as a foreign architecture) still lives in craft-parts, not this repo.
Related issues
No related issues found above the similarity threshold.