i386 arch not enabled on amd64 build systems
Metadata
Current evaluation
The i386-on-AMD64 limitation is implemented: current docs configure an i386 APT repository, and core24/core26 spread tests stage an i386 package in an AMD64 snap.
Suggested action: close resolved
Reason: Package-repository integration landed in commit 4104923f9 (PR #3649), and the current test-foreign-i386 fixture explicitly builds an AMD64 snap with an i386 apt repository and a stage-package qualified as i386. The documented configuration and spread coverage resolve the reported AMD64/i386 case.
Evaluated by: mr-cal-bot
Impact:
42
Quick Win:
25
Complexity:
35
Confidence:
95
Actionability:
92
Issue body
It's quite hard to build a snap which has build-packages or stage-packages which are not the current arch. For example a snap which needs an i386 package will fail to build being unable to find the package when run on amd64 build systems
Perhaps the necessary "dpkg --add-architecture i386 && apt update" could happen during the VM / container stand-up?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
25
Complexity:
35
Confidence:
95
Actionability:
92
|
close resolved | The i386-on-AMD64 limitation is implemented: current docs configure an i386 APT repository, and core24/core26 spread tests stage an i386 package in an AMD64 snap. | |
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
12
Complexity:
40
Confidence:
84
Actionability:
66
|
needs triage | Request to enable i386 build or stage packages on AMD64 hosts. Snapcraft now documents and tests related-architecture staging, but this unlabelled, unassessed request needs confirmation against the supported configuration. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
23
Staleness:
92
Complexity:
35
Confidence:
50
Support Request:
25
|
close stale | Feature request to enable i386 architecture on amd64 build systems so snaps requiring i386 build/stage packages can be built. Filed 7+ years ago with zero comments, no labels, and no maintainer interaction. The suggested mechanism (dpkg --add-architecture during VM/container stand-up) references a build system era that has since changed significantly. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
95
Support Request:
5
|
close stale | Feature request to enable i386 architecture on amd64 build systems for snap packaging. Issue is completely inactive for over 7 years with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
5
|
close stale | Feature request to enable i386 architecture on amd64 build systems for snap builds. Issue is completely inactive with no maintainer feedback for over 7 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | Request to enable i386 architecture support on amd64 build systems for snap builds. Unanswered and inactive for over 7 years. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1827067
(confidence 90%)
Addresses the same foreign-architecture dependency problem, but its unresolved arm64 Launchpad-chroot variant is distinct from the now-tested AMD64/i386 path.
Related issues
No related issues found above the similarity threshold.