← Back to issue list

core22: Only amd64 snap is built when multiple architectures are specified

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#2007790
Type
issue
State
open
Author
~brlin
Labels
Created
Updated
Closed

Current evaluation

Untriaged report that specifying multiple architectures in snapcraft.yaml only triggers amd64 builds in the Snapcraft build service.

Suggested action: needs triage

Reason: The issue has no labels, comments, or maintainer engagement after ~3.5 years, indicating it has not been triaged. It clearly describes a multi-architecture build failure, but requires maintainer assessment to verify if it's still reproducible on current bases or has been addressed elsewhere.

Impact: 50 Quick Win: 30.0 Staleness: 85 Complexity: 40 Confidence: 60 Support Request: 10

Issue body

Either the following configurations: ``` architectures: - build-on: amd64 build-for: amd64 - build-on: arm64 build-for: arm64 - build-on: armhf build-for: armhf - build-on: ppc64el build-for: ppc64el ``` ``` architectures: - amd64 - arm64 - armhf - ppc64el ``` will only trigger the amd64 build in the Snapcraft build service, recipes for reference: * https://github.com/brlin-tw/ffmpeg-cat/commit/36d166462e58d6fbc69fef33495ef606a617bdbe * https://github.com/brlin-tw/ffmpeg-cat/commit/c1468f6d1d2c132e0d36e1d11e5330e429450a85

Evaluation history

Date Model Scores Action Summary
qwen3.6-35b-a3b-mtp-q6
Impact: 50
Quick Win: 30.0
Staleness: 85
Complexity: 40
Confidence: 60
Support Request: 10
needs triage Untriaged report that specifying multiple architectures in snapcraft.yaml only triggers amd64 builds in the Snapcraft build service.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 40
Confidence: 85
Support Request: 15
close stale Specifying multiple architectures in snapcraft.yaml only triggers amd64 builds in the Snapcraft build service. Untriaged, no maintainer comments, inactive for over three years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 40
Confidence: 90
Support Request: 5
close stale Multi-architecture snap builds only trigger amd64 in the Snapcraft build service when using core22. Reported 3+ years ago with zero maintainer interaction or follow-up.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 40
Confidence: 85
Support Request: 10
close stale Multi-arch snap builds only produce amd64 when multiple architectures are specified in snapcraft.yaml. Issue is 3+ years old, has no maintainer comments, and references the deprecated core22 base.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 45
Confidence: 85
Support Request: 15
close stale Reports that specifying multiple architectures in snapcraft.yaml only triggers amd64 builds in the Snapcraft build service. No maintainer response or labels for over three years.

Update history

No update history recorded yet.

Related work

  • Duplicate Of: canonical/snapcraft#1999580 (confidence 60%)

    Launchpad issue #1999580 reports a similar core22 multi-architecture snap.yaml issue, suggesting this may be a duplicate or related upstream bug.

Related issues

Issue Project State Summary Similarity
#1999580 core22: wrong arch in snap.yaml when building for all archs snapcraft (launchpad) closed Abandoned. Reported incorrect architecture mapping in core22 snap.yaml for architecture-independent snaps, where build-for all incorrectly set the architecture to amd64.
74%
#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 Reports that snapcraft --target-arch=i386 on a core20 base silently builds an amd64 snap instead of failing early, wasting build time. Unlabelled, 0 comments, inactive ~5 years; a related core20/i386 bug was closed as superseded by improved arch parsing.
73%
#1737532 "snapcraft cleanbuild --target-arch=i386" produces amd64 executables snapcraft (launchpad) closed Closed without resolution. Cross-compilation for i386 via snapcraft cleanbuild continued producing amd64 binaries due to an incorrect container architecture and missing cross-compiler configuration.
70%