Re: bug: trying to schedule-replace a directory

Ben Collins-Sussman wrote:
>
> [sussman@sussman-mac:~/scratch/wc]$ svn rm libsvn_delta/
> [sussman@sussman-mac:~/scratch/wc]$ rm -rf libsvn_delta/
> [sussman@sussman-mac:~/scratch/wc]$ mkdir libsvn_delta
> [sussman@sussman-mac:~/scratch/wc]$ svn add libsvn_delta
> A libsvn_delta
> subversion/libsvn_wc/lock.c:835: (apr_err=155005)
> svn: Unable to lock 'libsvn_delta'
> [sussman@sussman-mac:~/scratch/wc]$ svn st
> R .
> [sussman@sussman-mac:~/scratch/wc]$ ### what the???

OK, obviously there's a bug there.

I thought, on asking Subversion to delete a directory, (a) the directory tree
and .svn directories were left in place so that (b) the delete can be reverted
and (c) "commit" can check whether the contents and refuse to delete anything
that was of date.

 From a quick test, it seems:

(a) is true
(b) is true
(c) is false - if I delete the remnants from disk, I can still commit the delete.

Is that expected?

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 31 18:22:01 2006