Build failure in pyicu

2017-12-15 Thread Mark Meyer
Hi, I've got a build failure in PyICU (python2-pyicu) during the test phase: == FAIL: testSurrogatePairs (test.test_Script.TestScript) -- Traceback (most recent c

Re: Build failure in pyicu

2017-12-15 Thread Tobias Geerinckx-Rice
Mark Meyer wrote on 15/12/17 at 10:26: > Hi, > I've got a build failure in PyICU (python2-pyicu) during the test phase: > > == > FAIL: testSurrogatePairs (test.test_Script.TestScript) >

[PATCH] gnu: python2-pyicu: Disable failing test.

2017-12-15 Thread Tobias Geerinckx-Rice
* gnu/packages/python.scm (python2-pyicu)[arguments]: Add ‘delete-failing-test’ phase. --- Mark, ...of course it finishes right after I send that previous e-mail. This patch makes the build pass for me. Could you confirm whether it works for you? Kind regards, T G-R gnu/packages/python.scm |

Re: [PATCH] gnu: python2-pyicu: Disable failing test.

2017-12-15 Thread Mark Meyer
Tobias, thanks for the patch, this works for me :) Cheers, Mark On Fri, Dec 15, 2017, at 11:47, Tobias Geerinckx-Rice wrote: > * gnu/packages/python.scm (python2-pyicu)[arguments]: Add > ‘delete-failing-test’ phase. > --- > > Mark, > > ...of course it finishes right after I send that previous e

Re: [PATCH] gnu: python2-pyicu: Disable failing test.

2017-12-15 Thread Tobias Geerinckx-Rice
Mark, Mark Meyer wrote on 15/12/17 at 11:58: > thanks for the patch, this works for me :) Wonderful! Pushed as d65854bdda4ad5464fcd8fe6289eedc13ea82ba1. (Just FYI: if you post to bug-g...@gnu.org next time, you'll get the visceral satisfaction of closing yet another bug. ;-) Kind regards, T G-

Re: [PATCH] gnu: python2-pyicu: Disable failing test.

2017-12-15 Thread Mark Meyer
However, for some reason python2-vobject fails to pick up this change and fails to build :( On Fri, Dec 15, 2017, at 12:17, Tobias Geerinckx-Rice wrote: > Mark, > > Mark Meyer wrote on 15/12/17 at 11:58: > > thanks for the patch, this works for me :) > Wonderful! Pushed as d65854bdda4ad5464fcd8fe

Re: java: switch to icedtea-8 as default JDK

2017-12-15 Thread Gábor Boskovits
I've found the problem with java-hamcrest-core. The root cause of this is that java-jarjar uses a bundled copy of asm, version 4.0. This asm version does not support icedtea8. I propose to use java-asm instead of the bundled one. In my opinion the best course of action should be: 1. create a pack

Re: java: switch to icedtea-8 as default JDK

2017-12-15 Thread Gábor Boskovits
Ok, it seems, that java-asm does not currently uses test anyway, so I can remove the junit native input. Will check if it is also true on master... 2017-12-15 14:52 GMT+01:00 Gábor Boskovits : > I've found the problem with java-hamcrest-core. > The root cause of this is that java-jarjar uses a bu

Re: java: switch to icedtea-8 as default JDK

2017-12-15 Thread Gábor Boskovits
It seems, that it is aslo safe to apply this on master. This is the patch: >From 8a4f7bcbbbefe282c15447907a67f81c5bb60aae Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?G=C3=A1bor=20Boskovits?= Date: Fri, 15 Dec 2017 15:22:03 +0100 Subject: [PATCH] gnu: Clean up depencies of java-asm. * gnu/packages/j

Re: Reproducible installation images

2017-12-15 Thread Ludovic Courtès
Mark H Weaver skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Mark H Weaver skribis: >> >>> l...@gnu.org (Ludovic Courtès) writes: >>> Mark H Weaver skribis: > To enable independent verification of these installer images, it would > be helpful to include the precise com

Re: emacs-25.3 aborted

2017-12-15 Thread Ludovic Courtès
Ricardo Wurmus skribis: > I can reproduce this on i686. After installing Emacs with “guix package > --no-grafts -u emacs”, however, there is no crash. > > The crash only happens with the grafted Emacs. Indeed: --8<---cut here---start->8--- $ ./pre-inst-env g

Re: Dualbooting with guixsd not handling grub installation

2017-12-15 Thread Ludovic Courtès
Hello, Martin Castillo skribis: > I realised a third option for dualbooting: > menuentry "GuixSD - grub core.img loader" { > search --set root --label guix-root --hint hd0,gpt3 > multiboot /boot/grub/i386-pc/core.img > } Indeed, that should always work. Note that if all you want is dual-bo

Re: Snippets for working on Guix

2017-12-15 Thread Ludovic Courtès
Hi! Ricardo Wurmus skribis: > to avoid the need to type out boilerplate I wrote a couple of snippets > that can be used with yasnippet in Emacs, and I thought I should share > them with you. > > These snippets are available: > > ./scheme-mode/guix-package > ./scheme-mode/guix-origin > ./sc

[WIP][PATCH] profiles: info-dir-file: Don't consider unwanted manifest entries

2017-12-15 Thread 宋文武
Hello! Currently we run profile hooks for all manifest inputs, so if you install a new package to your profile, all profile hooks will be run again, even if the new package doesn't provide info manuals, man pages, etc. Ideally only interested hooks need to be run, eg: if the new package has info

Re: [WIP][PATCH] profiles: info-dir-file: Don't consider unwanted manifest entries

2017-12-15 Thread Martin Castillo
Hi, in the second patch file: > + ;; We only need to build the 'dir' file for inputs that does containing info > + ;; manuals. s/containing/contain On 15.12.2017 16:12, 宋文武 wrote:> Hello! > > Currently we run profile hooks for all manifest inputs, so if you > install a new package to your profi

Re: [PATCH] gnu: python2-pyicu: Disable failing test.

2017-12-15 Thread Tobias Geerinckx-Rice
Mark, Mark Meyer wrote on 15/12/17 at 13:30: > However, for some reason python2-vobject fails to pick up this change > and fails to build :( Nuts. You're right. Long story and 2 drafts short: I had some mystical (and wrong) ideas about package-with-python2 that have now been set straight and pus

Re: Snippets for working on Guix

2017-12-15 Thread Ricardo Wurmus
Hi Ludo, > Ricardo Wurmus skribis: > >> to avoid the need to type out boilerplate I wrote a couple of snippets >> that can be used with yasnippet in Emacs, and I thought I should share >> them with you. >> >> These snippets are available: >> >> ./scheme-mode/guix-package >> ./scheme-mode/gui

GRUB LUKS support is slow?

2017-12-15 Thread Ludovic Courtès
Hello Guix, I have an encrypted root. When GRUB asks me for my passphrase, it takes 5–10 seconds after I hit enter before it displays the menu; then, once I’ve selected an entry, it takes another 5 seconds or so to boot. It’s always been this way for me (that’s on UEFI), but I’m sufficiently ann

Re: GRUB LUKS support is slow?

2017-12-15 Thread Mark H Weaver
l...@gnu.org (Ludovic Courtès) writes: > I have an encrypted root. When GRUB asks me for my passphrase, it takes > 5–10 seconds after I hit enter before it displays the menu; then, once > I’ve selected an entry, it takes another 5 seconds or so to boot. > > It’s always been this way for me (that’

Re: GRUB LUKS support is slow?

2017-12-15 Thread Adam Van Ymeren
On December 15, 2017 5:53:15 PM EST, Mark H Weaver wrote: >l...@gnu.org (Ludovic Courtès) writes: > >> I have an encrypted root. When GRUB asks me for my passphrase, it >takes >> 5–10 seconds after I hit enter before it displays the menu; then, >once >> I’ve selected an entry, it takes another 5

Re: GRUB LUKS support is slow?

2017-12-15 Thread Tobias Geerinckx-Rice
Guix, I'm afraid you'll all be somewhat disappointed by the answer... Adam Van Ymeren wrote on 16/12/17 at 00:25: > On December 15, 2017 5:53:15 PM EST, Mark H Weaver > wrote: >> l...@gnu.org (Ludovic Courtès) writes: >> >>> I have an encrypted root. When GRUB asks me for my passphrase, >>>

Re: GRUB LUKS support is slow?

2017-12-15 Thread Clément Lassieur
Ludovic Courtès writes: > Hello Guix, > > I have an encrypted root. When GRUB asks me for my passphrase, it takes > 5–10 seconds after I hit enter before it displays the menu; then, once > I’ve selected an entry, it takes another 5 seconds or so to boot. > > It’s always been this way for me (tha

Re: GRUB LUKS support is slow?

2017-12-15 Thread Adam Van Ymeren
On December 15, 2017 8:10:24 PM EST, Tobias Geerinckx-Rice wrote: >Guix, > >I'm afraid you'll all be somewhat disappointed by the answer... > >Adam Van Ymeren wrote on 16/12/17 at 00:25: >> On December 15, 2017 5:53:15 PM EST, Mark H Weaver >> wrote: >>> l...@gnu.org (Ludovic Courtès) writes: >

Re: Building Docker images of GuixSD

2017-12-15 Thread Chris Marusich
Christopher Baines writes: > Unfortunately, while I could get a shell using "docker exec ...", I had > to start the guix-daemon manually as the shepherd service didn't seem to > work, at least initially. Also, when I had started it, I tried > installing a package, and there was some promising out

How to customize the kernel

2017-12-15 Thread Chris Marusich
Hi, Suppose you want to compile a custom kernel. Suppose you want to use a custom kernel configuration. Currently, none of the logic that builds linux-libre kernels in Guix is public,, so the implication is that nobody should be using that to customize their kernel builds. Is anyone building cu

Re: Snippets for working on Guix

2017-12-15 Thread Maxim Cournoyer
Hi Ricardo! Ricardo Wurmus writes: > Hi Guix, > > to avoid the need to type out boilerplate I wrote a couple of snippets > that can be used with yasnippet in Emacs, and I thought I should share > them with you. > > These snippets are available: > > ./scheme-mode/guix-package > ./scheme-mode/

Re: [bug#29708] Update s-shell

2017-12-15 Thread 宋文武
ng0 writes: > Ludovic Courtès transcribed 0.4K bytes: >> ng0 skribis: >> >> > From cf2cbe9e9e525aa9dd697fcedb255a0fbc194ac9 Mon Sep 17 00:00:00 2001 >> > From: ng0 >> > Date: Thu, 14 Dec 2017 13:22:58 + >> > Subject: [PATCH] s-shell: Update to commit >> > da2e5c20c0c5f477ec3426dc2584889a7

Re: Snippets for working on Guix

2017-12-15 Thread Arun Isaac
>> to avoid the need to type out boilerplate I wrote a couple of snippets >> that can be used with yasnippet in Emacs, and I thought I should share >> them with you. >> >> These snippets are available: >> >> ./scheme-mode/guix-package >> ./scheme-mode/guix-origin >> ./scheme-mode/guix-git-re

geiser-xref-callers does not seem to work

2017-12-15 Thread Chris Marusich
Hi, It seems that geiser-xref-callers does not work for me. I believe I've configured Geiser correctly, since other commands like geiser-edit-symbol-at-point and geiser-doc-symbol-at-point do work in some cases. Here is a specific example where it fails for me: * Clone the Guix Git repository (