snapcraft behavior for type: base
Bug #1835532 reported by
Sergio Schvezov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Colin Watson | ||
Snapcraft |
Fix Released
|
Critical
|
Unassigned |
Bug Description
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
Related branches
~cjwatson/launchpad:generalise-snap-build-base
Merged
into
launchpad:master
- Ioana Lasc (community): Approve
-
Diff: 113 lines (+45/-10)2 files modifiedlib/lp/snappy/model/snap.py (+16/-7)
lib/lp/snappy/tests/test_snap.py (+29/-3)
description: | updated |
description: | updated |
Changed in snapcraft: | |
status: | In Progress → Fix Committed |
description: | updated |
Changed in snapcraft: | |
status: | Fix Committed → Fix Released |
tags: | added: core20 |
tags: | added: lp-snappy |
Changed in launchpad: | |
assignee: | nobody → Colin Watson (cjwatson) |
importance: | Undecided → High |
status: | New → In Progress |
tags: | added: id-5eb135a5073c1f2bc8e43d9a |
Changed in launchpad: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
https:/ /bugs.launchpad .net/snapcraft/ +bug/1835532