Mark,
I am using svnserve 1.2.3 and the latest subclipse plugin (thanks to Eclipse auto update).
Actually I don't want to lock -- it was Subclipse that asked to do so.
Sure a fresh checkout will also solve the problem, but if you don't have the .properties file in the repository (what is the case here), the Eclipse project settings would be lost. My method of ATTRIB + SVN update solved the problem without loss of that information.
Have Fun
Markus
________________________________
Von: Mark Phippard [mailto:MarkP@softlanding.com]
Gesendet: Do 01.09.2005 15:47
An: users@subclipse.tigris.org
Betreff: Re: AW: Re: AW: Re: The 'I cannot edit any file' HOW-TO
"Markus Karg" <markus.karg@quipsy.de> wrote on 09/01/2005 09:43:40 AM:
> lock told me that there is no lock token, whatever this means (maybe to
lock
> there has to be some special file in locally for SVN?).
> Unlock told me that it is not locked.
> Cleanup worked and worked but didn't help anything.
> Update just told me that I'm up to date.
In order to lock, you need a 1.2 server. None of the other commands would
apply to this situation.
A fresh checkout would also have cleaned up the problem as the files would
not have the read-only attribute set after the checkout.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Sep 1 23:54:03 2005