Add support for epoch property
Bug #1583298 reported by
Kyle Fazzari
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
click-reviewers-tools (Ubuntu) |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
Xenial |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
Yakkety |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
snapd (Ubuntu) |
Fix Released
|
Wishlist
|
Kyle Fazzari | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Wishlist
|
Kyle Fazzari |
Bug Description
In order to support step upgrades, snaps need to be able to specify upgrade paths. The method decided upon to specify said upgrade paths is an optional "epoch" property. Valid values consist of positive integers and an asterisk (e.g. 1 is epoch 1, 1* is the upgrade path from 1 to 2, and 2 is epoch 2). If the epoch is not specified, it should implicitly be 0.
Example YAML:
name: foo
version: 1
description: foo
summary: foo
epoch: 1*
Note that the API for providing this to the store does not yet exist, so this bug only covers the parsing of this information from the `snap.yaml`.
description: | updated |
description: | updated |
Changed in snapd (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in snapd (Ubuntu Xenial): | |
status: | New → Fix Released |
Changed in snapd (Ubuntu Yakkety): | |
status: | Fix Committed → Fix Released |
Changed in snapd (Ubuntu): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Note that this is closely related to https:/ /bugs.launchpad .net/snapcraft/ +bug/1581113 for snapcraft. They're kept separate to make the SRUs easier to test.