From: 宋文武 <iyzsong@openmailbox.org>
To: 21888@debbugs.gnu.org
Subject: bug#21888: guix-publish gets ERROR when serve gtk+.
Date: Thu, 12 Nov 2015 12:41:04 +0800 [thread overview]
Message-ID: <3c53a2735955b91d3849beb2e2159947@openmailbox.org> (raw)
can't substitute gtk+ from a guix-publish server, it fails with:
GET /nar/1dlz1am0qmj1579f5p6j5cvfx9l2aw50-gtk+-3.18.2
In web/server/http.scm:
117:27 1 (http-read #<<http-server> socket: #<input-output: so...>)
In unknown file:
0 (peek-char #<input-output: socket 13>)
ERROR: In procedure fport_fill_input: Connection reset by peer
next reply other threads:[~2015-11-12 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 4:41 宋文武 [this message]
2015-11-12 20:28 ` bug#21888: guix-publish gets ERROR when serve gtk+ Ludovic Courtès
2015-11-13 5:21 ` 宋文武
2015-11-13 8:07 ` Ludovic Courtès
2015-11-13 12:05 ` 宋文武
2015-11-13 13:29 ` Ludovic Courtès
2015-11-13 14:17 ` Thompson, David
2016-06-08 17:09 ` Ludovic Courtès
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=3c53a2735955b91d3849beb2e2159947@openmailbox.org \
--to=iyzsong@openmailbox.org \
--cc=21888@debbugs.gnu.org \
--cc=iyzsong@member.fsf.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).