Comment 6 for bug 1723094

On 21 March 2018 at 22:23, Iain Lane <email address hidden> wrote:

> 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…
>
> The installer itself will run that?
>

Well
https://code.launchpad.net/~mwhudson/livecd-rootfs/live-server-set-refresh.hold/+merge/341801
is my not very elegant proposal so far

> I see from here
>
> https://forum.snapcraft.io/t/development-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?
>

I assume that it's 60 days since the seeding process (how would snapd know
how old the image is?). But I haven't checked.

>
> Probably easier if I just comment on that thread:
>
> https://forum.snapcraft.io/t/development-sprint-march-5th-2018/4345/35
>
> Cheers,
>
> --
> Iain Lane [ <email address hidden> ]
> Debian Developer [ <email address hidden> ]
> Ubuntu Developer [ <email address hidden> ]
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1723094
>
> Title:
> Live images should be able to turn off Snap updates
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/snapd/+bug/1723094/+subscriptions
>