Just installed, can’t create a new clone of the repository on the client machine

0
Hi, I’ve just installed GitStack on my Windows Server 2003 machine for some testing, everything went well and I’ve managed to browse to the admin web page without a hitch. I’ve created a repository, a user and a user group and I’ve associated the user group to the repository giving read and write permissions. I’ve then installed TortoiseGit and MsysGit on my Windows 7 client, once again no issues in there. When I go to clone the repository I’ve created on the server I get this error git.exe clone     –progress -v  “http://servername:88/demad.git” “C:\Users\username\Desktop\webdev\htdocs\mydev\demad” Cloning into ‘C:\Users\username\Desktop\webdev\htdocs\mydev\demad’… fatal: http://servername:88/demad.git/info/refs?service=git-upload-pack not found: did you run git update-server-info on the server? git did not exit cleanly (exit code 128) (18720 ms @ 06/12/2012 14:16:02) I can browse to the server web page from my client with no issue so far, I have other web services running on the same server and there are no firewall or security issues. I’ve found that a lot of people are having the same problem but no solution has been offered so far. I’ve seen a workaround posted at https://gitstack.com/questions/git-clone-fails-with-inforefs-not-found-did-you-run-git-update-server-info-on-the-server/#answer-1091, I’ve tried to add an empty file to the repository from the server but that didn’t help. I’ve also tried as suggested in other posts to add another user but that didn’t help either. I’ve tried to clone the repository from within server after having installed MsysGit but I have the same result. I appreciate if somebody can help before I uninstall everything and move on. Thanks
asked December 6, 2012

3 Answers

0
I have the exact same issue. It appears to have been asked before with no solution. I guess I'll move on to something else.
0
Do you get any error in C:/GitStack/apache/logs/error.log ?
0
Thanks. I looked into C:/GitStack/apache/logs/error.log and found that GitStack was looking for the repository in the wrong location although its settings said D:/Repositories (my custom location), GitStack looked for the repositories in its default location. So I simply went and save the settings again from GitStack admin page. It solved the problem.

Your Answer

Please login to post questions.