snapcraft behavior for type: base
Metadata
Current evaluation
Closed without comments. The type: base and build-base configuration behavior was superseded by updated snapcraft core20 implementation.
Suggested action: —
No scores available.
Issue body
When a snapcraft.yaml is found that has
type: base
the "name" set in snapcraft.yaml should be used to determine the what build environment should be setup, thus
name: core18
type: base
# base: not set
shall create an Ubuntu 18.04 based build environment.
For the cases where the base has not been bootstrapped, it shall be possible to set `build-base` to the name of a base to use in order to setup the build environment, thus, the following will fail due to there being no core20 build environment
name: core20
type: base
# base: not set
but,can work with (LP: #1819196)
name: core20
type: base
build-base: core18
# base: not set
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without comments. The type: base and build-base configuration behavior was superseded by updated snapcraft core20 implementation. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without comments or discussion. The proposed behavior for resolving build environments using type: base and build-base in snapcraft.yaml appears to have been superseded or implemented in a later release. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The issue defined expected snapcraft behavior for type: base and build-base configuration but received no comments or resolution. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without discussion or implementation. The proposed type: base build environment logic was abandoned or superseded by later snapcraft versions, with no fix or merge details recorded. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #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. | |
| #1803776 snapcraft init missing a base | snapcraft (launchpad) | closed | Closed without resolution. The base requirement for snapcraft init was later implemented in subsequent releases, superseding this report. | |
| #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. | |
| #4983 Install base snap if declared as `build-base` | snapcraft | closed | Closed as superseded. Base and build-base combination restrictions in #4878 render this enhancement moot. The author acknowledged the change and implemented a workaround. Implementation may be revisited for kernel snap interim base support. | |
| #2689 schema: build-base support for the snapd type | snapcraft | merged | Merged into master. Implements build-base keyword support for the snapd snap type, enabling its construction. Approved by reviewer, passed CI, and updated four files. | |
| #1839604 build-base seems broken | snapcraft (launchpad) | open | Seven-year-old question about snapcraft rejecting 'base: bare' with 'build-base: core18' via a confusing validation error. No maintainer response; validation was rewritten in snapcraft 8.x, where build-base is now required for bare bases, so the reported combination is now valid. |