Re: [PATCH] Prototype register-path

l...@gnu.org (Ludovic Courtès) writes: > Hi reepca! > > I gave this patch set a try and looked at the code, and it looks very > good to me! > > “make check TESTS=tests/store.scm” passes now with the fixes you posted > today (‘getenv’ & co.) I end up with 2 failed tests, but neither of them are th

Re: GuixSD bootable ISO-9669 image

On Tue, 16 May 2017 10:31:36 +0200 l...@gnu.org (Ludovic Courtès) wrote: > Honestly, I was under the assumptions that DCE UUIDs was all that > mattered: it works for ext2 and btrfs, right? I would think that people > would rarely add FAT32 or ISO9660 UUIDs to the OS config. With UEFI I thought

Unexpected behaviour of guix environment --container

Hi, I try debugging some package test-cases. The test-suite runs (but fails) when using "guix build". Now I want to get an environment matching the build container (including the already build package). For this I run e.g. ./pre-inst-env guix environment -C kdelibs4support@5.34.0 --ad-hoc stra

In need for a simple "join build container"

Hi, I find myself debugging some package test-cases quite often. This is *very* time-consuming, esp. if compiling the source takes several minutes. So what I need is something to drop me into an interactive shell if the build fails. At the moment for these cases I try setting of an environment (

Re: In need for a simple "join build container"

Hartmut Goebel writes: > Hi, > > I find myself debugging some package test-cases quite often. This is > *very* time-consuming, esp. if compiling the source takes several minutes. > > So what I need is something to drop me into an interactive shell if the > build fails. > > At the moment for these

Re: 02/02: gnu: Add s.

Mark H Weaver (2017-06-04 20:15 -0400) wrote: >> +(define-public s >> + (let ((commit "6604341edb3a775ff94415762af3ee9bd86bfb3c") >> +(revision "1")) >> +(package >> + (name "s") >> + (version (string-append "0.0.0-" revision "." (string-take commit 7))) > > I think we shoul

Serial line lock directory

Hi, I'm trying to package minicom and there I get an error message checking for com line lock directory... configure: error: No suitable lock directory ... which was checking for a (common) directory to put a file in (as a marker) when a serial device is in use (and removing the file to fre

Re: 02/02: gnu: Add s.

Alex Kost writes: > Mark H Weaver (2017-06-04 20:15 -0400) wrote: > >>> +(define-public s >>> + (let ((commit "6604341edb3a775ff94415762af3ee9bd86bfb3c") >>> +(revision "1")) >>> +(package >>> + (name "s") >>> + (version (string-append "0.0.0-" revision "." (string-take com