unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: bug-guix@gnu.org
Subject: Re: Download progress interleaved with compile output
Date: Sun, 21 Apr 2013 11:59:18 +0200	[thread overview]
Message-ID: <878v4c5hmx.fsf@gnu.org> (raw)
In-Reply-To: <878v4cbcss.fsf@tines.lan> (Mark H. Weaver's message of "Sun, 21 Apr 2013 02:47:15 -0400")

Mark H Weaver <mhw@netris.org> skribis:

> I recently installed a large number of packages in a single "guix
> package -i" command, and in the resulting transcript I see download
> progress reports interleaved with compile output, e.g.:

[...]

> Is this intentional?

Well, clients make the ‘build-derivations’ RPC, which potentially
involves building several derivations, and the daemon returns the stderr
streams mixed.  So there’s not much that can be done without changing
the daemon and RPCs.

However, note that build logs are kept under $localstatedir.  That’s
what I use when needing to analyze logs.

Thanks,
Ludo’.

      reply	other threads:[~2013-04-21  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21  6:47 Download progress interleaved with compile output Mark H Weaver
2013-04-21  9:59 ` Ludovic Courtès [this message]

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=878v4c5hmx.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=mhw@netris.org \
    /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).