Philip Martin <philip@codematters.co.uk> writes:
> No, it's just a path canonicalisation problem in the new locking code.
Oh, sorry, I cancel my earlier mail, then. :-)
-K
> Before I file this one, has anyone taken a look at it?
>
> Ben Collins-Sussman <sussman@collab.net> writes:
> > Somebody noticed that by setting 'svn:keywords' accidentally on a
> > directory, this causes 'svn ci' to freak out:
> >
> > $ cd wc
> > $ svn ps svn:keywords .
> > property `svn:keywords' set on '.' ### bogusness
> > $ touch moo
> > $ svn add moo
> > A moo
> > $ svn ci -m "maou"
> > Sending
> > Adding moo
> > Transmitting file data .
> > subversion/libsvn_client/commit.c:670
> > svn_error: #21002 : <A general problem occured>
> > Commit succeeded, but other errors follow:
> >
> > subversion/libsvn_client/commit.c:688
> > svn_error: #21045 : <Working copy not locked>
> > Error bumping revisions post-commit (details follow):
> >
> > subversion/libsvn_wc/lock.c:280
> > svn_error: #21045 : <Working copy not locked>
> > directory not locked (/usr/home/sussman/projects/test/wc/)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 1 17:48:59 2002