Here's the output after setting those environment params... *Server side* F:\git>set GIT_TRACE_PACKET=1 F:\git>set GIT_TRACE=1 F:\git>git daemon --verbose --port=9419 --export-all --base-path=F:\git trace: exec: 'git-daemon' '--verbose' '--port=9419' '--export-all' '--base-path=F:\git' trace: run_command: 'git-daemon' '--verbose' '--port=9419' '--export-all' '--base-path=F:\git' [11200] Ready to rumble trace: run_command: 'C:\Git\libexec\git-core\git-daemon.exe' '--serve' '--verbose' '--port=9419' '--export-all' '--base-path=F:\git' [19100] Connection from [::1]:52256 fatal: protocol error: bad line length character: ▬♥☺
*Client side* F:\git>set GIT_TRACE_PACKET=1 F:\git>set GIT_TRACE=1 F:\git>git clone git://localhost:9419/test.git test2 trace: built-in: git 'clone' 'git://localhost:9419/test.git' 'test2' Cloning into 'test2'... trace: run_command: 'git-remote-https' 'origin' 'https://localhost:9419/test.git' fatal: unable to access 'https://localhost:9419/test.git/': Unknown SSL protocol error in connection to localhost:9419 On Thursday, June 12, 2014 11:42:34 AM UTC-4, Thomas Braun wrote: > > Am 11.06.2014 19:30, schrieb Clinton Parham: > > F:\git>git --version > > git version 1.9.2.msysgit.0 > > > > Thanks. > > > > On Wednesday, June 11, 2014 2:21:09 AM UTC-4, Thomas Ferris Nicolaisen > > wrote: > > > > Just occurred to me that I left some relevant pieces out in my > > quoting. Here's the whole original message (also available at [1]): > > > > On Monday, June 9, 2014 9:52:44 PM UTC+2, Clinton Parham wrote: > > > > Hello git users, > > > > I'm trying to run a git server on my Windows 7 workstation. I've > > downloaded the Windows installer > > from http://git-scm.com/downloads > > <http://git-scm.com/downloads> and I'm able to clone other > > repositories. > > > > Now I want to allow others to clone my repositories. But when > > testing my setup, I get these errors (both client and server are > > on the same box): > > > > _Client side:_ > > > > F:\git>git clone git://localhost:9419/test.git test2 > > Cloning into 'test2'... > > fatal: unable to access 'https://localhost:9419/test.git/ > > <https://localhost:9419/test.git/>': Unknown SSL protocol > > error in connection to localhost:9419 > > > > _Server side:_ > > > > F:\git>git daemon --verbose --port=9419 --export-all > > --base-path=F:\git > > [15452] Ready to rumble > > [11552] Connection from [::1]:51952 > > fatal: protocol error: bad line length character: ▬♥☺ > > > > > > _I setup the test.git repo like this:_ > > > > F:\>git --version > > git version 1.9.2.msysgit.0 > > > > > > F:\>cd git > > F:\git>mkdir test.git > > F:\git>cd test.git > > F:\git\test.git>git init --bare > > Initialized empty Git repository in F:/git/test.git/ > > > > F:\git\test.git>cd .. > > F:\git> > > > > > > Anyone had luck with this approach? > > > > > > > > I also fired up a Windows VM to see if it works: > > > > git version 1.7.10.msysgit.1 > > > > Server side: > > > > C:\git>git daemon --verbose --port=9419 --export-all > --base-path=C:\git > > [10816] Ready to rumble > > [8692] Connection from 127.0.0.1:3472 <http://127.0.0.1:3472> > > [8692] Extended attributes (21 bytes) exist <host=localhost:9419> > > [8692] Request upload-pack for '/agnes.git' > > > > Client side: > > > > c:\git>git clone git://localhost:9419/agnes.git test2 > > Cloning into 'test2'... > > remote: Counting objects: 852, done. > > Receiving objects: 100% (852/852), 114.14 KiB, done. objects: 86% > > (733/852) > > Resolving deltas: 100% (461/461), done.458) esolving deltas: 100% > > (461/461) > > remote: Compressing objects: 100% (458/458), done. > > remote: Total 852 (delta 461), reused 666 (delta 318) > > > > After upgrading to git version 1.9.2.msysgit.0, I get the same > > behavior on the server side as before, but oddly enough this on the > > client side: > > > > c:\git>git clone git://localhost:9419/agnes.git test3 > > Cloning into 'test3'... > > remote: Counting objects: 852, done. > > remote: Compressing objects: 100% (458/458), done. > > fatal: read error: Invalid argument > > fatal: early EOF > > fatal: index-pack failed > > > > So, I seem to be running into another issue, reported a couple of > > weeks ago [2]. > > > > Clinton, can you share which version of Git you have installed? (git > > --version, without cygwin please, just in normal Git for Windows). > > You wrote that you downloaded and installed from the homepage, but > > not when. > > > > Would be great if someone else could quickly check if this is > > working for their local versions. > > > > [1] > https://groups.google.com/d/topic/git-users/Xh4XfAALBLc/discussion > > <https://groups.google.com/d/topic/git-users/Xh4XfAALBLc/discussion> > > > [2] https://groups.google.com/d/msg/msysgit/B2HgjzhdobI/nStjWxumwUIJ > > <https://groups.google.com/d/msg/msysgit/B2HgjzhdobI/nStjWxumwUIJ> > > You might also want to set > export GIT_TRACE_PACKET=1 > export GIT_TRACE=1 > as this outputs some more information. > > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
