snapcraft fails when specifying 'any' architecture in build packages
Metadata
Current evaluation
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.
Suggested action: —
No scores available.
Issue body
When specifying a build package like python:any, snapcraft fails with this error message:
Could not find a required package in 'build-packages': "The cache has no package named 'python:any'"
Steps to reproduce:
$ snapcraft init
edit my-part in snap/snapcraft.yaml to add:
build-packages: ['python:any']
$ snapcraft
I think we can just drop the 'any', to match the behaviour of apt.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. Snapcraft failed when build-packages specified the ':any' architecture suffix. The reporter suggested automatically stripping the suffix to match apt behavior. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The suggested workaround is to omit the :any suffix from build package names to match apt behavior. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. Snapcraft failed when using the :any architecture suffix in build-packages. No fix or pull request was submitted, and the report was abandoned after nine years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1560481 snapcraft prints 'architectures' when trying to build a gadget snap | snapcraft (launchpad) | closed | Closed without resolution. The report noted snapcraft printing 'architectures' during gadget snap builds but received no comments or follow-up. | |
| #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. | |
| #1570835 snapcraft 2.8 fails on s390x | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft 2.8 failed on s390x due to a missing architecture table entry, but no fix or follow-up was recorded. | |
| #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. | |
| #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. | |
| #4214 snapcraft 7.4.3 doesn't adequately complain about non-existent architectures | snapcraft | closed | 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. | |
| #1897337 snapcraft build <part> ignores the part | snapcraft (launchpad) | closed | The snapcraft build command ignoring specified parts was closed without a fix or resolution. No comments or patches were provided, indicating the report was abandoned without addressing the filtering behavior. | |
| #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. | |
| #2061603 snapcraft 8.1 core24 root build-packages with "on <arch>" fails | snapcraft (launchpad) | closed | The on <arch> syntax in root build-packages fails parsing in snapcraft 8.1/core24. Closed and abandoned without resolution. | |
| #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. |