From: Eric Wong <e@80x24.org>
To: Jason Pyeron <jpyeron@pdinc.us>
Cc: git@vger.kernel.org
Subject: 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
Date: Mon, 22 Jan 2018 05:40:34 +0000 [thread overview]
Message-ID: <20180122054034.GA9759@starla> (raw)
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.
prev parent reply other threads:[~2018-01-22 5:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 11:19 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 Jason Pyeron
2018-01-22 5:40 ` Eric Wong [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180122054034.GA9759@starla \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=jpyeron@pdinc.us \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).