From 544eaff1e1c8e9e12a5bb4ec544610316e82f4ab Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 18 Feb 2022 12:10:55 -0400 Subject: [PATCH] comment --- ..._fcb4b6a62bcee4d2f70c58fb7f270b7a._comment | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/bugs/Failed_move__47__get_over_ssh_in_new_version/comment_3_fcb4b6a62bcee4d2f70c58fb7f270b7a._comment diff --git a/doc/bugs/Failed_move__47__get_over_ssh_in_new_version/comment_3_fcb4b6a62bcee4d2f70c58fb7f270b7a._comment b/doc/bugs/Failed_move__47__get_over_ssh_in_new_version/comment_3_fcb4b6a62bcee4d2f70c58fb7f270b7a._comment new file mode 100644 index 0000000000..ee324fa18f --- /dev/null +++ b/doc/bugs/Failed_move__47__get_over_ssh_in_new_version/comment_3_fcb4b6a62bcee4d2f70c58fb7f270b7a._comment @@ -0,0 +1,23 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2022-02-18T15:58:51Z" + content=""" +@ycp it is very possible that you also have an older version of git-annex +installed on the server, in such a way that the newer version is in PATH +when you log in interactively, but the older version is when you log in +non-interactively. + +See + +Note that "Run with no arguments or with -c cmd" is not a git-annex +message. It is a message output by git-shell, eg: + +> git-shell -c p2pstdio foo +> fatal: Run with no arguments or with -c cmd + +This probably means that git-annex-shell, not understanding the "p2pstdio" +command, has passed it on to git-shell, which failed like that. Which hints +very strongly that you do indeed have an old git-annex-shell in PATH at +that point. +"""]] -- 2.30.2