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

Re: Re: FW: The REPORT request returned invalid XML in the response: XML parse error at line ...

From: Joshua Varner <jlvarner_at_gmail.com>
Date: 2005-08-30 21:56:43 CEST

On 8/30/05, GOVAERTS Lieven <Lieven.GOVAERTS@post.be> wrote:
> I checked, and there's nothing wrong with the case of the file.
> I have been looking in the apache error_log file, and this lines seems
> to occur regulary:
> [Mon Aug 29 15:02:09 2005] [error] [client<>]
> A failure
> occurred while driving the update report editor [404, #160013]
> [Mon Aug 29 15:02:09 2005] [error] [client<>]
> Working copy
> path 'Controls/BankingNameAddressLocation.resx' does not exist in
> repository [404, #160013]
> What this user did was first try an update of the whole branch, failed
> with the error I reported
> Yesterday, then tried a few times to update the individual folder
> "Controls". He deleted the
> BankingNameAddressLocation.resx file and updated again, all without
> success.
> I got it running again by moving the Controls folder completely and then
> updating the parent folder.
> It seems something in the .svn folder got corrupted and that it was
> solved with a clean update.
> Don't know if it's still important, but I can probably get the faulty
> .svn folder from the developer
> and do some more investigation.
> Since it's come up several times, it might be worth it to make a copy. You
could diff
the working and non-working to see if that shows anything interesting. I'm
you can't just post the working copy or e-mail it to someone so they could
take a look.

I'm not familiar enough with the wc structure to give you a suggestion of
what to look
for. But, it wouldn't hurt to have it around, and the diff between the valid
and invalid
copy will probably help.

Received on Tue Aug 30 21:57:36 2005

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

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