Re: [Issue 1273] Changed - svn cp corrupts *two* repositories

Ben Collins-Sussman <sussman@collab.net> writes:

> Ah, so maybe we should investigate exactly how/why apache didn't
> gracefully shutdown the DB environment.
>
> In the repository you were committing to, the client told the server
> to copy some data into your transaction from an invalid path (i.e. the
> path didn't exist in the repository.) Did that cause httpd to abort
> BDB incorrectly? Can we reproduce this?

Well, the original issue said it was easy to reproduce, but didn't
give enough details to do it. I see no indication of which version of
Subversion was being used, and I don't know whether the URL being
copied was a file or directory, and if it was a directory what it
contained.

Using r5775 I can do the following

  rm -rf repo1 repo2 wc1 wc2

  svnadmin create repo1
  svn co http://localhost/tmp/repo1 wc1
  svn mkdir wc1/foo
  echo zig > wc1/foo/zig
  svn add wc1/foo/zig
  svn ci -m v1 wc1

  svnadmin create repo2
  svn co http://localhost/tmp/repo2 wc2
  svn mkdir wc2/bar
  echo zig > wc2/bar/zag
  svn add wc2/bar/zag
  svn ci -m v2 wc2

  svn cp http://localhost/tmp/repo2/bar/zag wc1/foo/zag2
  svn cp http://localhost/tmp/repo1/foo/zig wc1/foo/zig2
  svn cp wc1/foo/zig wc1/foo/zig3
  svn st wc1
  svn ci -m v3 wc1

and it doesn't hang the repositories. Both the URL->WC copies "work"
although neither appears to record the copyfrom history. So two
questions arise

Should I be able to copy a file into a working copy from an unrelated
repository?

If I copy a file from a repository into a working copy should it
record copyfrom history?

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org