snap install --revision tracks stable by default
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
When I specifically install a revision for testing I would like to keep that revision until I want to switch it. I can't pin to that revision as the next refresh will pull from stable.
Example:
$ snap install etcd --revision=48
$ snap info etcd
name: etcd
summary: "Resilient key-value store by CoreOS"
publisher: canonical
contact: <email address hidden>
description: |
Etcd is a high availability key-value store, implementing the RAFT
algorithm to deal with failover within the etcd cluster. Popular
in the Docker community as a shared store of small but important
data in a distributed application.
commands:
- etcd.etcdctl (etcdctl)
tracking: stable
installed: 3.1+master (48) 10MB -
refreshed: 2017-04-01 13:54:44 -0500 CDT
channels:
stable: 3.1.3 (41) 7MB -
candidate: 3.1.5 (46) 7MB -
beta: 3.1.5 (46) 7MB -
edge: 3.1+master (48) 10MB -
Where it shows "tracking: stable" I specifically do not want to track stable at all, and on a snap refresh it will go to the latest stable without intervention. This is not what I would expect.
Is there a way to pin without refreshing from a channel? (I would expect revision to do this if no channel is given on the commandline).
| Zygmunt Krynicki (zyga) wrote | #1 |
| affects: | snappy → snapd |
| Changed in snapd: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Andrew Scribner (ca-scribner) wrote | #2 |
I don't believe there is a way to do what you want right now. There's no way to not follow any channel or any track in the store.
I'm marking this as confirmed / medium for further analysis in another pass.