Package Details: snapd 2.67-2

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: 222
Popularity: 4.07
First Submitted: 2018-01-07 17:37 (UTC)
Last Updated: 2025-01-24 11:51 (UTC)

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:

  • 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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 25 Next › Last »

NatrixNatrix commented on 2024-05-09 13:33 (UTC)

I am getting the following error when building:

 ❯ LC_ALL=C makepkg -f
==> Making package: snapd 2.62-2 (Thu May  9 15:28:42 2024)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found snapd-2.62.tar.xz
==> Validating source files with sha256sums...
    snapd-2.62.tar.xz ... Passed
==> Extracting sources...
  -> Extracting snapd-2.62.tar.xz with bsdtar
==> Starting prepare()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
*** Setting version to '2.62-2' from user.
# github.com/snapcore/snapd/cmd/snap-seccomp
In file included from /usr/include/xfs/xfs.h:9,
                 from /usr/include/xfs/xqm.h:9,
                 from cmd/snap-seccomp/main.go:56:
/usr/include/xfs/linux.h: In function 'platform_zero_range':
/usr/include/xfs/linux.h:186:15: error: implicit declaration of function 'fallocate'; did you mean 'alloca'? [-Wimplicit-function-declaration]
  186 |         ret = fallocate(fd, FALLOC_FL_ZERO_RANGE, start, len);
      |               ^~~~~~~~~
      |               alloca
==> ERROR: A failure occurred in build().
    Aborting...

Presumably because of a missing _GNU_SOURCE somewhere. One workaround is to define it in the CFLAGS. I e makeprg CLFAGS+=" -D_GNU_SOURCE".

Which works but does lead to several 'redefinition' warnings during the build.

bboozzoo commented on 2024-04-29 06:44 (UTC)

@frozen good point, I've pushed an update. Although I do really recommend replicating the process of how main repos packages are build (even though nobody really cares or does so).

frozen commented on 2024-04-28 14:39 (UTC) (edited on 2024-04-28 14:39 (UTC) by frozen)

It seems the package fails to build with error

build flag -mod=vendor only valid when using modules

if you have the environment variable GO111MODULE=off or if it is unset, to get it to build you have to set GO111MODULE=on in the env before makepkg.

Could this perhaps be set inside the build function?

Ken commented on 2024-02-16 15:15 (UTC) (edited on 2024-02-17 12:21 (UTC) by Ken)

I also got this error on build:

==> Lancement de check()…
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

Did anyone manage to find a solution ?

EDIT: removing core/gcc-go and replacing with extra/go made it work !

Maxr commented on 2024-02-12 18:24 (UTC)

@bboozzoo Thank you very much, I should have stumbled upon that on myself, kinda embarrassing. Works.

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 :(

« First ‹ Previous 1 2 3 4 5 6 7 .. 25 Next › Last »