Ah ok, i was just having an update, it didn’t updated automatically. it only update when i refresh snap
Edited: I am not sure but its written on Arch Wiki
Configuration
The package ships several systemd unit files, which manage several tasks like automatically refreshing all installed snaps once a new version is released.
To launch the snapd daemon when snap tries to use it, start the snapd.socket and/or enable it to have it started at boot.
To start the timer which periodically refreshes snaps when a new version is pushed to the store use:
I just removed the upcoming marker. The arch package can be obtained from our releases page. Unfortunately the maintainer is not responding and we have little room to move right now. I’d like to split this off into a separate topic that involves:
updating installation instructions
working with the Arch community on a solution to inactive maintainer
Ah, sorry, I prepared .5 but somehow didn’t upload it. I will make that happen soon. ^H^H^H it is uploaded on the release page now.
As for your other question, that has some roadblocks still (/snap vs /var/lib/snapd/snap, nvidia handling in snap-confine, apparmor support). Out of that three apparmor support will soon be generalized (definitely in 2.29) so only the two will remain. The work on layouts may help in nvidia support. In addition someone may start a proper nvidia support initiative that would remove the biggest blocker but I haven’t heard anything about it.
Can I check in on the first issue? I’ve installed 2.27.5 on arch from the package downloaded from the releases page; it seems to work tolerably (e.g. I successfully installed hello-world and the core snap, and ran the former), but despite creating the /snap => /var/lib/snapd/snap symlink, attempting to snap install --classic ldc2 still leaves me with the message:
error: cannot install "ldc2": classic confinement is not yet supported on your
distribution
The community repo package is a bit outdated. Meanwhile, how about publishing snapd-stable and snapd-git package to AUR instead?
By convention, *-git packages usually build the latest master. The *-stable would follow the releases. Once the community repo package situation clears up we could align build files of AUR *-stable and the official one.
According to my knowledge, there was a limitation in snapd which causes snap to not updated through core, i think 2.29 will fix that issue so its can be update through snap!
Edited: One more limitation is Nvidia Binary Driver. i think that isn’t solved yet.
A little progress report. I have 2 PRs related to Arch. One https://github.com/snapcore/snapd/pull/4119 is already merged. The other https://github.com/snapcore/snapd/pull/4135 carries updates to unit tests and minor fixes to account control. There are some problems with spread tests at the moment (namely tests/main/static) but I hope we’ll be able to figure out a reasonable solution soon.
@Wimpress I wonder if there are news around Arch package issue. Is there anything we can do to improve the state of the community package? Can we start the unresponsive maintainer process now?
There may be other problems but one particular issue is that snap-confine still has two build-time choices: the layout of the /snap directory and the mode in which nvidia is handled. Both can be fixed but nobody is looking at that. If someone’s interested please contact the snapd team and I will happily guide them on the process.