Hi Maxim,
Maxim Cournoyer skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
> [...]
>
>> This looks good, and indeed it’s an unintended consequence of commit
>> cc1dfc202f2fefb6c2eb9467d1fc90a9154550c9.
>>
>> However, the log of commit cc1dfc had this:
>>
>>Failing to do that, "%p" would b
Hello!
l...@gnu.org (Ludovic Courtès) writes:
[...]
> This looks good, and indeed it’s an unintended consequence of commit
> cc1dfc202f2fefb6c2eb9467d1fc90a9154550c9.
>
> However, the log of commit cc1dfc had this:
>
>Failing to do that, "%p" would be "0" when using "ProxyCommand"
>in ~/
Hello,
Maxim Cournoyer skribis:
> From 942eb8cabef5b7c8b4425c765b6ee2ac9f529ad8 Mon Sep 17 00:00:00 2001
> From: Maxim Cournoyer
> Date: Sun, 4 Nov 2018 23:35:16 -0500
> Subject: [PATCH] Revert "copy: Default to port 22."
>
> This reverts commit cc1dfc202f2fefb6c2eb9467d1fc90a9154550c9. Specif
Hello,
I recently stumbled on the bug where guix copy would the port 22 even
when I had specified a different one in my ~/.ssh/config file.
This bug is triggered when omitting the port in the --to= (or --from)
expression, such as in
guix copy --to=somehost bash
And where somehost exists in ~/.s
