Automatic refresh of private snaps

Thanks. I will try that out.

Will it log anything from which I know it actually tried the snap to update?

@tpatel snap changes will list it, yes.

@denis to answer your last question, if a collaborator installs a snap, and then is no longer a collaborator, they shouldn’t be able to refresh a private snap.

I need to discuss what the intended way for this to work is, as some things changed in how we handle this (which is why it broke). We are also obviously missing tests for this, which also needs addressing.

With systemctl list-timers, I see in snapd.refresh.timer getting executed without having etc/systemd/system/snapd.refresh.timer. Why is that not forcing private snap to refresh ? Is it because the root folder doesnot have .snap/ folder with login credential? Or is it something else?

snapd ships the timer in /lib/systemd/system; /etc/systemd/system is where I suggested you put the edited version, as it would then override the other without interfering with a packaging upgrade (also it’s writable on core).

The lack of credentials for root would break this, yes.

Does snap update when done manually by “snap refresh”, when it is private mode and confinement strict?

yes, but in 2.31 we are also fixing the automatic bit: