snapcraft 7.4.3 doesn't adequately complain about non-existent architectures
Metadata
Current evaluation
Fixed in snapcraft 8. Validation now rejects unsupported architecture names and returns a clear error listing valid options, replacing the previous vague build plan mismatch warning.
Suggested action: —
No scores available.
Issue body
### Bug Description
If you specify a build-on architecture that does not even exist (like "gothic" or "baroque"), all snapcraft tells you is:
_"Could not make build plan: build-on architectures in snapcraft.yaml does not match host architecture (amd64)."_
Perhaps it could be more informative and let you know that there is no such architecture, and print a list of supported architectures.
### To Reproduce
Specify a non-existent architecture.
### Environment
Ubuntu 22.04.2 LTS
### snapcraft.yaml
```shell
architectures:
- build-on: gothic
```
### Relevant log output
```shell
Could not make build plan: build-on architectures in snapcraft.yaml does not match host architecture (amd64).
```
### Additional context
_No response_
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Fixed in snapcraft 8. Validation now rejects unsupported architecture names and returns a clear error listing valid options, replacing the previous vague build plan mismatch warning. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed in snapcraft 8. The tool now returns a clear error message for unsupported architectures, listing valid options instead of a vague build plan mismatch warning. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed in snapcraft 8. Architecture validation now rejects unsupported values and returns a specific error listing valid options, replacing the previous generic build plan mismatch warning. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed in snapcraft 8. Validation now returns clear error messages and lists supported architectures when an invalid build-on architecture is specified in snapcraft.yaml. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed in snapcraft 8. Validation now explicitly rejects unsupported architectures and returns a clear error message listing valid options, replacing the previous generic build plan mismatch warning. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5034 Snapcraft not verbose enough when missing architecture on plataforms | snapcraft | closed | Resolved by canonical/craft-application#437. Snapcraft now outputs a clear error message recommending users check the platforms declaration or build parameters when the execution environment lacks a matching architecture. | |
| #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. | |
| #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. | |
| #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. | |
| #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. |