Gábor Boskovits writes:
>> Are there any known big problems that remain to be solved here?
>>
>>
> There are two missing patchests. One for bootstrapping java-asm, and
> one that adds ant-junit to packages that needs them.
Okay, thanks for the reminder.
> One of the problems I know of is that
Hi Guix,
“guix pull” fails building Guix itself. I don’t have access to the
test-suite.log. Here’s the output:
--8<---cut here---start->8---
[…]
PASS: tests/texlive.scm
FAIL: tests/store.scm
[…]
Hi Ludo,
I've tried 'guix run' for a little bit and I think it has a lot of
potential! One of the problems with guix environment containers is that
it can take quite a while to build. 'guix run' could solve that.
Adding Xpra to 'guix run' and/or 'guix environment' in some way could
definitely be
Ricardo Wurmus writes:
> Hi Guix,
>
> “guix pull” fails building Guix itself. I don’t have access to the
> test-suite.log. Here’s the output:
>
> --8<---cut here---start->8---
> […]
> PASS: tests/texlive.scm
> FAIL: tests/store.scm
> […]
> ==
Ricardo Wurmus writes:
> Ricardo Wurmus writes:
>
>> Hi Guix,
>>
>> “guix pull” fails building Guix itself. I don’t have access to the
>> test-suite.log. Here’s the output:
>>
>> --8<---cut here---start->8---
>> […]
>> PASS: tests/texlive.scm
>> FAIL: tests
Hi Ludo,
On Thu, 15 Feb 2018 00:17:55 +0100
l...@gnu.org (Ludovic Courtès) wrote:
> Turns out creating the relevant indexes helps a lot, unsurprisingly I
> guess:
>
>
> https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/commit/?id=db27955ad3fae260ee2aa4bace8dd6a4115d338c
Yup. It's a tr
* src/cuirass/database.scm (db-get-builds): Modify.
(db-get-build): Modify.
---
src/cuirass/database.scm | 165 ---
1 file changed, 55 insertions(+), 110 deletions(-)
diff --git a/src/cuirass/database.scm b/src/cuirass/database.scm
index dd3e5a2..5a4631
Hello Ricardo,
Ricardo Wurmus writes:
> Hi Alex,
>
>> I want to be a student this year since this will be my final chance (I
>> am graduating this year). I look at the libreplanet page and I think
>> only the build daemon project is suitable for me since I don't have
>> knowledge in networking.
* src/cuirass/database.scm (db-get-builds): Inline output selection.
---
src/cuirass/database.scm | 87 +---
1 file changed, 83 insertions(+), 4 deletions(-)
diff --git a/src/cuirass/database.scm b/src/cuirass/database.scm
index 5a4631f..f19ee03 100644
Hi Guix,
I have a bad day. After the upgrade to glibc 2.26 none of the
Guix-installed software runs on the HPC cluster running CentOS 6.8.
The glibc 2.26 expects a minimum kernel version of 3.x on x86_64, but
CentOS 6.8 only comes with a heavily patched 2.6.32.
The NixOS developers patch glibc
Ricardo Wurmus writes:
> The NixOS developers patch glibc to make sure that all software still
> runs on Linux 2.6.32:
>
>
> https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/development/libraries/glibc/allow-kernel-2.6.32.patch
>
> Can we please also apply this?
We could also ap
Ricardo Wurmus writes:
> Ricardo Wurmus writes:
>
>> The NixOS developers patch glibc to make sure that all software still
>> runs on Linux 2.6.32:
>>
>>
>> https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/development/libraries/glibc/allow-kernel-2.6.32.patch
>>
>> Can we please
Hi Ricardo,
sorry to hear about those problems.
Can you try just passing --enable-kernel=2.6.32 to "configure" of glibc instead?
It should set the minimal version without any weird patching.
Our glibc/linux in gnu/packages/base.scm specifies --enable-kernel=3.2.0 which
we could modify to someth
Ricardo Wurmus writes:
> Ricardo Wurmus writes:
>
>> Ricardo Wurmus writes:
>>
>>> The NixOS developers patch glibc to make sure that all software still
>>> runs on Linux 2.6.32:
>>>
>>>
>>> https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/development/libraries/glibc/allow-kern
Ricardo Wurmus writes:
>> Here’s a patch to graft the glibc to apply the patch to allow the 2.6.32
>> kernel. I’m going to apply this at work now.
>
> That patch had a couple of problems. Here’s a new version.
Sad to hear of your troubles, thanks a lot for posting this. We
discovered at Verum
Hi Danny,
> Can you try just passing --enable-kernel=2.6.32 to "configure" of glibc
> instead?
>
> It should set the minimal version without any weird patching.
Does this work even though the official minimum kernel version for glibc
2.26 is 3.2.0?
> But newer glibc has moved a lot of kernel d
Pushed both.
2 of the unit tests fail with the mysterious error message:
unexpected value #
What's more, when I copy the contents of the test-assert to right before the
test-assert, the problem vanishes and all tests succeed...
Hi,
here is my first attempt at localizing guix.texi. This patch adds
guix.fr.texi, a localized version of the manual. It uses po4a to
generate the .po file and use that same file to generate the localized
manual.
I had to include the guix.fr.texi in the commit because it is necessary
that it exi
Le Mon, 19 Feb 2018 23:34:37 +0100,
Julien Lepiller a écrit :
> Hi,
>
> here is my first attempt at localizing guix.texi. This patch adds
> guix.fr.texi, a localized version of the manual. It uses po4a to
> generate the .po file and use that same file to generate the localized
> manual.
>
> I h
Hi Ricardo,
> Does this work even though the official minimum kernel version for glibc
> 2.26 is 3.2.0?
I think so, BUT the patchset looks pretty similar to what would happen
if you specified the configure flag except for one spot.
So maybe Nix found out some ill effects.
The most worrying part
the fix did not work, see
https://hydra.gnu.org/build/2513115
est project /tmp/guix-build-ldc-0.17.4.drv-0/build
Start 1: build-druntime-ldc-unittest
1/673 Test #1: build-druntime-ldc-unittest . Passed
533.53 sec
Start 2: build-druntime-test-runner
Mark,
On Fri, 2018-02-09 at 03:43 -0500, Mark H Weaver wrote:
> > nckx pushed a commit to branch master
> > in repository guix.
> >
> > commit 906f1b48e20a032c22a164c89f9e8862ab2bec7a
> > Author: Tobias Geerinckx-Rice
> > Date: Wed Jan 3 09:01:53 2018 +0100
> >
> > gnu: luajit: Update to
There are some patches on the staging branch, including an update to the
time zone database.
What are the plans for the next week or so? Should we try merging the
staging branch in that timeframe?
signature.asc
Description: PGP signature
Leo Famulari writes:
> There are some patches on the staging branch, including an update to the
> time zone database.
>
> What are the plans for the next week or so? Should we try merging the
> staging branch in that timeframe?
Yes, let's start this in a few days, when Hydra calms down. Perhaps
24 matches
Mail list logo