← Back to issue list

snapcraft cleanbuild produces incorrect architecture snap

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1817288
Type
issue
State
closed
Author
~anonymouse67
Labels
Created
Updated
Closed

Current evaluation

⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.

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.

Suggested action:

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
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

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1788654 snapcraft cleanbuild doesn't work with cross-compile stage-packages snapcraft (launchpad) closed Closed without resolution. Snapcraft cleanbuild fails during cross-compilation because it does not automatically configure multi-arch package support inside the container. No fix was implemented, and the report appears abandoned.
79%
#1641123 snapcraft does not properly detect the architecture when kernel is 64 bits but userspace is 32 snapcraft (launchpad) closed Closed without resolution. Snapcraft incorrectly identified arm64 architecture in 64-bit kernel/32-bit userspace chroots, generating mismatched snaps. The report was abandoned due to inactivity.
75%
#1746359 snapcraft cleanbuild --debug should provide guidance on build failure snapcraft (launchpad) closed Closed as abandoned due to inactivity. The requested debug shell guidance for snapcraft cleanbuild was never implemented.
75%
#1520248 snap with only scripts gets wrongs architecture set snapcraft (launchpad) closed Closed without comments or resolution. Snapcraft 0.5 incorrectly flagged script-only snaps as missing amd64 binaries. The issue was abandoned and likely resolved in later snapcraft versions.
74%
#1570706 Snapcraft cleanbuild command doesn't work snapcraft (launchpad) closed Closed without resolution, likely abandoned or superseded. The cleanbuild command failed due to LXC hash format incompatibility and container stop errors.
74%
#1997752 base core20: wrong arch triplet snapcraft (launchpad) closed Closed without a fix or resolution, likely abandoned due to inactivity. The report indicated Snapcraft incorrectly sets SNAPCRAFT_ARCH_TRIPLET when building on a mismatched host architecture. No comments or patches were submitted.
74%
#1862256 snapcraft should complain loudly when building base: core20 snap on i386 snapcraft (launchpad) closed 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.
74%
#1921418 wrong architecture of stage-snaps when cross building snapcraft (launchpad) open Cross-building with stage-snaps downloads the wrong architecture snap (tested on snapcraft 4.6). No comments, no activity for ~5 years, tracked under Jira label craft-415.
74%
#1799925 snapcraft gives conflicting advice for cleaning parts snapcraft (launchpad) closed Closed without a fix. Snapcraft incorrectly advised running snapcraft clean with part and step flags, which were unsupported. The author worked around it with a full clean. The report appears abandoned or superseded by later updates.
74%
#1881515 Snapcraft pulling wrong arch of debs when building foreign snaps snapcraft (launchpad) open 2018 report: --target-arch=armhf on x86 pulls x86-64 stage-packages debs instead of armhf. No labels, comments, or maintainer response in 6+ years. Legacy --target-arch flag removed; modern cross-compile documents the :$CRAFT_ARCH_BUILD_FOR suffix requirement.
73%