all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: "56709@debbugs.gnu.org" <56709@debbugs.gnu.org>
Subject: bug#56709: (No Subject)
Date: Sun, 15 Jan 2023 19:39:20 +0000	[thread overview]
Message-ID: <610yEbWhgyGIyNvrPOjggP59PuF7-ASX75H3pSs6h4k1vG1jtWvvQk2dLZ6prY0UkKhPm9vDjRm8FVbx_kCgrmvfK4y0QQyhMLd1iszdNCI=@lendvai.name> (raw)
In-Reply-To: <W0xF5oJft-01oMoYVba5fIcGke1ZVp9yJYKwmRq3rVUmD8y6PipTrtKHMdecx5FQG_nRIK6l4e2H5P49xQptdDPJmAsy-GS6zVtk2YJRKrY=@lendvai.name>

> > i'm also seeing this, and the solution was to comment
> > out the (identity ...) field of my machine-ssh-configuration.
> 
>
> i spoke too soon. today it's again broken for me the same way, even
> though identity is commented out. lechner on IRC also reported that
> it's broken for him.


since then it's working again. this seems to be some transient issue. possibly related to network state?

note that normal SSH always works. it's only a late phase of `guix deploy` where this error sometimes shows up.

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“The most urgent necessity is, not that the State should teach, but that it should allow education. All monopolies are detestable, but the worst of all is the monopoly of education.”
	— Frédéric Bastiat (1801–1850), 'What Is Money?'





  reply	other threads:[~2023-01-15 19:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 19:26 bug#56709: Channel opening failure with guix deploy Aleksandr Vityazev
2022-12-22  1:31 ` bug#56709: (No Subject) Attila Lendvai
2022-12-23  0:41   ` Attila Lendvai
2023-01-15 19:39     ` Attila Lendvai [this message]
2023-01-18 20:49 ` bug#56709: Channel opening failure with guix deploy Thompson, David

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='610yEbWhgyGIyNvrPOjggP59PuF7-ASX75H3pSs6h4k1vG1jtWvvQk2dLZ6prY0UkKhPm9vDjRm8FVbx_kCgrmvfK4y0QQyhMLd1iszdNCI=@lendvai.name' \
    --to=attila@lendvai.name \
    --cc=56709@debbugs.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.