Avoid error about git-annex-shell not being found when syncing with -J with a git remote where git-annex-shell is not installed.

This commit was sponsored by andrea rota.

1 files changed, 27 insertions, 0 deletions

diff --git a/doc/bugs/bash__58___git-annex-shell__58___command_not_found/comment_1_461a8d85738d63f9d276bb33d5c24255._comment b/doc/bugs/bash__58___git-annex-shell__58___command_not_found/comment_1_461a8d85738d63f9d276bb33d5c24255._comment
new file mode 100644
index 000000000..fda3bdf3c
--- /dev/null
+++ b/doc/bugs/bash__58___git-annex-shell__58___command_not_found/comment_1_461a8d85738d63f9d276bb33d5c24255._comment
@@ -0,0 +1,27 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2017-06-06T16:21:53Z"
+ content="""
+One of the remotes of your repository is on a host
+where git-annex-shell is either not installed, or perhaps
+it is installed but `ssh thehost git-annex-shell` does not
+work -- eg due to the problem decribed in
+[[tips/get_git-annex-shell_into_PATH]].
+
+There was indeed a change in 6.20170519 that explains why this
+only happens in -J mode. [[!commit 6992fe133b37ec6d64498f3dd2c69613c4c37469]]
+made it run git-annex-shell at startup in that mode.
+
+Hmm, I suppose one of your remotes could intentionally not have
+git-annex-shell on it, and yet you'd still want `git annex sync`
+to work to it, and so this message about git-annex-shell
+being displayed is not ideal.
+
+So, I've made it skip trying to run git-annex-shell in this case unless
+the remote has an annex-uuid set. If the remote has never had
+git-annex-shell installed, it can't have an annex-uuid set.
+
+And, when it does fail to run git-annex-shell, I've made it say which 
+remote it was unable to run it on.
+"""]]