Package Details: snapd 2.75.2-1

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)
Last Packager: bboozzoo
Votes: 231
Popularity: 3.42
First Submitted: 2018-01-07 17:37 (UTC)
Last Updated: 2026-04-20 08:01 (UTC)

Pinned Comments

bboozzoo commented on 2018-10-25 11:56 (UTC) (edited on 2025-07-10 11:42 (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:

  • Reload the profiles: systemctl restart apparmor.service
  • Restart snapd: systemctl restart snapd.service
  • Load profiles for snaps: systemctl enable --now snapd.apparmor.service
2.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

2.70

Snapd 2.70 drops setuid permissions on /usr/lib/snapd/snap-confine in favor of explicit file capabilities. After an upgrade to 2.70, the users are prompted to restart the apparmor.service otherwise attempts to run snaps will error with cannot set capabilities message.

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 28 Next › Last »

bboozzoo commented on 2021-07-30 09:59 (UTC)

@abhaypatil2000 please follow the AUR getting started steps: https://wiki.archlinux.org/title/Arch_User_Repository#Getting_started

abhaypatil2000 commented on 2021-07-29 20:29 (UTC) 

Starting prepare()...
  -> applying 0001-snap-squashfs-handle-squashfs-tools-4.5.patch
/home/abhay/aur/snapd/PKGBUILD: line 50: patch: command not found
==> ERROR: A failure occurred in prepare().
    Aborting...

I am getting this error. Any idea how to solve it? I have tried to delete the repo and reclone it. Still the same error.

Hyllios commented on 2021-07-26 03:06 (UTC)

This is flagged as out of date, however the fix is very simple.

Update the following lines

pkgver=2.51.3
...
sha256sums=('67d3701b52484d7dba9c7b122752429eafbb20a0182966dd44ab1b1f6c1b780e')

bboozzoo commented on 2021-06-11 05:21 (UTC)

@bendavis78 builds fine in clean chroot, suggesting something in your system is most likely responsible for the problem. My rough guess is there's some tweaks in makepkg.conf that confuse the go link too.

The procedure is described in archwiki and has been linked to here many times. eg here: https://aur.archlinux.org/packages/snapd/#comment-810009

bendavis78 commented on 2021-06-10 20:12 (UTC)

I'm getting this error when using makepkg:

==> Starting check()...
snap-exec is not a static binary

bboozzoo commented on 2021-05-28 16:49 (UTC)

@TheCultLeader666 try building in a clean chroot then: https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot#Classic_way

TheCultLeader666 commented on 2021-05-28 15:28 (UTC)

@bboozzoo I have the base-devel group installed, still getting the error

bboozzoo commented on 2021-05-28 15:25 (UTC)

@TheCultLeader666 make sure to have base-devel group installed.

TheCultLeader666 commented on 2021-05-28 15:22 (UTC) (edited on 2021-05-28 15:22 (UTC) by TheCultLeader666)

I'm getting this error when installing, I've tried reinstalling gcc:

cgo: exec gcc-5: exec: "gcc-5": executable file not found in $PATH
==> ERROR: A failure occurred in build().
    Aborting...
error making: snapd

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 28 Next › Last »