C. Michael Pilato wrote:
> D.J. Heap wrote:
>
>>svnsync on trunk has just started failing for me within the last few
>>days. I've been syncing to http://svn.collab.net/repos/svn but now I
>>get:
>>
>>
>>C:\Projects\Subversion\Debug\subversion\svnsync>svnsync sync
>>file:///C:/Subversion/svn-repo
>>..\..\..\subversion\libsvn_ra_dav\util.c:827: (apr_err=175002)
>>svnsync: REPORT request failed on 'http://svn.collab.net/repos/svn'
>>..\..\..\subversion\libsvn_ra_dav\util.c:296: (apr_err=175002)
>>svnsync: REPORT of 'http://svn.collab.net/repos/svn': 200 OK
>>(http://svn.collab.net)
>>
>>While debugging I see a few PROPFINDS go by and then a REPORT request
>>fails -- ne_request_dispatch returns 1 and so even though the http
>>status code is 200, we drop into error handling code at line 769.
>>
>>I've also attached a zipped Wireshark trace. There are no proxies
>>involved. No doubt it has something to do with the recent changes,
>>but I'm not familiar enough with it to narrow in on the problem very
>>quickly -- would someone more knowledgeable take a look, please?
>
>
> svnsync's protocol changed post-1.4.0-rc4. So, if you're using trunk
> svnsync against the 1.4.0-rc4 code on svn.collab.net, then this is an
> expected failure.
I should point out, though, that the changes were backported to 1.4.x, and
should be available rc5. So, when Subversion 1.4.0 is finally released
there will be no server/client incompatibility issues of this sort. Yes,
you'll see need a 1.4.0 server, but either 1.4.0 or 1.5.0-dev client will
work just fine.
--
C. Michael Pilato <cmpilato@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Aug 19 15:20:08 2006