unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Devan Carpenter <mail@dvn.me>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix build output insufficient
Date: Tue, 11 Sep 2018 13:59:44 +0200	[thread overview]
Message-ID: <20180911115944.nncttdqiqo74pl7v@kowloon> (raw)
In-Reply-To: <87lg88xqng.fsf@ambrevar.xyz>

[-- Attachment #1: Type: text/plain, Size: 840 bytes --]

Pierre Neidhardt transcribed 1.3K bytes:
> 
> > Also, on build failure, it would be nice to print a hint on what to
> > invoke to get to the failed build log after all (guix-daemon still wrote
> > it).
> 
> Indeed.  Is there such a command?
> 
> What about adding a hint, for instance:
> 
>  Building /gnu/store/i0kxn9cpkw8ml5472s185kxa6n64kmir-webkitgtk-2.20.5.drv - x86_64-linux
> +Saving log at /var/log/guix/i0/kxn9cpkw8ml5472s185kxa6n64kmir-webkitgtk-2.20.5.drv.bz2
>  starting phase `set-SOURCE-DATE-EPOCH'

I like this idea very much.

> This would be doubly useful:
> 
> - It makes it explicit to all users, without having to consult the manual or
> some `--help` message.
> 
> - With Eshell or M-x shell, we can directly find-file the log at point.
> 
> -- 
> Pierre Neidhardt
> https://ambrevar.xyz/



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-09-11 11:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11  8:26 Guix build output insufficient Pjotr Prins
2018-09-11  9:04 ` Pjotr Prins
2018-09-11  9:55   ` Danny Milosavljevic
2018-09-11 10:41     ` Pierre Neidhardt
2018-09-11 11:59       ` Devan Carpenter [this message]
2018-09-11 11:52 ` Ricardo Wurmus
2018-09-11 14:23   ` Danny Milosavljevic
2018-09-12  6:52     ` Ricardo Wurmus
2018-09-12 15:25       ` Pjotr Prins
2018-09-13  6:45         ` Pjotr Prins
2018-09-13  7:23           ` Ricardo Wurmus
2018-09-12 17:09   ` Ludovic Courtès
2018-09-12 17:25     ` Ricardo Wurmus
2018-09-12 17:34       ` Tobias Geerinckx-Rice
2018-09-12 17:42       ` Tobias Geerinckx-Rice
2018-09-12 17:52         ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180911115944.nncttdqiqo74pl7v@kowloon \
    --to=mail@dvn.me \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).