basename, sed, and tr not found while attempting pull

[Todd Marek]

Hello,

I'm running into an issue when I try to pull using SourceTree 1.6.1 on Mac OS X Lion. I receive the following errors:

/Applications/SourceTree.app/Contents/Resources/git_local/libexec/git-core/git-sh-setup: line 77: basename: command not found

/Applications/SourceTree.app/Contents/Resources/git_local/libexec/git-core/git-sh-setup: line 77: sed: command not found

/Applications/SourceTree.app/Contents/Resources/git_local/libexec/git-core/git-sh-setup: line 222: uname: command not found

Each of the requested commandline apps are found on my system in /usr/bin (confirmed with which basename etc..).

Has anyone run across this problem, and if so how did you resolve it?

Thanks.

[Todd Marek · Accepted solution]

Thanks for the help Steve. I have checked my .profile file and can't seem to locate anything out of the ordinary. My PATH always seems to end up including /usr/bin. I'm just using the absolute paths for now. It seems to have remedied the problem.

[akshay sharma]

hey Marek. Pls post the answer here as well. I am also facing same issue while using intelliJ

[stevestreeting]

The only way this could happen is if the PATH for Mac OS apps had been altered so that it no longer included /usr/bin. Note that the PATH that full .apps see is separate to that you see in a terminal.

The PATH is usually built up for .apps from the contents of /etc/paths and any files in /etc/paths.d. The contents of /etc/paths should be something like this on a standard install of OS X:

/usr/bin
/bin
/usr/sbin
/sbin
/usr/local/bin

I can only assume that this file has been changed so that the standard paths aren't there any more?

[Todd Marek]

Hi Steve,

Thanks for the reply. I looked in /etc/paths and I ahve the standard:

/usr/bin
/bin
/usr/sbin
/sbin
/usr/local/bin

The only file in /etc/paths.d is titled 50-X11 and contains just the following:

/usr/X11/bin

To your knowledge, are there any other places that apps draw on in constructing their path?

I have currently modified the .sh files that were effected by the error to include the full paths to the commands so I can continue to work, but am curious what could be casuing the errors.

Thanks once again for your insight.

Todd

[stevestreeting]

Hmm, no, that's the standard locations and that appears to be in order. I guess it would be worth checking your .profile just in case there's something there which is overriding the PATH, because actually the problem is not with the *direct* call that SourceTree makes, but with the nested calls that git is making, and if that has gone through /bin/sh then it would have read your ~/.profile file - so if that's overwriting your PATH then that could be a contender.