It is not possible to install a build-snap with a closed risk
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
Triaged
|
High
|
Sergio Schvezov |
Bug Description
When trying to install a snap from a risk that is closed, the snap from the lower risk level that follows it will be installed.
For example, in:
$ snapcraft status u1test-
Track Arch Channel Version Revision
latest all stable latest-stable 2
test-track-1 all stable - -
If I run sudo snap install u1test-
However, when using build-snaps in snapcraft, if I specify:
build-snaps: [u1test-
I get:
Traceback (most recent call last):
File "/home/
exec(
File "/home/
obj=
File "/home/
return self.main(*args, **kwargs)
File "/home/
rv = self.invoke(ctx)
File "/home/
return Command.
File "/home/
return ctx.invoke(
File "/home/
return callback(*args, **kwargs)
File "/home/
return f(get_current_
File "/home/
ctx.
File "/home/
return self.invoke(cmd, **kwargs)
File "/home/
return callback(*args, **kwargs)
File "/home/
project_
File "/home/
execute(
File "/home/
repo.
File "/home/
snap_
File "/home/
if self.is_classic():
File "/home/
return store_channels[
KeyError: 'latest/candidate'
To reproduce, run the latest unreleased snapcraft with the snapcraft.yaml from http://
It works when an open channel is specified, like:
build-snaps: [u1test-
Changed in snapcraft: | |
importance: | Undecided → High |
assignee: | nobody → Sergio Schvezov (sergiusens) |
milestone: | none → 2.35 |
status: | New → Triaged |
Changed in snapcraft: | |
milestone: | 2.35 → none |