We have experienced the "207 Multi-status" error in subversion when diffing to revisions of a file. A search for a solution, and posting to the user list did not help us, so we still live with the problem that only has appeared for some files. It might have something to do with a SCM conversion utility that we have used, but we don't know.
It seems to me that the 207 message is not an error message seen from Apache, rather an informative message, but that SVN interprets it as an error somehow. I would be glad to find out more about this ........
Sorry for not being able to help out more ....
From: kylo.ginsberg_at_gmail.com [mailto:kylo.ginsberg_at_gmail.com] On Behalf Of Kylo Ginsberg
Sent: 4. januar 2010 17:37
To: users_at_subversion.apache.org; dev_at_subversion.apache.org
Subject: Re: svnsync "207 Multi-Status" failure with http access method and property "svn:"
Self-bump and post to dev list also. Posting 2 days before Christmas
seems to be a bad way to get a response ... ;>
On Wed, Dec 23, 2009 at 1:13 PM, Kylo Ginsberg <kylo_at_kylo.net> wrote:
> Preparatory to setting up a proxy server, I'm trying to svnsync a
> repository from 1.6.6 server to another 1.6.6 server (both x86_64
> linux, one Fedora 7, one Fedora 12). Some user somehow managed to
> create a property "svn:" on a file and the svnsync fails like so:
> Transmitting file data .svnsync: At least one property change failed;
> repository is unchanged
> svnsync: PROPPATCH of
> 207 Multi-Status (http://hood)
> I'm able to reproduce (what I assume is) the same problem without svnsync:
> 1) create a repo, with both svn and http access methods
> 2) via svn access method create a file, set an "svn:" property, and
> commit it, e.g.
> svn co svn://snow/test test
> cd test/
> echo foo > foo.txt
> svn add foo.txt
> svn ps svn: asdf foo.txt
> svn ci -m testing
> 3) now try to access it via http:
>> svn pl http://snow/test/foo.txt
> svn: PROPFIND of '/test/!svn/bc/1/foo.txt': 207 Multi-Status (http://snow)
> So two questions here:
> 1) Is this a known issue? (I didn't see it in the bug db.) If not,
> can I get a second nomination that this is a bug? (If someone can
> point me in the right direction, and if this is likely to be a
> somewhat surgical fix, I'd be happy to attempt a patch.)
> 2) Any recommendations on how to proceed? For the initial sync of
> repos I can probably force the issue by svnsync'ing via the svn access
> method, but I don't think this will work once I set up write-through
Received on 2010-01-05 19:47:58 CET