On Wed, Mar 21, 2018 at 08:13:23AM -0000, Michael Hudson-Doyle wrote:
> For the record, the plan for the live server installer is to run “snap
> set core refresh.hold=$(date --date=now+60days --iso-8601=seconds)”
> fairly early on. If people leave their live sessions going for 60 days,
> so be it…
"At the refresh attempt, if inside a hold window, skip it as long as it
doesn’t go beyond the maximum number of days (60 days right now)
Must warn if requested hold cannot be respected due to maximum period"
It doesn't say what the maximum number of days is since - do you know?
If it it since the last refresh, is that the date that the image was
created? If so, what happens if your image is more than 60 days old? It
sounds to me like this spec won't let you hold refresh in that case.
Have you checked this?
On Wed, Mar 21, 2018 at 08:13:23AM -0000, Michael Hudson-Doyle wrote: seconds) ”
> For the record, the plan for the live server installer is to run “snap
> set core refresh.hold=$(date --date=now+60days --iso-8601=
> fairly early on. If people leave their live sessions going for 60 days,
> so be it…
The installer itself will run that?
I see from here
https:/ /forum. snapcraft. io/t/developmen t-sprint- march-5th- 2018/4345/ 11
"At the refresh attempt, if inside a hold window, skip it as long as it
doesn’t go beyond the maximum number of days (60 days right now)
Must warn if requested hold cannot be respected due to maximum period"
It doesn't say what the maximum number of days is since - do you know?
If it it since the last refresh, is that the date that the image was
created? If so, what happens if your image is more than 60 days old? It
sounds to me like this spec won't let you hold refresh in that case.
Have you checked this?
Probably easier if I just comment on that thread:
https:/ /forum. snapcraft. io/t/developmen t-sprint- march-5th- 2018/4345/ 35
Cheers,
--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]