-
Notifications
You must be signed in to change notification settings - Fork 2.7k
"git svn fetch" hangs (perl.exe) #1993
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The same goes for "git svn rebase", "git svn dcommit" |
This bug report is very short. And very incomplete. |
Commands are running without any output at 100% CPU. |
Okay, here's the thing: So without substantially better (read: more complete, less terse, volunteering more rather than less) information, there is literally nothing whatsoever that could be done to help you guys, @CrOrc & @dex-ds. |
Here's output of
|
Perl is hanging busy at last command
|
Here's my config
|
Here's output of
|
In git v2.19.1 after that goes
|
Maybe helpful or not.. msys-serf-1-0.dll!serf__spnego_init_sec_context+0x518 |
my git svn traces looks like crOrcs ouput. Windows environment: |
I'm experiencing the same issues as the other people here, and see the same trace output. I can chase this rabbit all the way to this line in
I don't have the skills/time to go into Something else of interest: I'm behind a proxy. I don't know if any of the other reporters are too. |
I'm experiencing the same behavior for |
Almost same here. |
Same symptoms and log output here as well. |
I have the same issues on two different machines.
Now the actual log:
|
Same problem here. SVN repository is via https and requires username and password. 2.20.0 prompts to accept certificate (self signed). 2.20.1 doesn't prompt at all. |
Same here. I believe i've also accepted a git console prompt months ago (pre git 2.20.0) to add a permanent security exception for the certificate/connection, which was probably before adding the certificate to the windows cert store. |
I did a Wireshark trace and the network connection is created but no data
is sent, not even the SSL handshake.
…On Thu, Jan 24, 2019, 08:54 th3ragex ***@***.***> wrote:
Same here.
Windows 10 1607. The SVN repository requires username and password over
HTTPS. The HTTPS is encrypted a self signed certificate and gets tunneled
through a VPN connection to an internal network. The self signed
certificate has been (manually) added to the windows certificate store.
I *believe* i've also accepted a git console prompt months ago (pre git
2.20.0) to add a permanent security exception for the
certificate/connection, which was probably before adding the certificate to
the windows cert store.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1993 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGfltpbN-YeFXMLf55YRB3pJlmPjHlXOks5vGbsDgaJpZM4ZclWZ>
.
|
I faced the same issue, downgrading to 2.19.2 sorted it out Running on a Windows 10 1607. SVN lives on an HTTPs connection with a self signed certificate (not CA certified) |
Same issue with 2.20.1.
|
I have just recently run into this issue with git svn dcommit. I believe that the issue is in OpenSSL, see openssl/openssl#2865. Pulling in the OpenSSL fix should hopefully resolve this issue. |
I can confirm that |
Have you had chance to see what was in the 'minor' fix from 20.0 to 20.1? I have memories that suggest they were various cascaded networking library code fixes, which may give a better clue. |
I have confirmed that this is indeed related to openssl/openssl#2865. Pulling in the OpenSSL fix from openssl/openssl@ef45aa1 and also rebuilding the "serf" package, fixes my git svn problems. I guess there could be other packages that might also be impacted by this OpenSSL issue. |
@nga888 excellent work! So what will need to happen now:
I will obviously be stuck with the building and publishing, and I would really appreciate help with the other two tasks. |
Thanks and you're welcome @dscho I've actually been testing this in MSYS2 with git-for-windows, as that's my preferred setup. I have just created this pull request msys2/MSYS2-packages#1576 for the openssl patch. If it's accepted I guess you can merge it to your fork or you can just grab it directly if you want. |
Comes with [OpenSSL v1.1.1a](https://www.openssl.org/news/openssl-1.1.1-notes.html). Signed-off-by: Git for Windows Build Agent <[email protected]>
Most importantly libserf, which will hopefully address git-for-windows/git#1993... Signed-off-by: Johannes Schindelin <[email protected]>
Most importantly libserf, which will hopefully address git-for-windows/git#1993... Signed-off-by: Johannes Schindelin <[email protected]>
This was done by upstream MSYS2, so I avoided that for the time being. |
FWIW v2.21.0-rc2 has the proposed fix. Please, all y'all, test away. |
Thanks so much dscho! I tried "git svn clone" with v2.21.0-rc2 today and it seemed work well. Great! |
@llongmanne559 thanks for testing! |
on current 2.20.1 x64 portable. 2.20.0 runs fine...
cheers, ds
The text was updated successfully, but these errors were encountered: