Package Details: snapd 2.51.1-1

Git Clone URL: (read-only, click to copy)
Package Base: snapd
Description: Service and tools for management of snap packages.
Upstream URL:
Licenses: GPL3
Conflicts: snap-confine
Submitter: Barthalion
Maintainer: bboozzoo (zyga)
Last Packager: bboozzoo
Votes: 163
Popularity: 4.69
First Submitted: 2018-01-07 17:37
Last Updated: 2021-06-28 07:58

Pinned Comments

bboozzoo commented on 2018-10-25 11:56

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 for details. After upgrading the package, you need to do the following steps:

  • Reload the profiles: systemctl restart apparmor.service
  • Restart snapd: systemctl restart snapd.service
  • Load profiles for snaps: systemctl enable --now snapd.apparmor.service

Latest Comments

« First ‹ Previous ... 12 13 14 15 16 17

aimileus commented on 2018-01-11 08:43

The last update should fix "snap: command not found". It uses the snap binary from $GOPATH instead.

@maxlefou I also added snap-confine to the conflicts array, that should fix the file conflicts. I merged the snap-confine and snapd packages so that created some file conflicts.

@bboozzoo the snap-mngt isn't in cmd for the 2.30 tag, which this package builds form ( So for this release I used the Fedora packaging. Enabled --enable-nvidia-biarch Added the configuration options from snapd-git. Removed the snappy core files. I don't understand that one, I already added "install -dm755 "$pkgdir/var/lib/snapd/snap"? Most Arch packages don't display messages about required systemd units even if the packages are (almost) useless without the service e.g. networkmanager. So I prefer to use the Arch packaging way. Also, most snapd installation guides for Arch mention the unit anyway.

Aventura5 commented on 2018-01-09 21:36

Same here, "line 132: snap: command not found"

oryband commented on 2018-01-09 11:00

I also have the same compilation error as mentioned below: line 132: snap: command not found

maxlefou commented on 2018-01-09 08:22

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

bboozzoo commented on 2018-01-08 11:59

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