Re: Problems with setting up prosody with IPv6 and certbot

nee writes: > 4. Ipv6 is not enabled by default on GuixSD All my GuixSD machines have IPv6 addresses, and I never did anything special. > Problem: > With the default configuration `ifconfig` > and `ip addr` did not show an ipv6 address for my server. > This resulted in

Seeding the Linux RNG at first boot

On Wed, Dec 06, 2017 at 12:11:36AM +0100, Marius Bakke wrote: > FWIW if you control the hypervisor, you can send something along the > lines of: > > qemu -device virtio-rng-pci,bus=pci.0,addr=0x1e,max-bytes=1024,period=1000 > > to feed the guest with entropy from the host through virtio, up to

Re: Reducing default verbosity

Am 06.12.2017 um 11:21 schrieb Ludovic Courtès: > Leo Famulari skribis: > >> I'd prefer to keep the full build output as the default of `guix build`, >> and maybe `guix environment`. > Yes, maybe just ‘guix build’ if you ask me. +1 for ‘guix build’ only. "guix environment"

Re: Reducing default verbosity

Am 05.12.2017 um 14:33 schrieb Ricardo Wurmus: > What do you think? IMHO this would be a great improvement. -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |

Re: ISO image available for testing!

Ludovic Courtès wrote on 06/12/17 at 09:14: >> One solution would be to explicitly check build outputs for references >> to native-inputs, and to force a build failure in that case. I started a rudimentary PoC for this last week, after realising how bad the situation is in ghc-* alone. We'll see

Re: Reducing default verbosity

Leo Famulari skribis: > I'd prefer to keep the full build output as the default of `guix build`, > and maybe `guix environment`. Yes, maybe just ‘guix build’ if you ask me. Ludo’.

Re: Reducing default verbosity

Hello! Danny Milosavljevic skribis: > On Tue, 5 Dec 2017 14:33:01 +0100 > Ricardo Wurmus wrote: > >> * Reduce package downloads from three lines to one line. The >> “Downloading URL” line is only important when things go wrong. >> *

Re: Rust bootstraps via i686?

Hi Adam, On Mon, 04 Dec 2017 14:56:39 -0500 Adam Van Ymeren wrote: > Does anyone know why rust bootstraps itself from the i686 version of the > binaries even if you're running on x86_64? It's to cut down on the number of weird binary blobs we use. > If I can make it bootstrap

Re: FOSDEM 2018 and announcing a GNU Guix/Guile day!

From: Manolis Ragkousis Subject: Re: FOSDEM 2018 and announcing a GNU Guix/Guile day! Date: Tue, 5 Dec 2017 19:59:38 +0200 > If you are going to attend please add your name to the wiki, or just > respond to this email, so we can order enough lunches! I'm going to attend.

Re: ISO image available for testing!

Hi Mark, Mark H Weaver skribis: > l...@gnu.org (Ludovic Courtès) writes: >> 91c9b5d01 * packages: 'package-grafts' trims native inputs. > > [...] > >> Long story short: we were flagging native inputs as potential sources of >> grafts even though, by definition, native inputs

Re: ISO image available for testing!

I wrote: > One solution would be to explicitly check build outputs for references > to native-inputs, and to force a build failure in that case. More precisely, we could force a build failure when any build output contains a reference to a component (store path) in the following set: