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

Re: possible bug - org.tigris.subversion.javahl.ClientException: Working copy not locked; this is probably a bug, please report

From: Shannon Dillman <shannon.dillman_at_gmail.com>
Date: Thu, 10 Feb 2011 18:09:19 -0500

Thanks guys - I was just reporting a bug, and didn't expect help. It
is much appreciated, and I now have things working.

Ryan - that's why I qualified "up to date" with "per the Synaptic
package manager" I am sorry I didn't specify further, which brings me
to Andy - you were right. 1.6.6 is what's installed, and I should have
known to dig a little deeper and not believe the package manager,
since I JUST installed Wordpress itself from a download, since the
version in the package manager was quite old.

Mark - thank you for pointing me at the FAQ. I deleted the project,
cleaned the Wordpress folders of everything .svn, re-created the
project - and got the error back. Repeated the above, but instead of
creating it as a PVP project, I created it as a general web project
(I'm not really going to build anything). Et voila! Also thanks for
the heads up on V 1.7 - I am really looking forward to that.

Again, I appreciate the help and ideas.

On Thu, Feb 10, 2011 at 4:44 PM, Ryan Schmidt
<subversion-2011a_at_ryandesign.com> wrote:
> On Feb 10, 2011, at 15:19, Andy Levy wrote:
>> Please be sure to specify the actual version of Subversion you're
>> using. "Up to date" could have two meanings here - up to date with
>> regard to what's in the Ubuntu 10.04 repository, or up to date with
>> regard to Subversion releases. From what I can tell, Ubuntu 10.04 has
>> Subversion 1.6.5 or 1.6.6, and the current official release of
>> Subversion is 1.6.15.
> It could also mean "up to date with what I think is up to date" in one of the above two senses, which might be different from what is actually up to date.
Received on 2011-02-11 00:10:21 CET

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.