Be informed before update

I understood that one of the purpose of snapcraft is to ensure that the system is up-to-date without requiring any user action. That’s fine. But I would like the user to be informed a few moment about the next update (and the possible reboot).

How can I achieve this?


1 Like

There’s never a reboot for snap refreshes, as far as I’m aware.

snapcraft is the tool to build snap packages … what keeps your snap packages up to date locally is snapd

and @Ads20000 is correct, until we start providing kernels or bootloaders as snap packages, there are no reboots necessary, snaps on desktop/server installs are happily getting along without them.

PS: i have adjusted the category of this thread to snapd …

Sorry for the misplaced category…

I have installed Ubuntu Core and after a few minutes, the system did reboot.

I thought it was related to snapd.

Yeah, Ubuntu Core actually uses snap packages for the kernel and the rootfs, so there you actually get reboots for these two snaps. but it tells you that it will reboot on the console 30 seconds before it does so, it also gives instructions how to stop the reboot process in case you still have files open in an editor etc.

You can also schedule updates in general so they do not come as a surprise:

1 Like

So I can imagine that a snap could read the list of the available updates every minute and warn the user before the scheduled window.
What is the best way to retrieve this update snap list?

You might have to write a script that does that. Set the refresh frequency to what you want it to be, then you’ll need to write a script that runs snap list then snap info foo on all of your snaps and analyses the difference between the installed revision and the revision in the channel that each app is tracking and then report all the differences. You’ll need to set the script to run before the snaps are scheduled to refresh. You’ll then probably have to hunt down the changelogs for each update online.

Is snapd-control interface required to perform such a task?

Technically yes, practically it means that you need a brand store since uploading snap packages using snapd-control to the global store is not permitted by policy.