Re: Anyone got ideas on how to make Gajim aware of plugins in store?

2017-06-13 Thread Ricardo Wurmus
ng0 writes: > Do I use native-search-paths? There is no variable > which is used in Gajim, so I think maybe I need to > include this in the wrapper and add something similar > to the native-search-path which would look in > ~/.guix-profile/share/gajim/plugins/ for $name-of-plugin > to PATH? Gaj

Re: Guix pull failure for Python 2.7.11

2017-06-13 Thread Ricardo Wurmus
Hi Mohammad, > Since the error is about connection, I should say that I was connected > to the internet when I ran `guix pull'. Inside of the build environment there is no network connection, so this test would always fail. > Because of this failure, I am unable to continue pulling the > higher

Re: (guix git) and guile-git finalizers.

2017-06-13 Thread Mathieu Othacehe
Hi Ludo, > To fix this, I think ‘libgit2-shutdown’ needs to call > ‘scm_run_finalizers’ before calling ‘git_shutdown’, but I’m not sure if > it’s enough. I tried this approach (using dynamic-call), and indeed, it's not enough. Before, removing (libgit2-shutdown) from (guix-git), I'll explore the

Re: (guix git) and guile-git finalizers.

2017-06-13 Thread Mathieu Othacehe
Hi Andy, > Nice sleuthing! Thanks :) > > If you want to manually handle finalization at 'safe' points from > Scheme, guardians are the things to use. Add your "finalizable" object > to a guardian, and periodically "pump" the guardian to see if anything > is finalizable; you can run the finaliz

Re: Invoking user shepherd; Was: Re: Defining *user* services in Guix

2017-06-13 Thread Ludovic Courtès
Hello Danny, Danny Milosavljevic skribis: > On Tue, 13 Jun 2017 10:06:16 +0200 > l...@gnu.org (Ludovic Courtès) wrote: > >> The ‘delete-file’ was to avoid EADDRINUSE but I wonder if it’s really a >> good idea. > > Not a good idea. > > We should just put the shepherd socket somewhere in /run/user

Re: Invoking user shepherd; Was: Re: Defining *user* services in Guix

2017-06-13 Thread Danny Milosavljevic
Hi Ludo, On Tue, 13 Jun 2017 10:06:16 +0200 l...@gnu.org (Ludovic Courtès) wrote: > The ‘delete-file’ was to avoid EADDRINUSE but I wonder if it’s really a > good idea. Not a good idea. We should just put the shepherd socket somewhere in /run/user/4711 where 4711 is the user id (the entire nam

Re: Compilation failure on very large module

2017-06-13 Thread ng0
Ludovic Courtès transcribed 0.9K bytes: > Hello, > > Ricardo Wurmus skribis: > > > Here’s the crash with Guile 2.2. I’ve added the module to the list of > > modules that should be compiled and ran “make”. You can see that there > > are a couple of undefined variables, but I don’t think this sh

Re: Compilation failure on very large module

2017-06-13 Thread Ludovic Courtès
Hello, Ricardo Wurmus skribis: > Here’s the crash with Guile 2.2. I’ve added the module to the list of > modules that should be compiled and ran “make”. You can see that there > are a couple of undefined variables, but I don’t think this should lead > to a crash. Looks like the same problem a

Re: Compilation failure on very large module

2017-06-13 Thread Ricardo Wurmus
Ricardo Wurmus writes: > I have a very large Guix module with almost all packages from CRAN. > Unfortunately, I cannot compile it. Guile 2.2.2 runs out of memory and > even Guile 2.0 crashes with “list too long”. Here’s the crash with Guile 2.2. I’ve added the module to the list of modules th

Re: (guix git) and guile-git finalizers.

2017-06-13 Thread Andy Wingo
On Mon 12 Jun 2017 14:44, Mathieu Othacehe writes: > Maybe the right answer is to disable auto finalization and call > run-finalizers as described here : > > https://www.gnu.org/software/guile/manual/html_node/Foreign-Object-Memory-Management.html#Foreign-Object-Memory-Management > > However I ca

Compilation failure on very large module

2017-06-13 Thread Ricardo Wurmus
Hi, I have a very large Guix module with almost all packages from CRAN. Unfortunately, I cannot compile it. Guile 2.2.2 runs out of memory and even Guile 2.0 crashes with “list too long”. Here’s what I did: guix environment --pure --ad-hoc guile@2.0 guix environment --pure --ad-hoc guil

Re: (guix git) and guile-git finalizers.

2017-06-13 Thread Ludovic Courtès
Hi! Mathieu Othacehe skribis: > While integrating (guix git) into Cuirass, I noticed unexpected > segfaults during "latest-repository-commit" evaluation. > > Segfaults can be narrowed to the following lines: > > (use-modules (git)) > (begin (libgit2-init!) >(let ((rep (repository-open "s

Re: Invoking user shepherd; Was: Re: Defining *user* services in Guix

2017-06-13 Thread Ludovic Courtès
Hello! Danny Milosavljevic skribis: > For a real user shepherd, it would be nice if when I logged in twice using > the same user account (without logging out in-between - so resulting in two > sessions of that user) it would still only have one shepherd instance for > that user account in tot

Re: Invoking user shepherd; Was: Re: Defining *user* services in Guix

2017-06-13 Thread Ludovic Courtès
Hello! Mathieu Othacehe skribis: > I wrote a first draft of user services a month ago. The idea here is > that guix user -r user-manifest.scm generates a script that lauches a > user shepherd. > > For instance with the following user-manifest.scm : > > (define (redshift-service config) > (list