snapcraft should complain loudly when building base: core20 snap on i386
Metadata
Current evaluation
Closed as superseded: improved architecture parsing rejects unsupported core20/i386 builds, making a dedicated check unnecessary; snapcraft#4392 improved this handling.
Resolution: closed superseded
Reason: Maintainer ~mr-cal closed the report because newer architecture parsing already handles unsupported base/architecture combinations. Commit 0330bc36e (snapcraft#4392) generalized unsupported-architecture handling, superseding the requested one-off check.
Evaluated by: mr-cal-bot
No scores available.
Issue body
There will not be a core20 base for i386 architecture, so if snapcraft detects that it is trying to build for that combination, it should complain loudly and clearly that this should not work.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Closed as superseded: improved architecture parsing rejects unsupported core20/i386 builds, making a dedicated check unnecessary; snapcraft#4392 improved this handling. | |
| stealth/space-bunny-alpha | — | closed superseded | Closed as superseded: newer architecture parsing rejects unsupported base/architecture combinations, removing the need for a dedicated core20-on-i386 check. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as superseded. Improved architecture parsing in snapcraft now correctly rejects unsupported base-architecture combinations, addressing the original request without requiring explicit i386 core20 checks. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. Improved architecture parsing in snapcraft now handles unsupported base-architecture combinations, resolving the request for explicit error messaging when building core20 snaps on i386. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
10
Confidence:
85
Support Request:
0
|
close stale | Request to add explicit validation in snapcraft when building with base: core20 on i386, as that combination is unsupported. Issue has been inactive for over 6 years with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
10
Confidence:
90
Support Request:
10
|
close stale | Request to add validation error when building core20 snaps on i386. Unlabelled, zero comments, inactive for over six years. The core20 base is deprecated, making this check obsolete. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
10
Confidence:
90
Support Request:
5
|
close stale | Request to add validation in snapcraft to fail with a clear error when building a snap with base: core20 for the i386 architecture, which lacks a core20 base. Issue is completely inactive with no maintainer response. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Superseded By:
snapcraft#4392
(confidence 78%)
Generalized unsupported-architecture handling likely made a dedicated core20/i386 check obsolete.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1943603 snapcraft --target-arch=i386 does not build i386 images, because core20 does not support i386 and yet the build starts and wastes time | snapcraft (launchpad) | open | Legacy Snapcraft accepted an unsupported core20/i386 target, wasted build time, and produced an amd64 snap; current validation excludes i386 and drops core20. | |
| #2009520 core18/20: inconsistent architecture parsing | snapcraft (launchpad) | closed | Superseded by snapcore/snapcraft#4340 and #4341. Core22+ overlapping build-on handling merged in #3821 (4876b53); core20 support was declined. | |
| #1835532 snapcraft behavior for type: base | snapcraft (launchpad) | closed | Implemented build-base support for base snaps; the proposed branch successfully built core20 using core18 before the issue was closed. | |
| #1866300 snapcraft fails to build core20 snap | snapcraft (launchpad) | closed | Closed without a documented fix after core20 Multipass/LXD failures; core20 build-base support was unavailable and the workaround was destructive mode. | |
| #1939713 snapcraft init create base: core18 snap | snapcraft (launchpad) | closed | Snapcraft init was updated to scaffold core20 instead of core18 by merged canonical/snapcraft#3587 (merge commit f91632aab). | |
| #2012074 snapcraft cannot build snap by default on aarch64 | snapcraft (launchpad) | open | ARM64 default builds failed on Snapcraft 7.3.1 because core20 selected amd64-only Multipass images; later defaults use core22/LXD on Linux, addressing the reported path. | |
| #2099923 Snapcraft builds are failing: install of snap "snapcraft" failed | snapcraft (launchpad) | open | Reported Launchpad Bionic non-i386 builds cannot install Snapcraft 7.x/stable because core20 needs snapd 2.61; the issue remains open, untriaged, and unanswered. | |
| #1992557 snapcraft remote-build snapcraft.yaml validation too strict | snapcraft (launchpad) | closed | Strict validation in snapcraft remote-build rejected empty LD_LIBRARY_PATH for core22 snaps. Resolved by the new remote builder, which fixes the legacy core18/20 implementation bug. | |
| #1641123 snapcraft does not properly detect the architecture when kernel is 64 bits but userspace is 32 | snapcraft (launchpad) | closed | Fixed in snapcore/snapcraft#1089 by deriving the build architecture from the compiler target, preventing 32-bit ARM artifacts from being mislabeled arm64. | |
| #1997752 base core20: wrong arch triplet | snapcraft (launchpad) | closed | Wrong SNAPCRAFT_ARCH_TRIPLET for core20 build-on/run-on builds fixed by adding SNAPCRAFT_ARCH_BUILD_ON/BUILD_FOR and *_TRIPLET_BUILD_FOR envvars (PR #4313, commit 93a9d8170); follow-up #4332 (48bd0632f) errors on unevaluable multi-arch cases. |