I think I have my Linux central repository set up correctly. I can pull and push from/to the repository on the Linux host itself. My problem is trying to push commits to that repository from windows. I keep getting "fatal: Could not read from remote repository." When I run 'ls' commands using plink from the command line it works fine with the same credentials. Clearly there is an issue with git on Windows and using SSH to access the remote repository. I'm stuck as to how to debug this. Can anyone point me in the right direction? TIA
threads / discuss / 32448
Push Windows to Linux Repository Problem
Subject: Push Windows to Linux Repository Problem
Re: Push Windows to Linux Repository Problem
Dennis Putnam <dap1@bellsouth.net> writes:
> I keep getting "fatal: Could not read from remote repository."
Can you "git ls-remote" the repository?
Andreas.
-- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Re: Push Windows to Linux Repository Problem
Hi Andreas,
Thanks for the reply and no, I could not. However, you put me on the right track. Since I was only pushing/pulling from Windows to/from my Linux repository, I did not realize that an SSH session from the Linux back to Windows would ever be necessary. I don't really understand why but apparently it is. I never set up that backwards connection. Once I did, everything started working.
On 12/23/2012 4:06 AM, Andreas Schwab wrote:
Show 7 quoted lines
> Dennis Putnam <dap1@bellsouth.net> writes: > >> I keep getting "fatal: Could not read from remote repository." > Can you "git ls-remote" the repository? > > Andreas. >
Re: Push Windows to Linux Repository Problem
----- Ursprungligt meddelande -----
Show 9 quoted lines
> Hi Andreas, > > Thanks for the reply and no, I could not. However, you put me on the > right track. Since I was only pushing/pulling from Windows to/from my > Linux repository, I did not realize that an SSH session from the > Linux > back to Windows would ever be necessary. I don't really understand > why > but apparently it is.
No. Git itself does not require a reverse connection of any kind. Maybe the Linux box checks that reverse lookup is set up for the client and refuses connection if reverse lookup of the connecting client's ip does not resolve to a hostname that in turn resolves back to the client's ip. If that is the case the server does not actually try to connect to the client with SSH or otherwise.
-- robin