John Goerzen <jgoerzen@complete.org> writes:
> On Wed, Apr 30, 2003 at 01:29:35PM -0000, issues@subversion.tigris.org wrote:
> > 1. Running 'svn cp URL wc' between two different repositories is
> > strictly verboten. It's not supposed to work yet, at least not till
>
> What is the canonical way of doing this then? svn merge seems close but
> still not quite there. svn export follwed by a recursive add?
Yes, that's all you can do for now.... export and add.
If you want _history_, then you can 'svnadmin dump', pipe through
svndumpfilter, and 'svnadmin load' the tree into the 2nd repository.
> > we have cross-repository communication working after svn 1.0. In
> > fact, if you had been using the latest release (both client and
> > server), this operation would have been *blocked*. 'svn cp' would
>
> I was running 0.21 on the server and 0.20.1 on the client. Could the latter
> have been the problem?
Yes. The 0.21 client blocks the 'svn URL wc' copy if the repository
UUIDs don't match. Although a bug Philip noticed yesterday may be a
monkey wrench in this behavior at the moment; I think he just fixed
the bug in HEAD.
> I'm not sure that I agree with closing this; despite the block for the svn
> cp being put in place now, it seems that this is a denial-of-service attack
> in the making if any old client can crash the server so easily.
Yeah, good point... I guess we're trying to figure out a small, simple
reproduction recipe here: what's the smallest set of DAV requests (or
old client actions) that can cause the 500 server error and DB hang?
If we can answer that question, I'd like to open an independent issue
for it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 1 16:52:57 2003