Package Details: snapd 2.35.4-1

Git Clone URL: (read-only)
Package Base: snapd
Description: Service and tools for management of snap packages.
Upstream URL:
Licenses: GPL3
Conflicts: snap-confine
Submitter: Barthalion
Maintainer: aimileus (bboozzoo, zyga)
Last Packager: bboozzoo
Votes: 51
Popularity: 4.459281
First Submitted: 2018-01-07 17:37
Last Updated: 2018-10-08 07:35

Latest Comments

1 2 3 4 5 6 Next › Last »

bboozzoo commented on 2018-10-11 20:37

@beidl Yes. It's already enabled in snapd-git. With a PR that landed today, the generated security policy is not downgraded on Arch anymore so the AppArmor profiles for snaps are not more fine grained. All this will be part of the upcoming 2.36 release. I'm plan to enable AppArmor by default in snapd with the next update in a week or so.

beidl commented on 2018-10-11 19:52

With AppArmor enabled in kernel packages provided in the default repos what are the chances of enabling AppArmor support in the snapd PKGBUILD by default?

bboozzoo commented on 2018-09-14 06:19

@eschwartz thanks for the tip. I ended up adding a hook locally. Your aurpublish project looks like a very nice alternative, I think I'll start using it and migrate to the repo layout it expects.

eschwartz commented on 2018-09-14 01:04

There have never been any such checks, and if there were it would prevent many legitimate update situations. Or lead to a world where the pkgrel gets updated every time whitespace or quoting gets fixed in a PKGBUILD...

I'd suggest instead, using something like community/aurpublish which provides githooks to keep .SRCINFO up to date.

bboozzoo commented on 2018-09-12 07:27

@qKUqm3wtY4 should be fixed now. Sorry for that. AUR used to have checks that rejected git push when pkg* were changed but .SRCINFO was not updated. This does not seem to work anymore.

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.