On Tue, Feb 27, 2018 at 4:09 PM, Myria wrote:
> Not to mention that the two revisions complained about are unrelated, and
> 2/3 the repository history apart.
>
> One thing that's interesting is that the commit the svnsync failed on is a
> gigantic commit. It's 1.8 GB. Maybe that svnsync is fail
I have seen a different result from svn log and I can cherry pick around and
see some expected output.
The curl output below has… "~$ployment%20to%20Test.doc">~$ployment to
Test.dochttps://scm-uat.web.att.com:6022/svn/asgard
--
As you work toward a conclusion, Andy, do you think there was a different
error message that could have driven you to root cause more quickly?
Nice catch
svn co https://scm-uat.web.att.com:6022/svn/asgard svn: E130003: The XML
response contains invalid XML
[an2124@hlth509 test3]$ svn co https://scm-uat.web.att.com:6022/svn/asgard/
svn: E130003: The XML response contains invalid XML
curl -k -u an2124 --insecure https://scm-uat.we
Johan Corveleyn writes:
> I'm wondering whether this is related to the bug that was fixed for
> 1.8.x here:
>
> http://svn.apache.org/viewvc?view=revision&revision=1803435
>
> ... or a similar problem.
> I'm actually not sure whether that bugfix was released already (it's
> not mentioned in CHANG
"NOCERA, ANDY" writes:
> svn co https://xxx.com:6022/svn/asgard
> svn: E130003: The XML response contains invalid XML
If you have the socat proxy available then you can use that to log the
traffic and see the failing XML:
https://subversion.apache.org/docs/community-guide/debugging.html#net-tra
I'm happy to announce the release of Apache Subversion 1.10.0-rc1.
Please choose the mirror closest to you by visiting:
http://subversion.apache.org/download.cgi#pre-releases
The SHA1 checksums are:
162dc785b5b1460c2f67af7460fe9b0b44e7aab7 subversion-1.10.0-rc1.tar.bz2
f16d5d7c1757c9
On Wed, 28 Feb 2018 03:21:01 +, NOCERA, ANDY wrote:
> My cert is not valid at this point, I had turned off ssl and had the same
> error. I wasn???t sure how to get beyond the 301 on a curl
You ask for .../asgard, and get redirected to .../asgard/ (note the slash at
the end). Try that.
And
