Re: Messed up windows installation of git-cola

[David Aguilar]

On Wed, Nov 28, 2012 at 7:28 PM, Tobias Reese
<tobias...@googlemail.com> wrote:
> Hi,
>
> i tried git cola on windows a few days ago and everything was running
> smothly. But now something was messed up.
> Everytime i interact with a remote the gui shows me the "updating" dialog
> forever. Having a look at the process list
> it gives me (for a fetch):
> - git.exe -> git fetch --verbose origin
> - ssh.exe -> ssh myu...@mygit.com "git-uload-pack '/mygit.git'"
>
> Invoking these commands on the shell work fine. Git from the shell in
> generall works without problems.
> Since my ssh key is password protected i have to provide a passphrase. My
> guess is that this happens at the
> point where i have to provide my password (but no proof of this).

If you are launching git-cola from the shell you can
use something like plink.exe and pageant.exe to serve as
your ssh agent.

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

git can be told to use plink.exe by setting the GIT_SSH variable.

These two pages touch on how to setup git to use putty, plink, and pageant
together:

http://www.mainelydesign.com/blog/view/git-plink-for-ssh-on-windows

http://nathanj.github.com/gitguide/tour.html

The GIT_SSH setup done there is automatically picked up by git-cola.
pageant is what you use to load your keys. It will ask for your
password as needed.

> I guess to hunt this problem down this is to little information. Is there
> any way to actually debug git-cola?

If you wanna hack on it then your best bet is cloning the github repo,
going in there, and running win32/cola.

It defaults to using pythonw.exe, which disconnects the terminal
from the process' stdin, so git will hang waiting for a password
when no ssh agent is in use.

If you change that to python.exe it should stay connected to your terminal,
so that when you do remote git stuff you can at least enter your password
at the bash shell. but the real fix is using an ssh agent, I think.
--
David