Karl Fogel wrote:
> Philip Martin <philip@codematters.co.uk> writes:
> > Rev 2625 fixed the problems where the client tried to lock a directory
> > twice. That was the know problem before the baton stuff was reverted,
> > so I think now it works as well as the trunk does.
> >
> > Since alpha has happened, I'd like to merge back to the trunk.
>
> If you think it's safe to do so, +1. There's no need to keep this
> development on a branch now that the release has been made.
I've noticed that the branch was merged to trunk and tried an example which
caused attempt to lock a directory twice before. Unfortunately, it does not
work, althought with a different error messages. The exact command sequence
is below with svn output in comments.
#!/bin/bash
rm -rf /tmp/repo
rm -rf /tmp/wc
cd /tmp
svnadmin create repo
svn co file://localhost/tmp/repo wc
cd wc
touch a.cpp
svn add a.cpp
svn ci -m ""
echo "x" > a.cpp
svn propset foo bar
svn ci -m ""
#subversion/libsvn_client/commit.c:662
#svn_error: #21052 : <Working copy is not up-to-date>
# Commit failed (details follow):
#subversion/libsvn_client/commit.c:874
#svn_error: #21052 : <Working copy is not up-to-date>
# Cannot commit propchanges for directory '/tmp/wc/'
svn upSending
#At revision 1.
svn ci -m ""
#Sending
#Sending a.cpp
#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 (/tmp/wc/)
- Volodya
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 31 09:37:10 2002