Re: Cloning remotely under git for Windows not working
- From
- Erik Cervin Edin <erik@cervined.in>
- Date
- Oct 20, 2022, 20:29 UTC
- Message-ID
- <CA+JQ7M_hE66XiBc4G7nXJMWpdOBWEm+Zp_74LcXQSOD8fo9LJw@mail.gmail.com>
- In-Reply-To
- <CA+JQ7M-NA9UYafMurb9MAo5bp6djdzRP7ChAbdmzU+nmrkXTNw@mail.gmail.com>
sorry, forgot reply all
On Thu, Oct 20, 2022 at 6:04 PM W. Ekkehard Blanz <ekkehard.blanz@gmail.com> wrote:
Show 6 quoted lines
> > $ git clone 10.0.7.181:D:\gitDepot\test.git > Cloning into 'test'... > username@10.0.7.181's password: > fatal: ''D:\gitDepot\test.git'' does not appear to be a git repository > fatal: Could not read from remote repository.
Any interesting information if you run with GIT_TRACE=1 git clone ... or any of the other debugging flags? https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables
I recall having a difficult time when I hosted a repository on windows a while back. Not exact specifics but that I ran into issues. Maybe because of some default windows things. Like the default terminal and/or the default ssh client.
Maybe something along the lines in this stackoverflow post https://stackoverflow.com/a/67937630/1507124 It mentions the following issue https://github.com/PowerShell/Win32-OpenSSH/issues/752 and the workaround is setting receive/uploadpack to use powershell. I distinctly recall facing this issue and I believe I solved it the same way, changing the default ssh shell to PowerShell instead of cmd. Not sure if it solves your issue but I think it helped me.
I'm also pretty sure that another time I tried setting mingw-bash as the ssh shell and then faced another issue related to mingw/windows path quoting shenanigans