2018-03-06 22:40 GMT+01:00 Ricardo Wurmus :
>
> Hi Gábor,
>
> > * gnu/packages/patches/java-jeromq-fix-tests.patch: New file.
> > * gnu/local.mk (dist_patch_DATA): Add it.
> > * gnu/packages/java.scm (java-jeromq)[source](patches): Add it.
> > [arguments](#test-exclude): Disable more failing tests
On Mon, Mar 05, 2018 at 09:04:34PM +0100, Andreas Enge wrote:
> builder for
> `/gnu/store/d5mkvgcyix959dlgka43qf66d1252hv8-qemu-minimal-2.10.2.drv' failed
> with exit code 1
After updating to a more recent git checkout, qemu-minimal is downloaded from
hydra:
/gnu/store/8l47i793wnddcp476cc819hznd
On Tue, Mar 06, 2018 at 05:42:56PM +0100, Marius Bakke wrote:
> How much memory does this machine have? Can you try to set up some swap
> space?
There is 1 GB of main memory according to /proc/meminfo, and there should
also be 500 MB of swap space. Maybe this is not enough?
Andreas
Hi Gábor,
> * gnu/packages/patches/java-jeromq-fix-tests.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Add it.
> * gnu/packages/java.scm (java-jeromq)[source](patches): Add it.
> [arguments](#test-exclude): Disable more failing tests.
> ---
Thank you for this.
> diff --git a/gnu/packages
Hi,
> This is expected. Strictly speaking, we’re talking about two different
> package objects, hence the different IDs.
I wonder
a) whether it is useful to have different graph nodes for the same package.
This is about usability of the resulting graph, esp. since this is the
default graph outp
Andreas Enge writes:
> 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:
Hi Ludo,
> If you run this on an “old” GuixSD, ‘find-long-options’ is undefined.
How can it be that (gnu services base) with find-long-options call is present
but the (gnu build linux-boot)'s find-long options isn't present?
Aren't they either both added by "guix system reconfigure" (or both rem
The icedtea packages are not reproducible.
* The JDK provides jar files that did not undergo repacking (see
ant-build-system), so they contain timestamps.
* The doc output contains files generated by javadoc, which contain
more than one timestamp. Near the top is a comment:
A little
2018-03-06 15:43 GMT+01:00 Ricardo Wurmus :
>
> Ricardo Wurmus writes:
>
> > Marius Bakke writes:
> >
> >> I suppose we'll have to set PYTHONHASHSEED somewhere in
> >> python-build-system as well. Did you check if that makes a difference
> >> for numpy? Perhaps it's enough to set it if we add
Ricardo Wurmus writes:
> Marius Bakke writes:
>
>> I suppose we'll have to set PYTHONHASHSEED somewhere in
>> python-build-system as well. Did you check if that makes a difference
>> for numpy? Perhaps it's enough to set it if we add an auto-compilation
>> step?
>
> Right, I’m going to test t
Marius Bakke writes:
> The only remark I have is: is introducing a new variable necessary?
> SOURCE_DATE_EPOCH implies that the user wants a deterministic build;
> the upstream patch doesn't actually honor it outside of making the
> hashing method deterministic. So, I think it might be enough t
The r-lambda-r package is not reproducible. The differences in the RDX
files indicates that the package’s RDB file includes references to
environments that differ in size, which leads to variables being stored
at different offsets in the RDB file.
Here’s the diffoscope output:
--8<--
Hi,
My system is Ubuntu 16.04.
I ran './guix-install.sh' and got the message: "This script must be run
as root.". So I ran 'sudo ./guix-install.sh' and got an error message
saying that:
GUIX_PROFILE="${HOME}/.guix-profile"
source "${GUIX_PROFILE}/etc/profile"
the 'source' command doesn
13 matches
Mail list logo
