Thank you, Mr. Svenson. You made my morning a little less frustrating.
]]>http://git.hands.com/?p=ssh-copy-id.git … e2720657be
And peeking around in the openssh-portable distribution's history... https://github.com/openssh/openssh-port … 7ace3b64a3
"Updated to Phil Hands' greatly revised version"
So this is where they're syncing it from. It's not even from the openssh team, or developed by BSD affiliates. It's a contrib script specific to the portable edition, which openbsd itself relegates to a *port*.
]]>The lazy way would be to wait for it to be included from upstream in an upcoming version of the package. Though I am a bit concerned about this - from my perspective this seems like a glaring and ridiculously obvious error which is not to be expected from the development team behing this package. This makes me wonder if I am missing something about how this code may work on a BSD system but not linux ... though I highly doubt this as the flawed-syntax used should not be valid in any POSIX shell.
Another lazy way would be - as noted above - just don't use this script. I've always found the script a bit silly and mostly pointless. It doesn't do much that you couldn't do pretty easily without it. It's 300+ lines of (now flawed) shell script to do the same thing that one fairly simple ssh command can do (or one very very simple scp, plus one very very simple cat command on the server).
Maybe none of the openssh devs ever used the script! Since it's so silly and all.
]]>Sorry, but how do I use this?
The "right way" might be to retrieve the source code with abs, making the change, then rebuilding the package.
The smart way would just be to modify the installed file as it's just moving one closing parenthesis in a shell script.
The lazy way would be to wait for it to be included from upstream in an upcoming version of the package. Though I am a bit concerned about this - from my perspective this seems like a glaring and ridiculously obvious error which is not to be expected from the development team behing this package. This makes me wonder if I am missing something about how this code may work on a BSD system but not linux ... though I highly doubt this as the flawed-syntax used should not be valid in any POSIX shell.
Another lazy way would be - as noted above - just don't use this script. I've always found the script a bit silly and mostly pointless. It doesn't do much that you couldn't do pretty easily without it. It's 300+ lines of (now flawed) shell script to do the same thing that one fairly simple ssh command can do (or one very very simple scp, plus one very very simple cat command on the server).
]]>Hi
Sorry, but how do I use this?
]]>Thx all
Two sessions learned
1. My new system (currently building) will not have testing repo
2. I use scp instead of ssh-copy-id
Side note, you can have them enabled, but only for specific usages, unless you specify
[testing]
Include = /etc/pacman.d/mirrorlist
Usage = Sync Search
[community-testing]
Include = /etc/pacman.d/mirrorlist
Usage = Sync Search
[multilib-testing]
Include = /etc/pacman.d/mirrorlist
Usage = Sync Search
This appeared in Arch Planet at Dec 31 of 2019
Blog post: https://shibumi.dev/posts/my-pacman.conf-file
That way you can query and/or test install, avoiding everything bumping to testing versions
It IS also documented in `man pacman.conf`...
]]>this fix has work for me very well.
]]>Two sessions learned
1. My new system (currently building) will not have testing repo
2. I use scp instead of ssh-copy-id
That script code is completely different from the current - and seems quite broken.
]]>