bug#34407: [PATCH] shepherd: Delete the socket file upon exit.

Yes, I have the 'rm /run/user/1000/shepherd/socket' workaround in my session script too... According to 'man 2 bind', the socket pathname should be deleted when no longer required, so a patch to fix this bug: >From f171f6adb2fc6ee3bf4d25378c2e7bba109b43d8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?

bug#34468: guix pull: wrong %system when using --system flag

Hello, Diego Nicola Barbato skribis: > When running ‘guix pull’ with the --system flag the resulting guix is > configured for the host architecture instead of the target > architecture (i.e. the %system variable in ‘(guix config)’ is set to the > host architecture instead of the target architect

bug#34505: [guix, conda]: conda build fail on ubuntu 17.10 (91 errors)

Pjotr Prins writes: > Looks to me it needs to be upgraded. 4.3 is rather old (somehow they > are no longer pushing to pypi) I tried to upgrade it, but newer versions are rather difficult to build. The developers have not yet responded to my bug report: https://github.com/conda/conda/issu

bug#34427: [bug#34453] [PATCH] build guile-static with guile-2.0

Hi Efraim, Efraim Flashner skribis: > When experimenting I found that using guile@2.0 as a base for > guile-static, the resulting guile-static didn't segfault on the target > architecture. As discussed in , I would rather fix the segfault in 2.2 than move b

bug#34499: Fwd: Guile-gnome package broken in Guix

On 2019-02-16 12:02, swedebugia wrote: The files end up in profile/share/guile-gnome-2/... which is not in guiles load path. The result of running the examples: (first get it with guix build --source) $ guile -s hello.scm ... ERROR: In procedure scm-error: no code for module (gnome gobject)

bug#34499: Fwd: Guile-gnome package broken in Guix

The files end up in profile/share/guile-gnome-2/... which is not in guiles load path. The result of running the examples: (first get it with guix build --source) $ guile -s hello.scm ... ERROR: In procedure scm-error: no code for module (gnome gobject) Forwarded Message Su

bug#34494: proot-based non-root setup: refusing to run with elevated privileges (UID 0)

Thanks, Pjotr. So I got it working on one system out of four, following the exact same steps each time: * Debian 9 (Stretch) - 4.9.130-2 x86_64 (real system) - *_fail_* * Ubuntu 17.10 (Artful Aardvark) - 4.13.0-46-lowlatency (real system) - _*fail*_ * Ubuntu 14.04 (Trusty Tahr)  -

bug#34494: proot-based non-root setup: refusing to run with elevated privileges (UID 0)

Hi pjotr, Did you try something like proot -0 -b /proc -b /dev -b /etc -r . -b etc_guix/acl:/etc/guix/acl gnu/store/vir3l..-guix-0.x/bin/guix-daemon —disable-chroot Yes, this doesn’t work - with or without the -0 flag. That used to work. But maybe no longer? I tried the new guix b