Ran command git svn clone "SVN URL".
It works fine till 4568 commits, but then it gets after this commit giving the error stated in title.
5
-
1The exact error that we get is Malformed network data: The XML response contains invalid XML: Malformed XML: no element found at /mingw64/share/perl5/site_perl/Git/SVN/Ra.pm line 312.tatushar3– tatushar32016-06-30 05:20:58 +00:00Commented Jun 30, 2016 at 5:20
-
Do you use git-svn as a frontend for an eixisting SVN repository that remains exisiting or do you try to do a one-time conversion of an SVN repository to Git?Vampire– Vampire2016-07-05 14:56:27 +00:00Commented Jul 5, 2016 at 14:56
-
@Vampire Can you please clarify your statement.tatushar3– tatushar32016-07-08 04:45:49 +00:00Commented Jul 8, 2016 at 4:45
-
What is unclear? Do you have an SVN repository that will still hold the canonical state of your source or do you try to do a one-time conversion of an SVN repo to a Git repo and are using Git exclusively from there on.Vampire– Vampire2016-07-08 07:36:53 +00:00Commented Jul 8, 2016 at 7:36
-
One time conversion. After this we will freeze our son repo. We are using git svn command to do this. @Vampiretatushar3– tatushar32016-07-09 08:30:43 +00:00Commented Jul 9, 2016 at 8:30
Add a comment
|
2 Answers
this seems to be because the default log-window-size is too small.
When you get error, from the new git repo, try running:
git svn fetch --log-window-size=4000
You can experiment with the actual number, but 4000 was the magic number for me.
3 Comments
burtsevyg
Same with --log-window-size=100000
burtsevyg
In my case when I create svnadmin dump svnadmin: E160004: Filesystem is corrupt svnadmin: E200014: Checksum mismatch while reading representation: expected: b564bb2bc05a87375cb56817aaca060f actual: 37ed90170516d2c16cc6976c86597150
foad322
it did not worked for me
git-svn is not the right tool for one-time conversions of repositories. It is a great tool if you want to use Git as frontend for an existing SVN server, but for one-time conversions you should not use git-svn, but svn2git which is much more suited for this use-case.
There are pleny tools called svn2git, the probably best one is the KDE one from https://github.com/svn-all-fast-export/svn2git. I strongly recommend using that svn2git tool. It is the best I know available out there and it is very flexible in what you can do with its rules files.
If you are not 100% about the history of your repository, svneverever from http://blog.hartwork.org/?p=763 is a great tool to investigate the history of an SVN repository when migrating it to Git.
