On Thu, Dec 20, 2012 at 12:08 PM, Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote:
Are you able to run `git init`, `git clone` `git fetch`? > If they fail, then how? (Please, cite the full error output). > > Well, none of the man pages work (which is an annoyance, but not the end of the world). I've set up an env var for GIT_EXEC_PATH and GIT_TEMPLATE_PATH to point to the correct locations, but when I try `git clone`, I get the following: [eric git]$ git clone https://e...@git.assembla.com/myproj.git Cloning into 'myproj'... Password for 'https://e...@git.assembla.com': error: RPC failed; result=22, HTTP code = 401 fatal: The remote end hung up unexpectedly In all fairness, I do not know if that is due to my package being installed under my home dir vs standard dirs, or if there is a firewall issue/etc, but I can confirm that a clone to that repo works properly on another system. Similarly, I can confirm that I can d/l data from other https sites without issues. I would install CentOS 5.5 somewhere (on a virtual machine for > instance), install the necessary developer tools there and then built > Git from the source configuring it to use /home/you/git as its "PREFIX". > Then install it (on the build machine, I mean) using something like > Sure - I was trying to avoid that effort, so was hoping that there would be some other way(s) to specify the required paths. Thanks, Eric --
