Re: "invalid XML" repro

kfogel@collab.net wrote:

>Branko Čibej <brane@xbc.nu> writes:
>
>
>>Here's what happened: I have a WC checked out from the 1.0-stabilization
>>branch. Now that the branch has been renamed, I can't update that WC any
>>more -- I get the error that the report contains invalid XML. It seems
>>that the update reporter can't follow changes forward through a rename.
>>"svn switch --relocate" doesn't help, either.
>>
>>I suspect fixing this will require a change in the WC lib logic.
>>
>>
>
>Ben and I encountered this too. Some comments:
>
>The error from 'svn up' is a genuine bug, Ben's filing an issue.
>
>
Good. Not a showstopper, though. :-)

>The 'svn switch --relocate' is pilot error (I made this mistake too).
>This is not a situation for a relocate, tempting as it seems on first
>glance.
>
>
Yes.

>But plain 'svn switch' does work, as it should.
>
>
Huh, right, now why didn't I try that? Ah, well... at least I'm
stressing the server with three simultaneous checkouts right now (one
over https) -- and all seems to work. :-)

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org