After having been away from subversion for a year or so, I've started
encountering severe problems getting back in the saddle on Mac OSX.
Namely, nearly everything I do to a working copy leads to a broken
(locked) repository as shown below:
bcox$ svn status
...looks OK, but...
bcox$ svn ci
svn: Working copy
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
...OK, if you say so...
bcox$ svn cleanup
svn: Can't move '.svn/tmp/entries' to '.svn/entries': Operation not
bcox$ ls -l .svn
-r--r--r-- 1 bcox bcox 118 Feb 5 14:06 README.txt
-r--r--r-- 1 bcox bcox 75 Feb 5 14:06 dir-wcprops
-r--r--r-- 1 bcox bcox 0 Feb 5 14:06 empty-file
-r--r--r-- 1 bcox bcox 9556 Feb 5 14:06 entries
-r--r--r-- 1 bcox bcox 2 Feb 5 14:06 format
-rw-r--r-- 1 bcox bcox 0 Feb 5 14:06 lock
drwxr-xr-x 35 bcox bcox 1190 Feb 5 14:06 prop-base
drwxr-xr-x 35 bcox bcox 1190 Feb 5 14:06 props
drwxr-xr-x 35 bcox bcox 1190 Feb 5 14:06 text-base
drwxr-xr-x 4 bcox bcox 136 Feb 5 16:22 tmp
drwxr-xr-x 35 bcox bcox 1190 Feb 5 14:06 wcprops
The real problem seems to be that .svn/entries is somehow actually
locked (via OSX chflags), not just write protected as I at first suspected.
Its not clear who's doing this (svn? eclipse?), but svn seems the most
likely culprit at this point.
I'm using http: access method via apache2 installed on port 18080.
Checkouts work fine, as is the repo itself. Initial working copies are
fine, but go south after one or more changes.
I've tried several SVN GUI's (subclipse, isvn, simplesvn, etc) which I
thought might have been responsible. But the above example was a fresh
working copy accessed only by the svn client, version 1.3.0 r17949.
Can someone please advise? Subversion is pretty much unusable at this point.
Received on Sun Feb 5 22:49:10 2006