-
Notifications
You must be signed in to change notification settings - Fork 443
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 fetch failed (on svn tagging commit) #99
Comments
I'm also seeing that running it on https://xmappr.googlecode.com/svn/trunk (using Fedora F18 beta and git 1.8.0.2):
|
It's git-svn bug. |
Given this error, I followed the advice from http://stackoverflow.com/questions/3009738/what-does-this-svn2git-error-mean/4434188#4434188 and removed the duplicate entries under the remotes svn section in my |
Given that this is a git-svn bug, where does one report the bug so that it gets fixed? I'm getting tired of removing duplicate entries every couple of minutes and I have a several gigabyte SVN repo to process, with almost 15 years of commits. |
This bug was first noticed 2 years ago, it was confirmed to be a git-svn bug, and nothing has been done since. So I decided to take action. I have created a bug report for Git (git-svn) at Ubuntu Launchpad: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1403767 |
Thanks @amedee. |
Thank you, @the-real-trash80 . Removal of svn remotes section in |
Will this be automatic anytime soon? |
I'm trying to rebase my vapoursynth svn2git repo (that was initiated with
svn2git -v --revision 2 http://vapoursynth.googlecode.com/svn/
command some time ago), butgit svn fetch
is failing on the svn commit performing tagging. (Same thing happens if you want to run svn2git from scratch.)I upgraded to git 1.8.0 (from debian unstable repository), but it didn't help.
The referenced part of
SVN.pm
is belowI don't see anything special in r332. Any ideas what's wrong and how it can be fixed? It's definitely not about quoting apostrophes or quotation marks, as they aren't there.
The text was updated successfully, but these errors were encountered: