Re: git svn errors out with git-cat-file "usage" message

> Martin Langhoff wrote:
>> On Wed, Apr 29, 2009 at 11:05 PM, Michael J Gruber
>> <git@drmicha.warpmail.net> wrote:
>>> But I just re-read your original report, and there's some inconsistency:
>>>
>>> git-svn triggers cat-file's usage message which says "git-cat-file ...".
>>> The dash indicates that it is a git cat-file before v1.6.0.1-13-g34baebc
>>> (where the dash was removed), so it's definitely not the current maint
>>> you think you are using.
>>>
>>> Do you have older ubuntu git packages installed in $PATH?
>>
>> Bingo! Yes,
>>
>> ~$ which git-cat-file
>> /usr/bin/git-cat-file
>> ~$ /usr/bin/git version
>> git version 1.5.6.3
>>
>> now that's really weird. git from ~/bin is using git-cat-file from
>> /usr/bin instead of ~/libexec/git-core ... how is the libexec path set
>> in the PATH during the execution of the script?
>>
> 
> If you're executing "git-svn", the "git-svn" found first in your $PATH
> will be used. Same with "git" really, so if you have a $PATH like this:
> 
>   PATH=/usr/bin:$(HOME)/bin
> 
> you will always use the git from /usr/bin (naturally).

> 
>> the funny thing is that Ubuntu wants to have git-core in place if
>> you're rebuilding kernel packages. I don't need to rebuild my kernel
>> anymore but I am sure this is an issue for others. What's the trick?
>> Add the libexec/git-core to the PATH before /usr/bin? Should git
>> internally append libexec/git-core earlier in the search path?
>>
> 
> The possibly easiest solution to your particular problem is to just
> remove the files installed by the git-core package and then log out
> and back in (to clear any persistent shell cache). You may need to
> mark git-core as not updateable in your apt config.
>