From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 35877@debbugs.gnu.org
Subject: bug#35877: guix pull extremely verbose (with no ----verbose)
Date: Fri, 24 May 2019 18:43:30 +0200 [thread overview]
Message-ID: <87ef4nsszx.fsf@gnu.org> (raw)
In-Reply-To: <87r28ofjz1.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 24 May 2019 08:24:34 +0200")
Hi Ricardo,
Ricardo Wurmus <rekado@elephly.net> skribis:
> I can now also reproduce this on a foreign distro. This only happens
> with “guix pull” (not with “guix package”) and with a newer daemon
> (which I didn’t have previously).
>
> When building things “guix pull” prints the full build log interspersed
> with tags like “@ build-log 22902 23”.
This happens when ‘compute-guix-derivation’ has to build things: it
inherits the client-provided settings such as the “multiplexed build
output” option, but its output goes straight to stderr without any
processing.
The right thing would be to consume its stderr, which might be tricky,
or to just hide it.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2019-05-24 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r28p5u8d.fsf@roquette.mug.biscuolo.net>
[not found] ` <87d0k9gsol.fsf@elephly.net>
[not found] ` <87o93t5isc.fsf@roquette.mug.biscuolo.net>
2019-05-24 6:24 ` guix pull extremely verbose (with no ----verbose) Ricardo Wurmus
2019-05-24 7:38 ` bug#35877: " Giovanni Biscuolo
2019-05-24 13:35 ` bug#35877: [Giovanni Biscuolo] " Giovanni Biscuolo
2019-05-24 16:43 ` Ludovic Courtès [this message]
2019-05-24 14:26 ` bug#35877: " Giovanni Biscuolo
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=87ef4nsszx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35877@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).