From 29d10fef0c608831eb6f7e40296616fe691b124c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 4 Feb 2015 14:37:49 -0400 Subject: [PATCH] comment --- ..._2a69ce8607f97aabdf3cc402c1091d7a._comment | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 doc/forum/Error_from_git-annex-shell_on_creation_of_gcrypt_special_remote/comment_1_2a69ce8607f97aabdf3cc402c1091d7a._comment diff --git a/doc/forum/Error_from_git-annex-shell_on_creation_of_gcrypt_special_remote/comment_1_2a69ce8607f97aabdf3cc402c1091d7a._comment b/doc/forum/Error_from_git-annex-shell_on_creation_of_gcrypt_special_remote/comment_1_2a69ce8607f97aabdf3cc402c1091d7a._comment new file mode 100644 index 0000000000..f94690b35a --- /dev/null +++ b/doc/forum/Error_from_git-annex-shell_on_creation_of_gcrypt_special_remote/comment_1_2a69ce8607f97aabdf3cc402c1091d7a._comment @@ -0,0 +1,30 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-02-04T18:09:49Z" + content=""" +It seems that some versions of git-shell will give this unhelpful +error message. Newer versions instead say +"fatal: Interactive git shell is not enabled." + +The initial push of the git-annex branch is not what failed. +It seems that the attempt to run "git-annex-shell gcryptsetup" +was what failed. + +My guess is that the remote server has an older version of git-annex +installed in /usr/bin, which doesn't understand the gcryptsetup +command, and that your newer installation of the standalone +version is not getting run when it sshes in. (A common problem; `~/.bashrc` +and `~/.bash_profile` are both ignored.) The old version of +git-annex-shell then passed the "gcryptsetup" command on to git-shell, +which I guess rejected it like that. (Not sure why.) + +git-annex seems to have successfully fallen back to using rsync to +configure the ssh://ma/meta/s/spw/local/annex repository's core.gcrypt-id. +(You might want to check that was set correctly.) + +Also, since it detected an old/not-working git-annex-shell on the remote, +it will have set git.remote.ma.gcrypt to "true", rather than +"shell", and this will cause git-annex to bypass using git-annex-shell +and instead use direct rsync. +"""]]