I’m travelling and wanted to disable the next autorefresh to not use too much data on a limited data plan, #snappy recommended to use (not very user friendly and not documented in “snap refresh --help”)
$ sudo snap set core refresh.hold=2018-09-07T17:00:00Z
that seemed to have worked but the output of “$ snapd refresh --time” is a bit confusing, now it states
“$ snap refresh --time
…
hold: tomorrow at 19:00 CEST
next: today at 15:23 CEST”
I would expect “next” to be reflecting the delay due to “hold” but it’s not?
Thanks for this report. It is indeed confusing. Here is one approach to fix this https://github.com/snapcore/snapd/pull/5789 - in the presentation layer the code will simply skip “next” if hold is set and the next is before hold.
Thanks Samuele for the review. I commented in the PR as well and updated the code. I have no strong opinion if we do just remove next: or if we amend information like: next: 2018-09-07 18:45 (but held).