Kei skribis:
> I've managed to get guix to build by running
>
> mount -t tmpfs tmp /tmp
>
> prior to building. I've tried it on two separate hard drives.
OK, good.
> Perhaps you can try and replicate my results?
No, I’d really need to know the answer to the questions
Andreas Enge skribis:
> Things work for me now, thanks for the help!
>
> However, I am still seeing this with latest git:
> substitute: updating list of substitutes from 'https://hydra.gnu.org'...
> 100.0%
>
> Should this not be https://mirror.hydra.gnu.org?
The daemon’s
I've managed to get guix to build by running
mount -t tmpfs tmp /tmp
prior to building. I've tried it on two separate hard drives.
Perhaps you can try and replicate my results?
Kei
"Thompson, David" skribis:
> If you run 'guix size perl' you will notice that, as of this writing,
> 138.2MiB of Perls' 307.6MiB closure is due to referencing gcc's
> default output in '/lib/perl5/5.22.1/x86_64-linux/Config_heavy.pl'.
> Perl's large closure inflates the
On Mon, Mar 21, 2016 at 10:29:51AM +0100, Ludovic Courtès wrote:
> Leo Famulari skribis:
>
> > * gnu/packages/tls.scm (openssl)[arguments]: Add #:disallowed-references.
>
> Sounds good! (And thanks for following commits closely. ;-))
>
> This should go to ‘core-updates’,
Florian Paul Schmidt writes:
> On 20.03.2016 20:56, myglc2 wrote:
>
>> - I did a near-identical install to a SSD (Kingston ssdnow300), see
>> "c06system-ssd.scm.log". If installed on the 1st server this shows
>> Guix welcome screen, loads the keyboard & mouse drivers,
If you run 'guix size perl' you will notice that, as of this writing,
138.2MiB of Perls' 307.6MiB closure is due to referencing gcc's
default output in '/lib/perl5/5.22.1/x86_64-linux/Config_heavy.pl'.
Perl's large closure inflates the closures of many other packages,
such as openssl.
Does anyone
Leo Famulari writes:
> On Sun, Mar 20, 2016 at 03:05:25PM +0100, Nils Gillmann wrote:
>> Previously reported GNOME bug solved after reconfiguring the
>> system with (services (gnome-desktop-service)).
>
> Okay, so the problem is solved then?
No, please read the full initial
Danny Milosavljevic skribis:
>> Sounds like postgresql died and shepherd did not notice? Or maybe it
>> keeps trying to respawn it? What did /var/log/shepherd.log say?
>
> 2016-03-19 10:34:48 Service postgres has been started.
> 2016-03-19 10:34:49 Respawning postgres.