From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: offload: error: failed to connect to `#<input-output... Protocol error
Date: Mon, 28 Jan 2019 18:13:29 +0100 [thread overview]
Message-ID: <CAJ3okZ3WNVo+7QjYdV0FMtAPVhpdoOcL=0VTH=+QdjWXRJZu7g@mail.gmail.com> (raw)
In-Reply-To: <87y37b5qln.fsf@elephly.net>
Dear Matthew and Ricardo,
I have tried to update (guix pull) on the both machines, in user
profile and root profile.
Still the same error about connect.
If I understand well, it should come from the daemon? So how can I update it?
On the both machines, the version is:
guix-daemon (GNU Guix) 0.16.0-8.7ba2b27
The version configured in /etc/systemd/system/guix-daemon.service, then:
/var/guix/profiles/per-user/root/current-guix/bin/guix-daemon --version
Thank you for your insight.
All the best,
simon
prev parent reply other threads:[~2019-01-28 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 16:07 offload: error: failed to connect to `#<input-output... Protocol error zimoun
2019-01-21 21:56 ` Matthew Brooks
2019-01-22 14:00 ` zimoun
2019-01-23 15:41 ` Ricardo Wurmus
2019-01-28 17:13 ` zimoun [this message]
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='CAJ3okZ3WNVo+7QjYdV0FMtAPVhpdoOcL=0VTH=+QdjWXRJZu7g@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@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.
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).