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

SVN Update error suggests probable bug

From: Tony Lenzi <lenz1105_at_gmail.com>
Date: 2006-08-03 15:10:03 CEST

While trying to update my checked out svn repository from Subclipse I
received the following error message:

org.tigris.subversion.javahl.ClientException: Working copy not locked; this
is probably a bug, please report
svn: Working copy 'C:\workspace\myproject\build' is missing or not locked.

I'm running Eclipse 3.1.2 and the Subclipse plugin 1.0.2 on a Windows XP pro
The repository is running on a Fedora Core 5 server, version 1.3.0 and we
use the svn:\\ protocol to access the repository.

I was trying to update my repository to see if any of my development team
had added anything new when I got this error. We've been experiencing
problems when one of us creates a directory in our source tree and runs an
update or commit after someone else had already committed that directory.
Instead of merging with the existing directory or asking if that's the
action I'd like to take, it throws an error and refuses to commit. The only
way I could finally get code committed yesterday was to delete my local
versions of those folders, clean up, run an update, and then put those
folders and files back in, add them if new, and then commit them. Very

Am I doing something wrong or is this a probably bug in SVN?

Thanks for the help,

Received on Thu Aug 3 19:56:09 2006

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.