From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 48240-done@debbugs.gnu.org
Subject: bug#48240: “guix copy” to host with daemon listening on TCP fails
Date: Sat, 08 May 2021 15:10:39 +0200 [thread overview]
Message-ID: <875yzt8j74.fsf@gnu.org> (raw)
In-Reply-To: <87a6p9rwu7.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 05 May 2021 18:04:16 +0200")
Hi,
Ricardo Wurmus <rekado@elephly.net> skribis:
> There are two hosts running Guix. The target host runs
> “guix-daemon” with “--listen=0.0.0.0:9999”; it does not listen on
> a local socket file. Trying to copy store items to the target
> host fails with this backtrace:
I pushed the four patches as 3270308eebe82075d2f02517c5a2b1599928495c.
Let me know if anything’s amiss!
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-05-08 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 16:04 bug#48240: “guix copy” to host with daemon listening on TCP fails Ricardo Wurmus
2021-05-05 21:32 ` bug#48240: [PATCH 1/4] store: 'open-connection' never returns #f Ludovic Courtès
2021-05-05 21:32 ` bug#48240: [PATCH 2/4] ssh: 'connect-to-remote-daemon' raises a nicer message upon error Ludovic Courtès
2021-05-05 21:32 ` bug#48240: [PATCH 3/4] store: Export 'connect-to-daemon' Ludovic Courtès
2021-05-05 21:32 ` bug#48240: [PATCH 4/4] ssh: Honor GUIX_DAEMON_SOCKET on the target machine Ludovic Courtès
2021-05-08 13:10 ` Ludovic Courtès [this message]
2021-05-11 8:43 ` bug#48240: “guix_ copy” to host with daemon listening on TCP fails Simon Streit
2021-05-11 9:56 ` bug#48240: “guix " Ludovic Courtès
2021-05-12 7:48 ` Simon Streit
2021-05-11 10:52 ` Ludovic Courtès
2021-05-11 14:01 ` Bone Baboon via Bug reports for GNU Guix
2021-05-11 21:22 ` Ludovic Courtès
2021-05-12 7:49 ` Simon Streit
2021-05-12 19:44 ` Simon Streit
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=875yzt8j74.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=48240-done@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).