git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git svn clone - Malformed network data: The XML response contains invalid XML: Malformed XML: no element found at /usr/share/perl5/vendor_perl/5.26/Git/SVN/Ra.pm line 312

From
EWEric Wong <e@80x24.org>
Date
Jan 22, 2018, 05:40 UTC
Message-ID
<20180122054034.GA9759@starla>
In-Reply-To
<042F7DAF79EF4C29B85958BD75AE019F@blackfat>
Jason Pyeron <jpyeron@pdinc.us> wrote:
> 
> I am asuming that this is an issue caused by codeplex's svn
> from tfs implementation. Does anyone here have any insight?
Seems like it, even using svn(1) fails (see below)
> r27599 = 9e769d8327767a155d7b96b7cc28579cf0ed4c93 (refs/remotes/git-svn)
> Malformed network data: The XML response contains invalid XML: Malformed XML: no element found at /usr/share/perl5/vendor_perl/5.26/Git/SVN/Ra.pm line 312.
OK, so lets find out what the next commit is after r27599:
  svn log -v -r 27599:HEAD https://smtp4dev.svn.codeplex.com/svn
  # which tells me r27864
  svn diff -r 27599:27864 https://smtp4dev.svn.codeplex.com/svn
  # which tells me:
  svn: E130003: The XML response contains invalid XML

strace only shows encrypted data, so maybe there's a flag or debug option you can enable in SVN itself to see what was in the bad XML or maybe contact the admin to see if it can be fixed.

Previous: Jason Pyeron
Message 2 of 2 in “git svn clone - Malformed network data: The XML response contains invalid XML: Malformed XML: no element found at /usr/share/perl5/vendor_perl/5.26/Git/SVN/Ra.pm line 312”
  1. Jason PyeronJan 21, 2018
  2. Eric WongJan 22, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.