From 1449629d5a27e8e95ce0194719c926febac55534 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sat, 6 Apr 2013 16:38:48 +0000 Subject: Added a comment --- .../comment_1_2143f0540fdcd7efeb25b5a3b54fe0fd._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_1_2143f0540fdcd7efeb25b5a3b54fe0fd._comment (limited to 'doc') diff --git a/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_1_2143f0540fdcd7efeb25b5a3b54fe0fd._comment b/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_1_2143f0540fdcd7efeb25b5a3b54fe0fd._comment new file mode 100644 index 000000000..aa8237c17 --- /dev/null +++ b/doc/bugs/Use_a_git_repository_on_the_server_don__39__t_work/comment_1_2143f0540fdcd7efeb25b5a3b54fe0fd._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 1" + date="2013-04-06T16:38:46Z" + content=""" +Well, it works here. It checks that all of `git`, `rsync`, and `git-annex` are in the path on the remote server using `which`. + +I think the most likely reason would be if you've installed git-annex on the remote server but not in the PATH. If you're using the standalone tarball, for example, it's \"installed\", but it has no way to find it. + +Or, you could have installed from cabal, which puts it in ~/.cabal/bin or ~/bin or something like that, and perhaps you configured your shell to put that directory in the PATH, but you did it in a way that only works for login shells. If you set the PATH in `~/.bashrc`, for example, that would not work for a noninteractive shell. +"""]] -- cgit v1.2.3