Package Details: snapd-git 2.42.r264.gf0a24204a4-1

Git Clone URL: (read-only)
Package Base: snapd-git
Description: Service and tools for management of snap packages.
Upstream URL:
Licenses: GPL3
Conflicts: snap-confine, snapd
Provides: snapd
Submitter: bboozzoo
Maintainer: bboozzoo (aimileus, zyga)
Last Packager: bboozzoo
Votes: 5
Popularity: 0.462255
First Submitted: 2017-11-17 06:47
Last Updated: 2019-10-04 08:59

Latest Comments

« First ‹ Previous 1 2

bboozzoo commented on 2018-02-21 10:23

@mati865 same thing happens on Arch at the moment. Master branch is in a bit of a flux, so it's best to use snapd package, which has just been updated to 2.31.1 and should work just fine.

Update: you need to use edge branch of the core snap with current master (probably at least until 2.32) is released. snap refresh core --edge will do the trick

mati865 commented on 2018-02-21 10:04

On Manjaro when starting any non-classic snap I'm getting:

$ spotify
execl failed: No such file or directory
child exited with status 1


bboozzoo commented on 2018-02-21 06:37

@kirkyd thanks for spotting it. Pushed an update.

This is what happens when you're too lazy and stop doing chrooted builds.

kirkyd commented on 2018-02-20 22:54

man page seems to be missing...

/home/kirk/build/snapd-git/PKGBUILD: line 178: /home/kirk/build/snapd-git/pkg/snapd-git/usr/share/man/man1/snap.1: No such file or directory

obi12341 commented on 2018-02-19 13:08

@bboozzoo thanks :)

bboozzoo commented on 2018-02-19 11:33

@obi12341 pushed an update. Upstream code was updated to not fiddle with LDFLAGS in one of the helper binaries (snap-seccomp) thus allowing the Arch specific patch to be dropped.

obi12341 commented on 2018-02-19 10:38


latest update displays some errors: ==> Starting prepare()... patching file cmd/snap-seccomp/main.go Hunk #1 FAILED at 20. 1 out of 1 hunk FAILED -- saving rejects to file cmd/snap-seccomp/main.go.rej ==> ERROR: A failure occurred in prepare().

output of cmd/snap-seccomp/main.go.rej:

bm456 commented on 2018-01-19 14:47

i'm testing it

this was my content

i've run sudo rm -rf /snap

i'll test

bboozzoo commented on 2018-01-16 06:30

As I understand this is a message coming from pacman when it does a check for potential file conflicts. Have you made the symlink yourself when the old community package was installed? Can you make sure that the old snapd and snap-confine packages are removed, remove the symlink, and try to install snapd-git again?

bm456 commented on 2018-01-15 20:33


i've an error with your program

snapd-git: /snap exists in filesystem

original log (at spanish)

snapd-git: /snap existe en el sistema de archivos