ng0 writes:
> did we ever talk about that there's too little information on how to get
> the current log file of a failed build? I need this right now (the full log)
> and I can't remember how, and making use of the log folder in var/log/guix/
> won't
> help either.
The daemon doesn’t keep log
Hello,
Ricardo Wurmus skribis:
> under “guix/scripts” there are a couple of tools that are really useful,
> such as “guix challenge”. While they are great for the command line,
> I’d really like to use them from within Guile.
>
> Using “(guix-challenge)” directly is cumbersome, because I need t
ng0 writes:
> did we ever talk about that there's too little information on how to get
> the current log file of a failed build? I need this right now (the full log)
> and I can't remember how, and making use of the log folder in var/log/guix/
> won't
> help either.
Why won't /var/log/guix help
Sorry about the mail floundering, hopefully this is better.
>From 2486f55a177b3f62509fd999e5d5cbd072d5ce17 Mon Sep 17 00:00:00 2001
From: Alex ter Weele
Date: Wed, 7 Mar 2018 18:28:24 -0600
Subject: [PATCH 1/4] gnu: Add ghc-aeson-1.1.2.0.
* gnu/packages/idris.scm (ghc-aeson-1.1.2.0): New variabl
Hartmut Goebel writes:
> Am 09.03.2018 um 15:06 schrieb ng0:
>> The daemon doesn’t keep logs for failed builds.
>
> I asked this a few month ago and was told this is a bug.
I think it would be great to create a bug report.
Hartmut Goebel transcribed 332 bytes:
> Am 09.03.2018 um 15:06 schrieb ng0:
> > The daemon doesn’t keep logs for failed builds.
>
> I asked this a few month ago and was told this is a bug.
>
> --
> Regards
> Hartmut Goebel
>
> | Hartmut Goebel | h.goe...@crazy-compilers.com
Am 09.03.2018 um 15:06 schrieb ng0:
> The daemon doesn’t keep logs for failed builds.
I asked this a few month ago and was told this is a bug.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goe...@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thoug
Clément Lassieur transcribed 766 bytes:
> ng0 writes:
>
> > Ricardo Wurmus transcribed 358 bytes:
> >>
> >> ng0 writes:
> >>
> >> > did we ever talk about that there's too little information on how to get
> >> > the current log file of a failed build? I need this right now (the full
> >> > lo
ng0 writes:
> Ricardo Wurmus transcribed 358 bytes:
>>
>> ng0 writes:
>>
>> > did we ever talk about that there's too little information on how to get
>> > the current log file of a failed build? I need this right now (the full
>> > log)
>> > and I can't remember how, and making use of the lo
Ricardo Wurmus transcribed 358 bytes:
>
> ng0 writes:
>
> > did we ever talk about that there's too little information on how to get
> > the current log file of a failed build? I need this right now (the full log)
> > and I can't remember how, and making use of the log folder in var/log/guix/
>
Hi Aakanksha,
> I'm interested in working on the project "Improve the user experience
> for Guix package".
Thanks for your interest in Guix!
> I know C/C++ fair enough, I have experience working with GIT too.
Excellent! Some familiarity with C++ will come in handy. Most of Guix
is written in
Hi,
did we ever talk about that there's too little information on how to get
the current log file of a failed build? I need this right now (the full log)
and I can't remember how, and making use of the log folder in var/log/guix/
won't
help either.
--
A88C8ADD129828D7EAC02E52E22F9BBFEE348588
ht
12 matches
Mail list logo
