snapcraft behavior for type: base

Bug #1835532 reported by Sergio Schvezov on 2019-07-05
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Undecided
Unassigned
Snapcraft
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

description: updated
Sergio Schvezov (sergiusens) wrote :
Changed in snapcraft:
importance: Undecided → Critical
status: New → In Progress
Dimitri John Ledkov (xnox) wrote :

well..... we'd want core20 to point at whatever "devel" currently points to. As in cosmic, disco, eoan, funky... and eventually park on funky.

description: updated
Dimitri John Ledkov (xnox) wrote :

I built the proposed build-base branch localy, and used it on the host only (inside multipass VM which did get launched, it was still using the edge channel)

And I can build core20 snap properly now!!!

Snapped core20_20_amd64.snap
Ship it!

Changed in snapcraft:
status: In Progress → Fix Committed
description: updated
Changed in snapcraft:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers