From a6b0e8c7eacceedf10b3bc29132e78614deceefe Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 1 Feb 2021 12:40:30 -0400 Subject: [PATCH] comment --- ..._d8d2fa5af2ef2f7b4a59e1faa4f34a05._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/bugs/problems_with_SSH_and_relative_paths/comment_2_d8d2fa5af2ef2f7b4a59e1faa4f34a05._comment diff --git a/doc/bugs/problems_with_SSH_and_relative_paths/comment_2_d8d2fa5af2ef2f7b4a59e1faa4f34a05._comment b/doc/bugs/problems_with_SSH_and_relative_paths/comment_2_d8d2fa5af2ef2f7b4a59e1faa4f34a05._comment new file mode 100644 index 0000000000..120a8879a3 --- /dev/null +++ b/doc/bugs/problems_with_SSH_and_relative_paths/comment_2_d8d2fa5af2ef2f7b4a59e1faa4f34a05._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2021-02-01T16:34:33Z" + content=""" +I was going to say, I have repos with relative ssh paths that I use with +git-annex every day. + +This seems likely to be a problem with how git-annex +is installed on the server, that is preventing running git-annex-shell +there. Ie, it should work to run `ssh remote.example.com git-annex-shell`. + +Sometimees there can be tricky problems with PATH not getting set as usual +when sshing, see [[tips/get_git-annex-shell_into_PATH]]. + +I don't know how the absolute path could have seemed to work, and then +seemed to fail when you tried it again later. My guess would be, something +must have changed on the server in the meantime. +"""]]