snapcraft 8.1 core24 root build-packages with "on <arch>" fails
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
The on <arch> syntax in root build-packages fails parsing in snapcraft 8.1/core24. Closed and abandoned without resolution.
Suggested action: —
No scores available.
Issue body
snapcraft 8.1
base: core24
Root build-packages definition with additional syntax "on <arch>" does not pass the parser test.
example:
build-packages:
- build-essential
- on amd64:
- gcc-aarch64-linux-gnu
- on arm64:
- gcc
This will throw error:
Bad snapcraft.yaml content:
- string type expected (in field 'parts.snapcraft/core.build-packages[1]')
- string type expected (in field 'parts.snapcraft/core.build-packages[2]')
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | The on <arch> syntax in root build-packages fails parsing in snapcraft 8.1/core24. Closed and abandoned without resolution. | |
| qwen/qwen3.6-35b-a3b | — | — | Arch-specific build-packages syntax triggers a parser error in snapcraft 8.1. Closed without resolution or comments, indicating the bug was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The parser rejected the on <arch> syntax in root build-packages for core24, throwing a type mismatch error. No comments or fixes were submitted, and the issue was closed as abandoned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #1817288 snapcraft cleanbuild produces incorrect architecture snap | snapcraft (launchpad) | closed | 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. | |
| #1835638 inconsistent to arch behaviour | snapcraft (launchpad) | open | Snapcraft 3.6 stage-packages with 'on <arch>'/'to <arch>' conditionals behave inconsistently: cross-compiling works but native builds fail to pull required packages, and adding 'else' under 'on amd64' mixes arch packages. No maintainer response in 7+ years. | |
| #1691569 snapcraft fails when specifying 'any' architecture in build packages | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft failed when build packages used the ':any' architecture suffix. The reporter suggested stripping the suffix to match apt behavior, but no fix or pull request was implemented. | |
| #1980536 snapcraft unusable on systems not using apt | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft retained hard apt dependencies, causing crashes on non-Debian systems like Arch Linux. The issue appears abandoned with no fix provided. | |
| #1866300 snapcraft fails to build core20 snap | snapcraft (launchpad) | closed | Closed without comments or resolution after 74 days. The core20 build failure involving multipass hangs and LXD tracebacks was abandoned. | |
| #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. |