From: Leo Famulari <leo@famulari.name>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: "help-guix\\@gnu.org" <help-guix@gnu.org>
Subject: Re: guix pull errors
Date: Mon, 29 Mar 2021 12:50:30 -0400 [thread overview]
Message-ID: <YGIFVlm3G/m4CTBQ@jasmine.lan> (raw)
In-Reply-To: <c0tXE7wtUWosyRkv12GT3hWqmBdLYfxc21ja440WFCToCJf2JQUpylG-w7lzJrJ3JTFMltPj1yOXTxPYJOHgKduJ2XJ-tWSMpdvq8Xmv7bw=@elenq.tech>
On Sun, Mar 28, 2021 at 11:02:13PM +0000, Ekaitz Zarraga wrote:
> Hi,
>
> I'm getting tons of guix pull errors these days.
> They look like they are related with network issues because they
> disappear if I insist (many times) and they appear in different
> packages.
>
> They look like this:
>
> ```
> guix/ui.scm:2164:12: In procedure run-guix-command:
> Bad Read-Header-Line header: #<eof>
>
> substitution of /gnu/store/c39c4jhgg1pq3sw083pcmp42gba05kr2-evince-3.36.5 failed
> ```
>
> I'm finding them all the time.
>
> I think they are very cryptic... Maybe we can do something
> about that.
Have you updated your guix-daemon recently? This looks like some recent
bugs that have been fixed.
next prev parent reply other threads:[~2021-03-29 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 23:02 guix pull errors Ekaitz Zarraga
2021-03-29 16:50 ` Leo Famulari [this message]
2021-03-29 17:23 ` Ekaitz Zarraga
2021-03-29 18:52 ` Leo Famulari
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=YGIFVlm3G/m4CTBQ@jasmine.lan \
--to=leo@famulari.name \
--cc=ekaitz@elenq.tech \
--cc=help-guix@gnu.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.
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).