* gnu/packages/python.scm (python-pysam, python2-pysam): New variables.
---
gnu/packages/python.scm | 38 ++
1 file changed, 38 insertions(+)
diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index f81ab69..24bec00 100644
--- a/gnu/packages/python.
Hi,
On 19/12/14 19:20, Eelco Dolstra wrote:
> I see a few ways to get PID namespaces back:
>
> * Do a regular fork followed by clone(... | CLONE_NEWPID | CLONE_PARENT)
> (after
> which the intermediate process can exit).
This has been implemented in bd0f362d2fad1dd5f28e762011888b5eabd21280.
-
On Tue, Dec 23, 2014 at 1:17 AM, Ludovic Courtès wrote:
> I found that “guix build python2-matplotlib -n” triggers a seemingly
> infinite loop (either uses of ‘package-with-python2’ somehow introduce
> cycles, or they lead to very large DAGs), which is what is causing Hydra
> evaluation failures.
Federico Beffa writes:
> On Tue, Dec 23, 2014 at 1:17 AM, Ludovic Courtès wrote:
>> I found that “guix build python2-matplotlib -n” triggers a seemingly
>> infinite loop (either uses of ‘package-with-python2’ somehow introduce
>> cycles, or they lead to very large DAGs), which is what is causing
Federico Beffa skribis:
> The build does finish as I've tested it on my machine before
> committing the package. However, for some reason, guix needs very long
> to generate the derivation. On my machine (quad-core Xeon E5520)
> python2-matplotlib takes ca. 31 mins to start building.
> Python2-sc
Ludovic Courtès writes:
> Federico Beffa skribis:
>
>> The build does finish as I've tested it on my machine before
>> committing the package. However, for some reason, guix needs very long
>> to generate the derivation. On my machine (quad-core Xeon E5520)
>> python2-matplotlib takes ca. 31 min
