snapcraft init missing a base
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without resolution. The base requirement for snapcraft init was later implemented in subsequent releases, superseding this report.
Suggested action: —
No scores available.
Issue body
snapcraft init needs to initialize with a base.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The base requirement for snapcraft init was later implemented in subsequent releases, superseding this report. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. Closed without comments or resolution, leaving the requirement for snapcraft init to specify a base unaddressed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without comments or linked pull request. No fix or merge details were recorded, indicating the issue was abandoned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1939713 snapcraft init create base: core18 snap | snapcraft (launchpad) | closed | Closed without direct resolution, likely abandoned due to inactivity. Subsequent Snapcraft releases updated the init default to core20 and core22, effectively resolving the reported behavior. | |
| #1604326 snapcraft init doesn't fail if there is a .snapcraft.yaml file | snapcraft (launchpad) | closed | Closed without resolution. The snapcraft init command remains unchanged and still creates snapcraft.yaml when .snapcraft.yaml exists, indicating the bug was abandoned or superseded by newer project changes. | |
| #1706564 Please allow the new "base" key in snapcraft.yaml | snapcraft (launchpad) | closed | The request to support the new base key in snapcraft.yaml was closed without implementation. With zero comments and no resolution details, the issue was abandoned or superseded by later updates. | |
| #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. | |
| #1835532 snapcraft behavior for type: base | snapcraft (launchpad) | closed | Closed without comments. The type: base and build-base configuration behavior was superseded by updated snapcraft core20 implementation. | |
| #81 snapcraft init with parts fails with required options | snapcraft | closed | Migrated to Launchpad bug tracker https://bugs.launchpad.net/snapcraft/+bug/1516775. Closed and superseded by upstream tracking due to the missing required options handling in snapcraft init. | |
| #1990550 snapcraft init creates boilerplate which opaquely fails to build by default | snapcraft (launchpad) | closed | Closed without resolution. The report recommended updating snapcraft init to default to core22 instead of core20, preventing opaque build failures and CLI mismatches. No fix or pull request was submitted, leaving the request abandoned. | |
| #1857019 cannot build snapd snap with build-base: core w/o base: core | snapcraft (launchpad) | closed | Closed without resolution or comments. The snapcraft TypeError when using build-base: core without base: core remains unresolved. | |
| #2103643 snapcraft whoami fails if run in a place with recipe using base: core | snapcraft (launchpad) | closed | Closed without resolution or fix. The snapcraft whoami command incorrectly parsed snapcraft.yaml and failed on outdated base: core configurations. The issue was abandoned after 513 days with no comments or patches. | |
| #6186 `snapcraft try` error is outdated | snapcraft | closed | Closed after assignment. Maintainer provided implementation guidance using get_effective_base() for dynamic base detection, with parametrized tests planned for core24 and core26. |