-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
git svn broken in git version 2.33.0.windows.2 #3392
git svn broken in git version 2.33.0.windows.2 #3392
Comments
I'm experiencing the same issue. Only thing I have to add is that it still worked for me with 2.33.0.windows.1 |
I can reproduce, but I am a bit stretched. Could I ask you to help identify the root cause e.g. by testing the Aug 23 snapshot (i.e. the snapshot between v2.33.0 and v2.33.0(2))? And maybe even try to identify the exact file(s) that need to be replaced in v2.33.0(2) to fix it (I would do that by extracting two portable Gits, identifying which files are different/missing, and copying a couple of them over until the symptoms go away). Thank you so much in advance! |
Was able to do a quick test; the Aug 23 is already bad. |
Okay, then I suspect that the problem was caused by upgrading cURL (it lost the metalink dependency, which depended on libexpat, and both were removed as a consequence). |
There have been two major breakages recently, might just as well try to prevent them from happening again: - git-for-windows/git#3348 (v2.33.0-rc0) - git-for-windows/git#3392 (v2.33.0(2)) Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
TBH I had hoped for a bit more assistance here. Now I have to somehow squeeze out the time to investigate myself 😞 |
Fully understand, but that's all I could squeeze in today (during my day job). |
FWIW once we found the culprit and fixed it, I am thinking about releasing Git for Windows v2.33.0(3). It would also include OpenSSL v1.1.1l (which fixes a high severity CVE). But maybe I should not rush things so much, |
It would seem that copying |
Many thanks for the quick fix. Please let me know if you want me to verify the fix (and if yes, where I can find the corresponding snapshot). |
Thank you for that datapoint.
Yes, once there is a new snapshot, I would love to ask you to verify that |
Here is a build: https://github.com/git-for-windows/git/actions/runs/1171601455 |
Had the same issue as OP with the stable build and tested myself that one, now it works as expected. Thank you! |
Same here; thanks! |
For the record, there is now a snapshot with the fix. These snapshots are precisely like the official Git for Windows versions, with the exception of the funny version number ;-) |
Does that mean I can close the issue?
…On Tue, 31 Aug 2021 at 15:25, Johannes Schindelin ***@***.***> wrote:
For the record, there is now a snapshot
<https://wingit.blob.core.windows.net/files/index.html> with the fix.
These snapshots are precisely like the official Git for Windows versions,
with the exception of the funny version number ;-)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3392 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIBW52NDIOP4KE2MDJAS7LT7TJ3JANCNFSM5CYMP6DA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
It's already closed. No further action needed. |
Thank you |
Thanks dscho! This worked for me. For those that are using 64-bit and do not want to download the entire Git snapshot, here's the This will fix SVN on Git 2.33.0.windows.2 until the next release is ready. |
The `git svn` command, which was broken in Git for Windows v2.33.0(2), [has been fixed](git-for-windows/git#3392). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
An even better workaround is to upgrade to the latest snapshot (as I had already mentioned). |
Everybody coming to this ticket: please update to Git for Windows v2.33.1. |
I have the same issue on widowns 10 with old git version : Issue is solved by using updating the git on windows |
As a general rule, I do not support old Git versions. Only new ones. They are the ones with fixes. |
Setup
Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
git version 2.33.0.windows.2, 64-bit
Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
What options did you set as part of the installation? Or did you choose the
defaults?
Any other interesting things about your environment that might be related
to the issue you're seeing?
No
Details
Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
PowerShell
What commands did you run to trigger this issue? If you can provide a
Minimal, Complete, and Verifiable example
this will help us understand the issue.
I was running commit-diff, but the issue is reproducible with a simple clone:
What did you expect to occur after running these commands?
I expected git svn to do the clone. Usually it produces output like this:
What actually happened instead?
Git svn produced the following errors:
If the problem was occurring with a specific repository, can you provide the
URL to that repository to help us with testing?
You can use any repository. E.g.: https://github.com/git-for-windows/build-extra
What's the latest version of Git where you do not experience this issue?
Git svn commands seem to work fine in these versions:
The text was updated successfully, but these errors were encountered: