From 61f30ff452ba3b5a9b3f95e821941136b8c5de06 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 9 Aug 2015 17:18:04 -0400 Subject: [PATCH] document a PATH issue --- ..._35e5d9b427963fc7b9618eb522bd1273._comment | 10 ++++++++++ doc/install/NixOS.mdwn | 19 +++++++++++++++++++ 2 files changed, 29 insertions(+) create mode 100644 doc/forum/Remote__39__s_git-annex-shell_not_detected/comment_2_35e5d9b427963fc7b9618eb522bd1273._comment diff --git a/doc/forum/Remote__39__s_git-annex-shell_not_detected/comment_2_35e5d9b427963fc7b9618eb522bd1273._comment b/doc/forum/Remote__39__s_git-annex-shell_not_detected/comment_2_35e5d9b427963fc7b9618eb522bd1273._comment new file mode 100644 index 0000000000..6e37bdb4e0 --- /dev/null +++ b/doc/forum/Remote__39__s_git-annex-shell_not_detected/comment_2_35e5d9b427963fc7b9618eb522bd1273._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2015-08-09T21:20:05Z" + content=""" +Another way to deal with the problem is to find the location where +git-annex-shell is installed on the remote system's Nix store, and +configure the git remote for that system to use that location, by setting +`remote..annex-shell` in its git configuration. +"""]] diff --git a/doc/install/NixOS.mdwn b/doc/install/NixOS.mdwn index e9730b2856..23d7a99312 100644 --- a/doc/install/NixOS.mdwn +++ b/doc/install/NixOS.mdwn @@ -8,3 +8,22 @@ When including it in a NixOS configuration.nix file, the name of the reference t The build status of the package within Nix can be seen on the [Hydra Build Farm](http://hydra.nixos.org/job/nixpkgs/trunk/gitAndTools.gitAnnex). + +---- + +If git-annex is installed using Nix on a non-NixOS system, note that +git-annex-shell will not be available in PATH if git-annex tries to ssh +into the system and run it. This is because bash is typically built +without the flag `-DSSH_SOURCE_BASHRC`, and so the .bashrc that sets up the +PATH to include Nix-installed packages is not read. + +This is not a problem when using NixOS, because it does build bash with +that flag. Nor is this a problem when using git-annex locally. +But, if you're setting up a server that will be used as a git +remote, you'll need to find a way to get git-annex-shell +into the PATH, or otherwise deal with this. + +Another way to deal with the problem is to find the location where +git-annex-shell is installed on the remote system, and configure the git +remote for that system to use that location, by setting +`remote..annex-shell` in its git configuration.