| Git Clone URL: | https://aur.archlinux.org/snapd.git (read-only, click to copy) |
|---|---|
| Package Base: | snapd |
| Description: | Service and tools for management of snap packages. |
| Upstream URL: | https://github.com/snapcore/snapd |
| Licenses: | GPL3 |
| Conflicts: | snap-confine |
| Submitter: | Barthalion |
| Maintainer: | bboozzoo (zyga, mardy) |
| Last Packager: | bboozzoo |
| Votes: | 217 |
| Popularity: | 4.47 |
| First Submitted: | 2018-01-07 17:37 (UTC) |
| Last Updated: | 2024-11-13 08:24 (UTC) |
Tried to update the package, I ran into file conflicts with: /usr/bin/ubuntu-core-launcher, /usr/lib/snapd/snap-confine, /usr/lib/snapd/snap-discard-ns, /usr/lib/snapd/system-shutdown, /usr/lib/udev/snappy-app-dev and /usr/share/man/man5/snap-discard-ns.5.gz
Tried to uninstall and install back. Compilation stops at: /tmp/pamac-build-user/snapd/PKGBUILD: line 132: snap : command not found
Thanks for the effort.
I tried installing this on a clean system and ran into some problem with package() failing in this line:
# Install man file snap help --man > "$pkgdir/usr/share/man/man1/snap.1"
I reviewed the PKGBUILD and there's some issues that may need addressing:
snap-mgmt is provided by data/snap-mgmt, no need to pull in the one from fedore packaging
we probably would want --enable-nvidia-biarch
better set all possible configuration variables when doing make -C
"$srcdir/$pkgname/data"
quite a few of snappy core specific files can be removed in install()
please make sure that /var/lib/snapd/snap existst when symlinking
/snap, it's actually created as a side effect of this install -dm755
"$pkgdir/var/lib/snapd/snap/bin but it's better to be explicit
IMO we still should display the message about the need to enable snapd.socket (probably even add a note about needing to do systemctl daemon-reload)
Let me know if you need any help, it'd be great to keep snapd and snapd-git in sync and working mostly out of the box.
edit: formatting
Pinned Comments
bboozzoo commented on 2018-10-25 11:56 (UTC) (edited on 2024-04-09 07:39 (UTC) by bboozzoo)
Package update notes
2.36
2.36 is the first release with AppArmor enabled by default on Arch.
If you do not have AppArmor enabled at boot there should be no functional changes visible.
If you wish to use snaps with Apparmor, first make sure that Apparmor is enabled during boot, see https://wiki.archlinux.org/index.php/AppArmor for details. After upgrading the package, you need to do the following steps:
systemctl restart apparmor.servicesnapd:systemctl restart snapd.servicesystemctl enable --now snapd.apparmor.service2.62
Since 2.62 snapd generated additional files describing the sandbox. The snapd service needs to be restarted after the update for snaps to continue working (unless the system is rebooted after the update, in which case no additional steps are needed). To restart, run
systemctl restart snapd.service