unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: guix-devel@gnu.org, 60227@debbugs.gnu.org
Subject: [bug#60227] guile-ssh 0.16 update
Date: Wed, 21 Dec 2022 23:38:46 +0100	[thread overview]
Message-ID: <87sfh82xhl.fsf_-_@gnu.org> (raw)
In-Reply-To: <87tu1py7q8.fsf@contorta> (Vagrant Cascadian's message of "Tue, 20 Dec 2022 15:29:35 -0800")

Howdy!

Vagrant Cascadian <vagrant@debian.org> skribis:

> Well, that is what I did, pulled guix to the curren wip-guile-ssh-0.16
> branch (which contains an update to guile-ssh 0.16 and updates guix to
> use a commit containing that), and managed to guix copy from one machine
> to another, so I *think* we are good!

As mentioned on IRC, I tested it with ‘GUIX_DAEMON_SOCKET=ssh://…’ and
‘guix copy’, and it all seems good.  So I think you can go ahead!

> Patch attached for the guile-ssh update. Once that lands in master we
> can consider updating guix to use it...

No need to update the ‘guix’ package, or am I missing something?  The
‘guix’ package depends on guile-ssh, so it’ll end up using the new
version anyway.

Thanks!

Ludo’.




      reply	other threads:[~2022-12-21 22:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87wn8jd680.fsf@contorta>
     [not found] ` <87tu3nd3im.fsf@contorta>
     [not found]   ` <87cza5vc9h.fsf@gnu.org>
     [not found]     ` <87mt7iwi16.fsf@contorta>
2022-12-20 23:29       ` guile-ssh 0.16 update Vagrant Cascadian
2022-12-21 22:38         ` Ludovic Courtès [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=87sfh82xhl.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=60227@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=vagrant@debian.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).