Dean Thompson <dthompson@peakstrategy.net> writes:
> I am fairly certain I have discovered a simple but severe subversion
> bug. Here is the script of my actions:
>
> bash-2.05b$ mkdir tmp
> bash-2.05b$ cd tmp
> bash-2.05b$ mkdir svntest
> bash-2.05b$ svn import
> . svn+ssh://dthompso@cvs.peakstrategy.net/usr/local/svn
> -m "test"
> Adding svntest
>
> Committed revision 21.
> bash-2.05b$ rm -rf svntest
> bash-2.05b$ svn co
> svn+ssh://dthompso@cvs.peakstrategy.net/usr/local/svn/svntes
> t
> Checked out revision 21.
> bash-2.05b$ ls
> svntest
> bash-2.05b$ cd svntest
> bash-2.05b$ mkdir a
> bash-2.05b$ mkdir a/b
> bash-2.05b$ svn add a
> A a
> A a/b
> bash-2.05b$ svn commit -m "test"
> Adding a
> Adding a/b
>
> Committed revision 22.
> bash-2.05b$ svn move a b
> svn: Working copy 'b/b' is missing or not locked
> bash-2.05b$
Yup, this is a bug. I've got a more compact reproduction recipe,
based on yours, and I've filed this as
http://subversion.tigris.org/issues/show_bug.cgi?id=2343
Here's the recipe:
#!/bin/sh
SVN=${HOME}/src/subversion/subversion/clients/cmdline/svn
SVNADMIN=${HOME}/src/subversion/subversion/svnadmin/svnadmin
URL=file:///`pwd`/repos
rm -rf repos svntest
${SVNADMIN} create repos
mkdir svntest
${SVN} import svntest ${URL}/svntest -m "test"
rm -rf svntest
${SVN} co ${URL}/svntest
cd svntest
mkdir a
mkdir a/b
${SVN} add a
${SVN} commit -m "test"
# Even if you insert 'svn up' here, the following move command still
# results in this error:
#
# subversion/libsvn_wc/lock.c:677: (apr_err=155005)
# svn: Working copy 'b/b' is missing or not locked
${SVN} move a b
Thanks for the report! We'll fix it as soon as we can; obviously, if
you have time/ability to write a patch for it, that would be great.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 23 22:41:15 2005