Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665102
Title:
it is also the case that snap refresh --list does not show new updates
on the devmode snaps, which is consistent I suppose, but if it did show
them one could know to manually do the refresh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ha! Of course I only remember my side of the discussion :)
Gustavo, are you suggesting that the snap would be refreshed and STAY in
devmode? Or that it would switch to strict (remember the possiblity of
devmode), and go to devmode if a subsequent revision specified devmode,
with no prompt?
I
Thanks for the well thought out explanation.
I would proffer and alternative until either #1 or #2 can be decided
upon.
Refresh for all snaps that stay in the same confinement mode. I.e. one
--devmode snap to a more recent --devmode snap, which currently does not
happen.
I agree that upgrades
The current behavior was the precise outcome of a very long conversation
we (Mark and I) had in Heidelberg, about the subtle properties of such
updates. We agreed to block devmode => strict refreshes because we could
not get a clear agreement on what was the proper way to treat those
updates.
