unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Brice Waegeneire <brice@waegenei.re>
To: 41238-close@debbugs.gnu.org
Subject: bug#41238: guix deploy close ssh session after each store items sent
Date: Tue, 18 Jan 2022 08:08:51 +0100	[thread overview]
Message-ID: <871r15tta4.fsf@waegenei.re> (raw)
In-Reply-To: <0156447bb0d526cdfe42d51a154a2bd3@waegenei.re> (Brice Waegeneire's message of "Wed, 13 May 2020 16:32:55 +0000")

Hello Guix,

Brice Waegeneire <brice@waegenei.re> writes:

> “guix deploy” bugs; they keep coming! “guix deploy” doesn't make use of SSH
> channels[0], instead it close the SSH session each time after sending store
> items.

[...]

Ludo‘ fixed the issue with the commit 7f20e59a13a6acc3331e04185b8f1ed2538dcd0a.

For posterity, here is the workaround I was using a few month ago and is now
unecessary. The session filed needed to be manually set with a call to
"openssh-ssh-session" from (guix ssh):

--8<---------------cut here---------------start------------->8---
(machine-ssh-configuration
  (host-name "foo")
  (system "x86_64-linux")
  (session (open-ssh-session "foo" #:user "root"))
  (host-key "..."))
--8<---------------cut here---------------end--------------->8---

Currently the following suffice:

--8<---------------cut here---------------start------------->8---
(machine-ssh-configuration
  (host-name "foo")
  (system "x86_64-linux")
  (user "root") 
  (host-key "..."))
--8<---------------cut here---------------end--------------->8---

Cheers,
- Brice




      parent reply	other threads:[~2022-01-18  7:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 16:32 bug#41238: guix deploy close ssh session after each store items sent Brice Waegeneire
2020-05-15  6:59 ` Oleg Pykhalov
2020-05-15  7:46   ` Brice Waegeneire
2022-01-18  7:08 ` Brice Waegeneire [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=871r15tta4.fsf@waegenei.re \
    --to=brice@waegenei.re \
    --cc=41238-close@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 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).