mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

theory

Browse source
This commit is contained in:
Joey Hess 2014-11-04 17:42:24 -04:00
parent 46f1337882
commit deee74ff6d
1 changed files with 34 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
doc/bugs/git_annex_sync_thinks_remote__39__s_name_is_a_command/comment_3_c7f9b400336b29587b26a161041e7980._comment Normal file
View file

@ -0,0 +1,34 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2014-11-04T21:21:16Z"
content="""
From the debug output, it's apparently `git fetch origin` (and also the `git
push origin`) that is, somehow, resuting in the error message.
But, I'll bet it doesn't happen if you run `git fetch origin` by hand, does
it?
My best guess is that this is somehow related to the ssh connection
caching code. To make ssh connection caching work, git-annex sets
`GIT_SSH=git-annex`. This would result in `git fetch` running `git annex i3`
as we see here, but with some environment variables set that would make
git-annex know that it's supposed to be handling a ssh caching scenario.
Perhaps you have a really old version of git-annex, that doesn't know about
that ssh caching environment, installed someplace, in addition to the more
recent version that's in you path. If the old version somehow gets run by
git, it would explain this behavior.
To check this theory, first try disabling ssh caching temporarily, and see if
that avoids the problem:
git config annex.sshcaching false
git annex sync
git config annex.sshcaching true
If that did avoid the problem, take a look at
`~/.config/git-annex/program`. It probably points to the location of an old
version of git-annex. Likely one installed from the standalone tarball.
Removing that file would then solve your problem.
"""]]