I'm attempting to do a one-way from subversion to Git migration of a large subversion repository using git svn
with the following command (IMPORTANT after the migration only Git will be used):
git svn clone --no-minimize-url --trunk=/trunk/GBI --branches=/branches/GBI --tags=/tags/GBI --authors-file=authors.txt https://yyy/svn-repos/zzz/ GBI
After couple of hours running, the clone process crashes with the following error:
r79791 = 00349b8063f90447ea8a040751cd2a40e74b74f3 (refs/remotes/origin/trunk)
Error from SVN, (175009): Malformed network data: The XML response contains invalid XML: Malformed XML: no element found
Then I thought that maybe there is a clever way to resume the process right after the offending revision ... is that possible?
Any ideas what causes this error in the first place?
The answer to this question suggests using the --log-window-size
to prevent this issue from happening in the first place ... can I add the option and retry from the failed revision? is this issue then a git svn
memory usage issue or a problem that is connected solely to a corrupted subversion revision?
Is there a git svn option to robustify the process to ignore errors and not just stop the lengthy process due to this error?
UPDATE: I arrived at this point following the Atlassian Stash Migrating to Git guide which indicates using git svn
and their svn-migration-scripts.jar
implementation
I recently had
Error from SVN, (175009): Malformed network data: The XML response contains invalid XML: Malformed XML: unclosed token
which is almost the same and executing git svn fetch
in the repository folder created by git clone as mentioned by Mykola Gurov in a comment did continue at the revision where the error occurred and ran until the last SVN revision.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With