[cross-compile] when a deb package that has a dependency to non-architecture deb package, snapcraft does not recognize that and throws a dependency error
Metadata
Current evaluation
Core22 cross-compilation can treat an architecture-independent dependency as target-specific; cross-architecture behavior was reproduced, but current core24 behavior remains unverified.
Suggested action: keep open
Reason: The report includes a precise failing project and logs, and a maintainer reproduced related cross-architecture behavior for armhf. Although Snapcraft 8.8 improved cross-compilation and now documents `$CRAFT_ARCH_BUILD_FOR`, the latest maintainer comment explicitly requests a core24 reproduction, so there is no evidence that the original architecture-independent dependency failure was fixed.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
14
Complexity:
48
Confidence:
84
Actionability:
63
|
keep open | Core22 cross-compilation can treat an architecture-independent dependency as target-specific; cross-architecture behavior was reproduced, but current core24 behavior remains unverified. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
5
Complexity:
60
Confidence:
65
Actionability:
40
|
keep open | Cross-compiling snap with architecture-specific deb packages fails when dependencies are architecture-independent (e.g. python3-serial). Issue labeled Needs information; maintainer asked reporter to test with core24/snapcraft 8.8+ but no response in 235 days. | |
| qwen/qwen3.8-27b |
Impact:
50
Quick Win:
15
Staleness:
55
Complexity:
70
Confidence:
60
Support Request:
20
|
keep open | Cross-compiling a core22 snap with an arch-pinned stage package (gpsd-clients:arm64) fails with 'unmet dependencies: python3-serial' because non-arch-specific deps aren't resolved for the target arch. Maintainer offered a workaround and asked if it reproduces on core24; no reply yet. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
40
Confidence:
75
Support Request:
30
|
close stale | Cross-compilation dependency resolution fails for non-arch-specific packages in Snapcraft. Issue is old, has a workaround, and may be resolved in newer versions. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
70
Confidence:
85
Support Request:
20
|
keep open | Cross-compiling snaps with architecture-specific packages fails due to unmet dependencies on non-arch packages. Labeled needs information; awaiting author's test results on core24/Snapcraft 8+. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#4542
(confidence 91%)
Covers cross-compilation fetching stage packages for the host architecture instead of the target architecture.
-
Related To:
canonical/snapcraft#5335
(confidence 89%)
Addresses target-architecture stage-package selection and documents explicit `$CRAFT_ARCH_BUILD_FOR` package naming.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1881515 Snapcraft pulling wrong arch of debs when building foreign snaps | snapcraft (launchpad) | closed | Reported --target-arch pulling wrong debs for foreign arch builds. Maintainers noted the feature was broken and disabled for core20. Marked resolved as cross-builds have been significantly improved in recent Snapcraft versions. |