Package Details: snapd 2.42.2-1

Git Clone URL: https://aur.archlinux.org/snapd.git (read-only)
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: 100
Popularity: 3.48
First Submitted: 2018-01-07 17:37
Last Updated: 2019-11-25 10:30

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

Latest Comments

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

qKUqm3wtY4 commented on 2018-09-12 07:01

This package is broken:

:: snapd package(s) failed to install. :: ensure package version does not mismatch between .SRCINFO and PKGBUILD :: ensure package name has a VCS suffix if this is a devel package

mati865 commented on 2018-09-04 09:57

@bboozzoo it turned out to be unreproducible post-upgrade issue. Works fine now.

bboozzoo commented on 2018-09-03 09:38

@mati865 thanks for the report. It's a bug in snapd service files, classical distributions should not need to use snap-failure, yikes! I'll try to fix it upstream.

While at it, can you check the log to see why snapd may have failed? The failure helper is run only of the main service fails, so snapd must have exited unexpectedly. I'd be really interested in knowing what happened there.

mati865 commented on 2018-09-02 10:07

With the latest version I'm getting: snapd.failure.service: Failed at step EXEC spawning /usr/lib/snapd/snap-failure: No such file or directory. Probably snap-failure should be included in the package.

aimileus commented on 2018-08-17 06:51

Autoconf and automake are included in the base-devel group, which is supposed to be installed when building AUR packages.

jezeklu commented on 2018-08-17 06:45

Hello @bboozzoo, there are missing dependencies in makedepends array - autoconf and automake. Thanks for completion.

gee commented on 2018-08-03 13:08

Hello,

until snapd builds with flto would you mind adding fno-lto to the flags since you already use them?

Thanks!

JayGatsby commented on 2018-06-26 22:10

thank you bboozzoo: I tried fixing it and messed with a bunch of settings not sure my machine would be the best to try to debug from... ended up removing snapd for now. believe that it had something to do with a symlink but couldn't figure out what needed to be changed. Again, thanks!

bboozzoo commented on 2018-06-25 05:46

@JayGatsby what do you mean by snaps no longer opening? Are snaps no longer being mounted?

Can you report this on https://forum.snapcraft.io/ and upload journalctl and SNAP_DEBUG=1 SNAP_CONFINE_DEBUG=1 snap run hello-world logs?

JayGatsby commented on 2018-06-24 18:45

snaps no longer opening for me - Wonding if this is something others are experiencing or isolated to my machine.