How does WC lock cleanup work?

Here's a simple reproduction recipe for a bug:

  % svn cp filename existing-url

  svn_error: #21079 : <Item already exists in filesystem>
    file `file:///var/ghudson/svn-test/grows' already exists.
  % svn cp filename existing-url

  svn_error: #21044 : <Attempted to lock an already-locked dir>
    working copy locked: .

I thought this would be easy to fix, but I can't quite understand how
the WC code is supposed to work. wc_to_repos_copy() grabs a write
lock and does a pile of operations under SVN_ERR(), although a few
operations do a "goto cleanup" instead. Why? If an SVN_ERR() occurs,
then pool_cleanup() gets a chance to clean up the access baton, but it
chooses not to clean up physical locks. Why?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Aug 3 16:29:33 2002