RE: Re: Issue: Exception during revert
From: Matthijs Dolsma <Matthijs.Dolsma_at_nxp.com>
Date: Tue, 1 Nov 2011 14:46:29 +0100
Thanks for your reply. I indeed used the approach of a fresh checkout + file copy as a workaround. This is working fine. Thanks to single .svn folder in the root the file copy was a breeze.
Because I'm doing a lot of troubleshooting/bug fixing myself I fully understand the difficulty of reproducing. But nevertheless I wanted to report this, to give you some indication. If I can find a way of getting the error again, I will let you know.
As of yet, I'm running 8 checkouts which I upgraded. Around 16000 files per working copy. Overall seems to be running stable.
(forgot to Cc to your mail address, so forwarding my dev_at_subversion reply now. If you reply, please do so on dev_at_subversion.apache.org.)
-------- Original Message --------
noting that no-one has replied yet, I would like to thank you for your problem report. However, it is difficult to tell what exactly went wrong in your specific case and how to fix it (there is a known issue about missing checksums, but I'm not familiar with it, maybe someone else can comment).
At the end of the day, I suggest that you try to make a clean checkout using svn 1.7, so that you get a brand new working copy that pretty much guarantees you a consistent state to work with.
If you have uncommitted modifications in your old/locked working copy, you would need to transfer them to the new working copy. That *can* be simply a matter of copying the files over (omitting '.svn' folders). If you had local moves, adds, deletes or such, that would need some more work.
If it is a lot of work for you to get a fresh checkout, you can also try to blast away the entire working copy subtree in which your error appears, starting with at least the parent folder above the problem. A subsequent 'update' should bring those things back and maybe fixes things at the same time. And again, make sure you don't blast away uncommitted changes.
Hope that this is helpful -- I'm basically just confirming that we care, seeing that no-one else has replied yet.
Oh, BTW, your error appears to be coming from the Subversion API itself.
On 10/28/2011 05:41 AM, Matthijs Dolsma wrote:
This is an archived mail posted to the Subversion Dev mailing list.