[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.5.3 svnsync fails with "207 Multi-Status"

From: Kylo Ginsberg <kylo.ginsberg_at_gmail.com>
Date: Thu, 23 Oct 2008 13:08:02 -0700

Self-bump ... anybody have insight into this error?

On Tue, Oct 21, 2008 at 4:47 PM, Kylo Ginsberg <kylo.ginsberg_at_gmail.com> wrote:
> Background:
> 2 Fedora 7 x86_64 servers running svn 1.5.3. I want to try a proxy
> server setup so I'm starting by using svnsync to replicate the
> repository. It churns away for many hours and after about 80k
> revisions, svnsync reports:
>
> Transmitting file data .svnsync: At least one property change failed;
> repository is unchanged
> svnsync: PROPPATCH of
> '/svnroot/!svn/wrk/ab249067-9027-4e1a-9ed7-8474b6d416f3/users/jwhiteman/python/cfg/CFG.xml':
> 207 Multi-Status (http://hood)
>
> I did a little googling and see some hints on this subject, none of
> which have helped me out:
> * I tried disabling deflate, but that didn't help
> * someone says an old neon version can cause this, but I built 1.5.3
> using the 1.5.3 dependencies tarball
> * someone mentioned trying serf, but I got segfaults on checkout with
> 1.5.3 serf so I've stayed away
>
> I've been running the synchronize operation from a cmd-line on the
> dest machine, so for now, I restarted the synchronize operation
> specifying a file:// url rather than an http:// url and it got past
> the revision in question. Of course, that won't work when I actually
> set up a master-slave proxy b/c the master machine will be driving the
> sync's.
>
> Any ideas?
>
> Thanks!
> Kylo
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-23 22:08:33 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.