From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 60227-done@debbugs.gnu.org, guix-devel@gnu.org
Subject: Re: bug#60227: guile-ssh 0.16 update
Date: Wed, 21 Dec 2022 22:56:37 -0800 [thread overview]
Message-ID: <87zgbg6i56.fsf@contorta> (raw)
In-Reply-To: <87sfh82xhl.fsf_-_@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
On 2022-12-21, Ludovic Courtès wrote:
> 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!
Ok, pushed as 0744540d09ddef8dbf25cc5d65da9d029dab338c.
>> 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.
Probably (clearly?) just me overthinking it and somehow... guix builds
with the inputs from the guix commit defined in the guix package, not
just as the source code for the guix package built with the currently
defined guix inputs to using the guix build tool... guix building guix
with guix and with guix defining the guix inputs... to alleviate risk of
casuing any genuine (further) confusion...
I'll trust your judgement here!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2022-12-22 7:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 20:49 guile-ssh and libssh updates Vagrant Cascadian
2022-10-28 21:47 ` Vagrant Cascadian
2022-10-28 22:55 ` Vagrant Cascadian
2022-11-02 11:14 ` Ludovic Courtès
2022-12-11 20:15 ` Vagrant Cascadian
2022-12-20 9:17 ` guile-ssh 0.16 update (was Re: guile-ssh and libssh updates) Vagrant Cascadian
2022-12-20 23:29 ` guile-ssh 0.16 update Vagrant Cascadian
2022-12-21 22:38 ` [bug#60227] " Ludovic Courtès
2022-12-22 6:56 ` Vagrant Cascadian [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=87zgbg6i56.fsf@contorta \
--to=vagrant@debian.org \
--cc=60227-done@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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).