Ok, so this is what this bug is about:
When setup-profile runs it does the following sequence of actions:
- disconnect the snap in question, remember the list of snaps that were
affected by this disconnect
- remove the snap from Repository (the one with the older Revision)
- add the snap to the repository (the one with the newer Revision)
- auto connect the new snap
- reload connections for the new snap
- setup the security of all affected snaps
The last step is where the bug shows up. The list of affected snaps is
remembered as a list of snap.Info objects. Those keep the old .Revision
around.
** Summary changed:
- Installing a new two times leaves it with profiles referring to older revision
+ setup-profile configures security based on snap.Info from DisconnectSnap,
which still sees older revision
** Changed in: snapd (Ubuntu)
Status: New => In Progress
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572463
Title:
setup-profile configures security based on snap.Info from
DisconnectSnap, which still sees older revision
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1572463/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
