diff options
author | 2015-02-04 14:37:49 -0400 | |
---|---|---|
committer | 2015-02-04 14:37:49 -0400 | |
commit | 81d3b4dfbaaca5d6baf259dca62e8bdb0e769fe8 (patch) | |
tree | 5cec24c48dadddf2d7da121524ac8c47bce7a4b6 | |
parent | 3e3cfb45e84593635037c07eaa4be16b1dfe7bf2 (diff) |
comment
-rw-r--r-- | doc/forum/Error_from_git-annex-shell_on_creation_of_gcrypt_special_remote/comment_1_2a69ce8607f97aabdf3cc402c1091d7a._comment | 30 |
1 files changed, 30 insertions, 0 deletions
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 000000000..f94690b35 --- /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. +"""]] |