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 2 3 4 5 6 7 8 9 10 .. 28 Next › Last »

bboozzoo commented on 2024-02-12 08:17 (UTC)

@Maxr -D_FORTIFY_SOURCE is not being set in any part of the snapd tree. Are you sure you aren't setting -D_FORTIFY_SOURCE-.. in makepkg.conf more than once?

Maxr commented on 2024-02-10 16:32 (UTC) (edited on 2024-02-10 16:33 (UTC) by Maxr)

I get an error on building:

*** Setting version to '2.61.1-1' from user.
# runtime/cgo
<command-line>: error: "_FORTIFY_SOURCE" redefined [-Werror]
<command-line>: note: this is the location of the previous definition
cc1: all warnings being treated as errors

Any idea what's wrong? I can't find any solution so far.

alexdelorenzo commented on 2023-11-04 08:50 (UTC) (edited on 2023-11-09 06:56 (UTC) by alexdelorenzo)

Can't build 2.61:

if command -v shellcheck >/dev/null; then shellcheck snapd.run-from-snap snapd.core-fixup.sh; fi
snapd.run-from-snap: snapd.run-from-snap: openBinaryFile: does not exist (No such file or directory)
snapd.core-fixup.sh: snapd.core-fixup.sh: openBinaryFile: does not exist (No such file or directory)

edit: The fix involved removing firejail's /usr/local/bin/shellcheck wrapper

patlefort commented on 2023-10-31 19:32 (UTC)

Any reason for passing MAKEFLAGS variable manually? make will read it automatically. Arguments passed in MAKEFLAGS aren't always in the form of -<arg> so it might fail, like when using make job server.

RicardoPQ commented on 2023-10-25 13:23 (UTC) (edited on 2023-10-25 13:24 (UTC) by RicardoPQ)

Hi, when trying to update I get this message:

snap-exec is not a static binary
 -> error making: snapd-exit status 1
 -> Failed to install the following packages. Manual intervention is required:
snapd - exit status 1

And doesn't get updated :(

bboozzoo commented on 2023-10-20 19:08 (UTC)

@shastry thanks, I've pushed an update

shastry commented on 2023-10-20 18:31 (UTC)

The autoconf-archive package is needed (makedeps) to build this.

Else you get an error like:

configure.ac:42: the top level
configure.ac:277: error: possibly undefined macro: dnl
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoreconf: error: /usr/bin/autoconf failed with exit status: 1
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: snapd-exit status 4

arnaudlecam commented on 2023-09-29 12:41 (UTC)

Could you please add automake to PKBUILD's makedeps ?

bboozzoo commented on 2023-06-22 07:43 (UTC)

FYI, AppAmor 3.1.6 was just released with a fix for the regression introduced in 3.1.5, https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.1.6

InspectrClouseau commented on 2023-06-17 16:08 (UTC) (edited on 2023-06-17 16:12 (UTC) by InspectrClouseau)

Tblue: I see, thank you for opening the bug report. I was doubting myself since on a different computer it does work. The regressions must have been introduced after apparmor 3.1.4-1. The later version is installed on a different computer and still works fine!

Edit: I downgraded to 3.1.4-1 on this machine as well and was able to install without issues. Maybe this information is useful to your bug report.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 28 Next › Last »