Nikita Karetnikov <[email protected]> skribis: >> Also why do this as root? It’s a Bad Idea.) > > Because I use Guix in a chroot. Can it still be harmful?
Usually one never logs in as root. You should only escalate as root when needed, typically via sudo. >> Any hints in test-suite.log or tests/*.log? > > No. There’s probably an error message in test-suite.log in such cases. >> Could you check the permissions on /nix/var/nix/daemon-socket/socket? > > srw-rw-rw- 1 root root 0 2013-06-22 01:34 socket > > I've found out that the following works: > > # ./pre-inst-env guix-daemon --build-users-group=nixbld & > # ./pre-inst-env guix build -K hello > > But 'make check' fails for some reason. ‘make check’ uses a different store (see the ‘test-env’ script.) It may be that $top_builddir/test-tmp/var/XXX/daemon-socket/socket is created with the wrong user or permissions. Could you check whether this works: ./test-env guile -c '(use-modules (guix store)) (pk (open-connection))' If it fails, can you prefix that command line with ‘strace -f -o log’, and post the output of ‘grep daemon-socket log’? TIA, Ludo’.
