Ricardo Wurmus writes:
> I have applied this patch locally:
>
> diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
> index 5f701701a..0d1ecc3c6 100644
> --- a/gnu/packages/python.scm
> +++ b/gnu/packages/python.scm
> @@ -359,8 +359,42 @@ data types.")
>
Ricardo Wurmus writes:
> Ricardo Wurmus writes:
>
>> Unfortunately, this doesn’t fix all reproducibility problems with numpy:
>>
>> --8<---cut here---start->8---
>> Binary files
>>
Gábor Boskovits writes:
> 2018-03-05 16:36 GMT+01:00 Gábor Boskovits :
>
>> 2018-03-05 1:05 GMT+01:00 Ricardo Wurmus :
>>
>>>
>>> Ricardo Wurmus writes:
>>>
>>> > Unfortunately, this doesn’t fix all
2018-03-05 16:36 GMT+01:00 Gábor Boskovits :
> 2018-03-05 1:05 GMT+01:00 Ricardo Wurmus :
>
>>
>> Ricardo Wurmus writes:
>>
>> > Unfortunately, this doesn’t fix all reproducibility problems with numpy:
>> >
>> > --8<---cut
Guix pull has the wrong error message when the commit-id for the
"--commit" parameter is too short:
$>guix pull --commit=d20647722ad36024a3a0b6e1e75c1ba49b9f61d
Updating from Git repository at
'https://git.savannah.gnu.org/git/guix.git'... guix pull: error: Git
error: unable to parse OID -
Hello,
trying to do a "./pre-inst-env guix system reconfigure" using the recent
git checkout 0ebc1b934d39b6c924cbe17fd37ceb2b201e9ac2 on my x86_64 virtual
machine results in the following error:
TEST: tests/qom-test... (pid=15434)
/mips64el/qom/boston:
Okay, this evening, I see 10 packages being built and lots of messages
"build started"/"build succeeded"; so maybe there is no bug at work here.
Andreas
Related to the attempt to upgrade Racket to 6.12:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30603
Apparently the patch I proposed may break GC, so another option should
be found. But more interestingly is that my thought that things broke
because of a change from Racket 6.11 to 6.12
Hello,
Hartmut Goebel skribis:
> "guix graph" delivers the same package with different IDs. Here is an
> example with a node delivered twice. (For plasma-workspace, which I'm
> working on, this package was even listed four times).
>
> $ ./pre-inst-env guix graph -t
Right now, I do not seem to be running out of build users, but I think
that cuirass nevertheless behaves strangely; so I am asking here instead
of opening a new bug (maybe there is no bug, actually).
I reconfigured bayfront this morning with the latest git checkout.
Right now, there are only two
2018-03-05 1:05 GMT+01:00 Ricardo Wurmus :
>
> Ricardo Wurmus writes:
>
> > Unfortunately, this doesn’t fix all reproducibility problems with numpy:
> >
> > --8<---cut here---start->8---
> > Binary files
Hi Artyom,
Artyom Poptsov skribis:
> I implemented a fix for the looping problem; could you please check if
> the patch works for you?
>
> The changes are committed in e24401f1ef56b1f3d7ef847c54fb0c2fe9cf3cf8 on
> the 'master' branch.
I’d rather let someone else test
Andreas Enge skribis:
> guix system: loading new services: user-homes term-auto nginx...
> shepherd: Evaluating user expression (register-services (primitive-load
> "/gnu/st?") ?).
> guix system: error: exception caught while executing 'eval' on service 'root':
>
l...@gnu.org (Ludovic Courtès) skribis:
> Mark H Weaver skribis:
>
>> l...@gnu.org (Ludovic Courtès) writes:
>>
>>> Diego Nicola Barbato skribis:
>>>
When running `guix system reconfigure /etc/config.scm' as root I get the
following error:
Hi,
"guix graph" delivers the same package with different IDs. Here is an
example with a node delivered twice. (For plasma-workspace, which I'm
working on, this package was even listed four times).
$ ./pre-inst-env guix graph -t package -b graphviz qtbase | grep
autoconf-wrapper
"59511552"
Hello!
Ricardo Wurmus skribis:
> Is it a bad idea to override the timestamps in the generated binaries?
> I think that we could avoid the recency check then, which was an
> obstacle to resetting the timestamps of the source files.
I think it’s good if we can fix Python
On Fri, Mar 02, 2018 at 04:08:33PM +0200, Efraim Flashner wrote:
> When I use a shell script to build all the packages, if a package hangs
> and gets eaten by the timout-limit then it holds the build user and
> space in /tmp until all 10 builders are taken and building stops or all
> the builds
17 matches
Mail list logo