Comment 4 for bug 1572463

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.