snapcraft cleanbuild produces incorrect architecture snap
Metadata
Current evaluation
Bug (legacy cleanbuild naming a snap _multi.snap despite correct advanced architectures) was never fixed; closed in Aug 2023 by ~sergiusens noting cleanbuild is no longer supported and all builds are now transparently clean.
Resolution: closed stale
Reason: The affected code path was decommissioned: maintainer comment from ~sergiusens (2023-08-17) states cleanbuild is no longer supported as all builds transparently cleanbuild, and legacy commands were removed in snapcraft PR #6035 (commit 3623601d7). No code change addressed the multi-arch filename bug.
Evaluated by: mr-cal-bot
No scores available.
Issue body
When using the stable release of the snapcraft snap, if one uses the advanced architectures yaml like:
```
architectures:
- build-on: amd64
run-on: amd64
- build-on: armhf
run-on: armhf
```
and without a base specified so snapcraft operates in legacy mode, then snapcraft cleanbuild will produce a "multi" file snap name like "snap-name_0.1_multi.snap", even though the snap.yaml in the snap itself has the correct architecture specification.
This can be reproduced on amd64 with snapcraft stable snap (revision 2496), and a basic snap without `base` and with the above architectures snippet and specificaly using snapcraft cleanbuild
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Bug (legacy cleanbuild naming a snap _multi.snap despite correct advanced architectures) was never fixed; closed in Aug 2023 by ~sergiusens noting cleanbuild is no longer supported and all builds are now transparently clean. | |
| stealth/space-bunny-alpha | — | closed stale | Legacy cleanbuild naming was left unfixed; maintainers closed the report in 2023 because builds are now clean by default. | |
| stealth/space-bunny-alpha | — | closed stale | The bug report for legacy `cleanbuild` naming was abandoned after inactivity; legacy mode and `cleanbuild` were later deprecated and removed. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned due to inactivity. The legacy mode and cleanbuild feature were later deprecated and removed in snapcraft, superseding this issue. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned and closed without resolution. The legacy mode cleanbuild multi-arch naming bug remains unfixed due to lack of activity and deprecation of legacy mode. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned and closed without comments or resolution. The reported defect caused snapcraft cleanbuild to produce incorrect multi-architecture snaps in legacy mode. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The cleanbuild multi-architecture bug in legacy mode remains unfixed. No comments or patches were submitted. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Superseded By:
canonical/snapcraft#6035
(confidence 85%)
Merged PR removing deprecated snapcraft commands/options (3623601d7), eliminating cleanbuild entirely.
-
Duplicate Of:
snapcraft (launchpad)#1830371
(confidence 80%)
Other cleanbuild bug closed as obsolete for the same decommissioning reason.
-
Duplicate Of:
snapcraft (launchpad)#1800119
(confidence 70%)
'snapcraft cleanbuild' report closed as obsolete after cleanbuild was decommissioned.
-
Duplicate Of:
snapcraft (launchpad)#1800121
(confidence 65%)
'sudo snapcraft cleanbuild' closed as obsolete on the same grounds.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1697979 snapcraft fails on initial cleanbuild probe | snapcraft (launchpad) | closed | Closed as obsolete: cleanbuild was decommissioned, and standard Snapcraft builds now transparently use a clean build environment. | |
| #4214 snapcraft 7.4.3 doesn't adequately complain about non-existent architectures | snapcraft | closed | Fixed in Snapcraft 8: invalid build-on architectures now produce a clear validation error listing all supported architectures. | |
| #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. | |
| #2044389 snapcraft clean failed but exit 0 | snapcraft (launchpad) | open | Snapcraft 7.5.3 reports a missing build environment during clean but exits 0; a maintainer confirmed the bug and agreed it should fail, with no fix recorded. | |
| #1520248 snap with only scripts gets wrongs architecture set | snapcraft (launchpad) | closed | Script-only snap architecture handling was fixed by merged PR canonical/snapcraft#121 (merge 672bdedf4; implementation 4d4261135) and recorded for Snapcraft 0.6. | |
| #1862256 snapcraft should complain loudly when building base: core20 snap on i386 | snapcraft (launchpad) | closed | Closed as superseded: improved architecture parsing rejects unsupported core20/i386 builds, making a dedicated check unnecessary; snapcraft#4392 improved this handling. | |
| #1788654 snapcraft cleanbuild doesn't work with cross-compile stage-packages | snapcraft (launchpad) | closed | Closed as an obsolete legacy cleanbuild/LXD issue after a maintainer directed users to migrate to bases; no targeted cross-architecture fix was recorded. | |
| #1560481 snapcraft prints 'architectures' when trying to build a gadget snap | snapcraft (launchpad) | closed | Gadget-snap build support was added in commit 5610f0eaf (PR #886). | |
| #1800119 snapcraft cleanbuild | snapcraft (launchpad) | closed | The obsolete cleanbuild command was retired because builds became clean by default; a maintainer closed the report in August 2023. | |
| #1808800 snapcraft clean does not work inside snapcraft --debug | snapcraft (launchpad) | closed | The managed-host failure in snapcraft clean inside snapcraft --debug was already fixed in an earlier release; maintainer confirmation was added on 2020-08-24. |