Dear Neels, 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. Best regards, Matthijs Dolsma -----Original Message----- From: Neels J Hofmeyr [mailto:ne...@elego.de] Sent: Tuesday, November 01, 2011 9:20 PM To: Matthijs Dolsma Subject: Fwd: Re: Issue: Exception during revert (forgot to Cc to your mail address, so forwarding my dev@subversion reply now. If you reply, please do so on dev@subversion.apache.org.) -------- Original Message -------- Subject: Re: Issue: Exception during revert Date: Tue, 01 Nov 2011 13:56:13 +0100 From: Neels J Hofmeyr <ne...@elego.de> Organization: elego Software Solutions GmbH To: dev@subversion.apache.org Hi Matthijs, 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). Anyway, 'upgrade' seems to be a wee bit unreliable. 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. Nevertheless, this here is not the mailing list for TortoiseSVN, which is a separate project from this, the "core" Subversion. Thanks! ~Neels On 10/28/2011 05:41 AM, Matthijs Dolsma wrote: > Dear Subversion team, > > > > Today I encountered an exception in TortoiseSVN. > > > > Recipe > > In my working copy I did the following: > > 1. Check for modifications > > 2. Found one file missing/deleted status => Revert > > 3. Exception was reported. > > The file with the bad status has been renamed recently. From something > like "NameX.txt" to "Namex.txt". This might explain the > missing/deleted status. I reverted already several times. > > > > Symptoms > > Now my working copy is locked. Any cleanup command will trigger same > exception. > > The file/folder status is no longer reported in windows explorer. > > Reboot did not change behavior. > > > > My system > > * Windows 7 64bit > > * TortoiseSVN 1.7.1, Build 22161 - 64 Bit , 2011/10/21 22:51:59 > > * Installed with TortoiseSVN-1.7.1.22161-x64-svn-1.7.1.msi > > * Working copy was 1.6 version, ran cleanup first, then installed > version 1.7, then ran the upgrade command. > > > > Kind Regards / Met vriendelijk groet, > > > > Matthijs Dolsma > > ITEC-Asia Octopus Product Team > > *N**X**P* Semiconductors Hong Kong Limited > > 8/F General Garment Bldg, 100-110 Kwai Cheong Rd > > Kwai Chung, N.T. Hong Kong > > Tel: +852 2319 7881 > > Fax: +852 2480 0602 > > >
