unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 34209@debbugs.gnu.org
Subject: bug#34209: guix --version: ERROR: In procedure display: In procedure fport_write: Broken pipe
Date: Sun, 27 Jan 2019 18:57:08 +0100	[thread overview]
Message-ID: <87imyarnkb.fsf@elephly.net> (raw)
In-Reply-To: <87d0ojlmb5.fsf@ambrevar.xyz>


Pierre Neidhardt <mail@ambrevar.xyz> writes:

> In Bash:
> --8<---------------cut here---------------start------------->8---
> $ guix --version | awk '{print $4; exit}'
> Backtrace:
>            5 (primitive-load "/home/ambrevar/.config/guix/current/bin/guix")
> In guix/ui.scm:
>     464:2  4 (show-version-and-exit _)
> In ice-9/format.scm:
>   1590:19  3 (format #t "Copyright ~a 2019 ~a" "(C)" "the Guix authors\n")
>    261:19  2 (format:format-work "Copyright ~a 2019 ~a" ("(C)" "the Guix authors\n"))
>     70:10  1 (format:out-obj-padded _ _ _ _)
> In unknown file:
>            0 (display "the Guix authors\n" #<output: file 1>)
>
> ERROR: In procedure display:
> In procedure fport_write: Broken pipe
> --8<---------------cut here---------------end--------------->8---

This happens because awk closes the stream while we’re writing to it.
We could wrap the things in “run-guix” in (leave-on-EPIPE …).

Or we tell Guix not to ignore SIGPIPE.

See also https://issues.guix.info/issue/29826.

--
Ricardo

  reply	other threads:[~2019-01-27 19:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26 16:31 bug#34209: guix --version: ERROR: In procedure display: In procedure fport_write: Broken pipe Pierre Neidhardt
2019-01-27 17:57 ` Ricardo Wurmus [this message]
2019-01-27 17:57 ` 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=87imyarnkb.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=34209@debbugs.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).