@ogra this post is about snap refresh --list
listing packages that are already at their latest version (see: https://github.com/brave/brave-browser/issues/32869#issuecomment-1714485293). It’s not really specifically about Brave, it just happened to be one of those packages in this case.
Initially, I was not able to reproduce exactly what Nidal saw, but I just got the following:
% snap refresh --list
Name Version Rev Size Publisher Notes
brave 1.57.64 274 165MB brave✓ -
firefox 117.0.1-2 3131 248MB mozilla✓ -
WARNING: There is 1 new warning. See 'snap warnings'.
% snap refresh
All snaps up to date.
WARNING: There is 1 new warning. See 'snap warnings'.
% snap refresh --list
Name Version Rev Size Publisher Notes
brave 1.57.64 274 165MB brave✓ -
firefox 117.0.1-2 3131 248MB mozilla✓ -
WARNING: There is 1 new warning. See 'snap warnings'.
% snap refresh
All snaps up to date.
WARNING: There is 1 new warning. See 'snap warnings'.
% snap refresh brave
error: snap "brave" has "auto-refresh" change in progress
% snap refresh
All snaps up to date.
WARNING: There is 1 new warning. See 'snap warnings'.
% snap refresh firefox
snap "firefox" has no updates available
% snap refresh --list
All snaps up to date.
WARNING: There is 1 new warning. See 'snap warnings'.
% snap list|grep 'brave\|firefox'
brave 1.57.64 274 latest/stable brave** -
firefox 117.0.1-2 3131 latest/stable mozilla** -
%
This looks like a bug to me. snap refresh --list
shows packages at their latest versions/revisions as requiring a refresh, then snap refresh
says all snaps are up to date (which is true, but contradicts what snap refresh --list
says) and then snap refresh brave
says a refresh is already ongoing, but there’s nothing to refresh. And finally snap refresh --list
says there’s nothing to refresh, but all packages are at their initial versions/revisions which initially made it list those packages as requiring a refresh.