Package Details: snapd-git 2.35.4.r1435.g9e7ba8ed9-1

Git Clone URL: https://aur.archlinux.org/snapd-git.git (read-only)
Package Base: snapd-git
Description: Service and tools for management of snap packages.
Upstream URL: https://github.com/snapcore/snapd
Licenses: GPL3
Conflicts: snap-confine, snapd
Provides: snapd
Submitter: bboozzoo
Maintainer: bboozzoo (aimileus, zyga)
Last Packager: bboozzoo
Votes: 4
Popularity: 0.112935
First Submitted: 2017-11-17 06:47
Last Updated: 2018-10-08 07:51

Latest Comments

1 2 Next › Last »

egrupled commented on 2018-03-30 11:44

@bboozzoo All clear now, thanks for help.

BTW: shouldn't systemd-generator be fixed in non git version too?

bboozzoo commented on 2018-03-29 19:34

pushed an update with a fix for systemd-generator and workaround for TMPDIR

@egrupled can you check if it builds correctly on your system now?

egrupled commented on 2018-03-29 12:46

@bboozzoo Considering below, can you add export TMPDIR="/tmp" at the beginning of check() section? This will make sure that /tmp is used for tests. Otherwise build will fail for everyone who uses non-standard TMPDIR.

egrupled commented on 2018-03-20 09:51

I think when someone set TMPDIR to something else than /tmp they had good reason too. Hardcoding dirs isn't smart behavior. Also if they refuse to remove they should refuse to create in first place.

bboozzoo commented on 2018-03-20 06:36

@egrupled the cleanup in unit tests refuses, IMO for good reasons, to remove anything that does not start with /tmp/, given that the directory is created using glib's g_dir_make_tmp() and the strace, I'd guess that your TMPDIR is set to /build

egrupled commented on 2018-03-19 20:24

@bboozzoo Yeah, in clean chroot it works. Unfortunately most AUR helpers don't support building in clean chroot.

I uploaded strace of failed attempt here: https://ghostbin.com/paste/h4n4r/raw

I suppose it's related to BUILDDIR != TMPDIR on my machine.

bboozzoo commented on 2018-03-19 18:31

@egrupled tried mkchrootpkg in a clean chroot without any issues. Running unit tests directly no issues either. Is this reproducible? Can you run this specific test under strace (strace -vf ./cmd/libsnap-confine-private/unit-tests -p /locking/sc_lock_unlock) and paste the log somewhere?

egrupled commented on 2018-03-19 17:40

Check fails on my machine with:

/locking/sc_lock_unlock: refusing to remove: /build/.LMFQFZ: Resource temporarily unavailable
make: *** [Makefile:3334: check-unit-tests] Error 1

Any clues?

bboozzoo commented on 2018-02-22 07:25

@mati865 can share which apps segfault? It'd be interesting to look into this in more detail. The only snaps requiring opengl that I have used are ohmygiraffe and boa. No issues there, although I'm using nvidia-340xx drivers as my hardware is quite dated.

mati865 commented on 2018-02-21 22:28

@bboozzoo thanks, I hoped snap run --gdb from git will help to discover why apps requiring OpenGL segfault. Unfortunately there is no stack trace avaiable. Nvidia drivers 390