Comment 9 for bug 1594330

Note that this was reported at the same time we had operational issues in
the store that resulted in inconsistent results (e.g. the revision could've
flapped)

On 27 Jun 2016 07:15, "Michael Vogt" <email address hidden> wrote:

> Here is my theory what happend:
> """
> - user has rev 3 installed
> - store is modified (e.g. by the krita owner) to make rev 3 unavailable in
> the stable channel
> - on the next refresh snapd gets "2" as the latest snap in stable
> - snapd install "2" (because that is what the store told it)
> - store is modified again to make rev 3 available in stable again
> - on the next refresh snapd gets "3" again and tries to refresh to that
> - it fails because 3 is already installed, however it should not fail but
> instead just link rev 3 instead of rev 2.
> """
> once we implement the last step we also solve the issue when alternating
> between channels.
>
> --
> You received this bug notification because you are a member of Snappy
> Developers, which is subscribed to Snappy.
> https://bugs.launchpad.net/bugs/1594330
>
> Title:
> After a refresh doesn't use the right version of the snap
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/snappy/+bug/1594330/+subscriptions
>