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: 3.99
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 .. 8 9 10 11 12 13 14 15 16 17 18 .. 25 Next › Last »

henrylaxen commented on 2020-10-25 18:51 (UTC)

Thanks bboozzoo for the pointers. I got it to compile by changing:

CPPFLAGS="-D_FORTIFY_SOURCE=2"

to CPPFLAGS="-D_FORTIFY_SOURCE=2 -O2"

Best wishes, Henry Laxen

bboozzoo commented on 2020-10-25 18:16 (UTC)

@henrylaxen it builds fine in my system and in a clean chroot. Maybe you're setting something in your environment? The /etc/makepkg.conf file is owned by pacman, so maybe you can try reinstalling that to reset whatever modifications you have there.

If that doesn't help you can always try and debug the recipe, adding -x -v to go build commands will produce more useful output.

henrylaxen commented on 2020-10-25 17:34 (UTC)

I never changed them from the default. I think these are the ones you are looking for:

CPPFLAGS="-D_FORTIFY_SOURCE=2"
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt"
CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now"

If there are other flags, just let me know. Best wishes, Henry Laxen

bboozzoo commented on 2020-10-25 17:19 (UTC)

@henrylaxen what build flags are set in /etc/makepkg.conf?

henrylaxen commented on 2020-10-25 16:58 (UTC)

When trying to install, I get: In file included from /usr/include/bits/libc-header-start.h:33, from /usr/include/stdlib.h:25, from _cgo_export.c:3: /usr/include/features.h:397:4: error: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Werror=cpp] 397 | # warning _FORTIFY_SOURCE requires compiling with optimization (-O) | ^~~~~~~ cc1: all warnings being treated as errors ==> ERROR: A failure occurred in build(). Aborting...

Not sure how to proceed from here. Any pointers will be appreciated. Best wishes, Henry Laxen

MartinX3 commented on 2020-09-16 10:47 (UTC) (edited on 2020-09-16 10:47 (UTC) by MartinX3)

I'm getting a big, fat warning

==> WARNUNG: Verwende bestehenden $srcdir/ Baum
==> Beginne build()...
fatal: Kein Git-Repository (oder irgendein Elternverzeichnis bis zum Einhängepunkt /)
Stoppe bei Dateisystemgrenze (GIT_DISCOVERY_ACROSS_FILESYSTEM nicht gesetzt).
fatal: Kein Git-Repository (oder irgendein Elternverzeichnis bis zum Einhängepunkt /)
Stoppe bei Dateisystemgrenze (GIT_DISCOVERY_ACROSS_FILESYSTEM nicht gesetzt).
*** Setting version to '2.46.1-1' from user.

Ataraxy commented on 2020-09-11 01:22 (UTC)

I'm getting a build problem after removing .cache/yay/snapd:

configure: WARNING: "cannot find the valgrind tool, will not run unit tests through valgrind"
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
make: *** No rule to make target '"4"'.  Stop.
==> ERROR: A failure occurred in build().
    Aborting...
error making: snapd

bboozzoo commented on 2020-08-17 07:50 (UTC)

@dslink builds fine with 2.45.3.1-2 I pushed a week ago.

dslink commented on 2020-08-15 18:29 (UTC)

Wont build, even tried to build directly from offical git. This is the aur error snap-confine-private.a make[1]: Leaving directory '/tmp/trizen-***/snapd/src/snapd-2.45.3.1/cmd' ==> Starting check()... ==> ERROR: A failure occurred in check(). Aborting... :: Unable to build snapd - makepkg exited with code: 4

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 25 Next › Last »