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

Re: Broken Working Copy.

From: Robert Graf-Waczenski <rgw_at_lsoft.com>
Date: Wed, 08 Oct 2008 10:02:00 +0200

Ryan Schmidt wrote:
> On Oct 6, 2008, at 04:32, James Green wrote:
>> I'm a bit lost as to what is going wrong with one of my local working
>> copies. I can't do anything with it at the moment.
>> Firstly, trying to execute a commit fails with:
>> "Working copy D:\ ... locked"
>> "Please execute the Cleanup command".
>> So trying to run the Cleanup command:
>> "Cleanup failed to process the following paths:
>> "D:\ ..."
>> I've tried running cleanup on each sub dir ... i've tried removing a
>> lock only to be told that there is nothing locked. What on earth is
>> going on?
> You're saying you read the message "Working copy D:\ ... locked" and
> then tried "svn unlock <something>" and it said it wasn't locked and
> are confused? If so, I don't blame you; these are two different and
> unrelated uses of the word "lock". See:
> http://subversion.tigris.org/issues/show_bug.cgi?id=2303
>> Makes me very nervous, it seems too easy for SubVersion to get its
>> knickers in a twist!! Then to be given wrong error messages isn't
>> particularly good either.
>> What steps do I need to take to fix this?
> Working copies can get corrupted from time to time. If we know how,
> Subversion could be improved to either not corrupt the working copies
> in that way, or to enhance "svn cleanup" so it could repair the
> corruption. Since it is not known how your working copy got corrupted
> in this way, all you can do is check out a new one.

We had similar problems here in our windows shop with the workstation of
one of our developers. We also checked out a new working copy. In our
case the corruption was caused by an influence external to subversion
(and TortoiseSVN). We tracked down the culprit and found it: Our Java
IDE was configured to write its compiled class files to the same
location were the sources reside, i.e. into the WC folder. Each time we
told the IDE to rebuild the project, it first cleaned all empty folders
recursively, which fubar'd the WC... Now we run the IDE with slightly
different settings, causing it to build into a separate classes folder.
After this, no more WC corruption. So, when encountering WC corruptions,
don't blame subversion but first look elsewhere.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-08 10:09:18 CEST

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

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