On 11/8/06, Mark Gibson <mgibson@fruitfly.org> wrote:
>
>
> Erik Huelsmann wrote:
> > On 11/8/06, Mark Gibson <mgibson@fruitfly.org> wrote:
> >> i had a svn commit just hang - ctrl-C wouldnt end it. so i killed the svn
> >> process. now when i commit i get:
> >>
> >> svn commit
> >> svn: Working copy '/home/mgibson/pheno-tool/java/svn/phenote' locked
> >> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
> >> details)
> >>
> >> i svn cleanup as it suggests but still get same message.
> >
> > Then probably the working copy wasn't cleaned up successfully. Which
> > svn version are you using?
>
> version 1.3.1 (linux)
>
> What error does 'svn cleanup' generate?
>
> no errors from svn cleanup - no response at all - just seems to return
> contentedly - as if im clean
hmm. are there .svn/log* files or .svn/killme / .svn/KILLME (i'm
unsure about the case, I'm answering your question without consulting
the sources).
> is this problem on the client or server side? its svn through sourceforge - do i
> need to contact them
>
> are there lock files i can manually fiddle with (i cant find them)
yes: .svn/lock
> so its only from the root of my svn files/dirs that is the problem. If i go down
> from the root I can svn commit. and at the root I can do other svn commands -
> update, status, log (does log show locks? i grepped for lock - got nothing) - I
> just cant svn commit from the root anymore - It still gives the above error message.
log doesn't show locks (afaik), but those would be different locks
than the ones your client is complaining about. Locked files (in the
repository) have little to do with locked working copies, no matter
how unfortunately similar the wording ...
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 8 22:35:41 2006