Sean Russell <ser@germane-software.com> writes:
> However, I still get the error in the server-side log messages:
>
> [Wed Dec 19 10:46:12 2001] [error] [client 65.14.169.215] Could not fetch
> resource information. [500, #0]
> [Wed Dec 19 10:46:12 2001] [error] [client 65.14.169.215] could not determine
> resource kind [500, #21050]
> [Wed Dec 19 10:46:12 2001] [error] [client 65.14.169.215] file not found:
> filesystem `/home/subversion/db', revision `7', path `/rexml/tags/1.2.3'
> [500, #21050]
This might actually be intentional. Part of the copy operation's
logic is to decide if, when you give a destination of ...tags/1.2.3,
"1.2.3" is the new thing to be created, or just an existing directory
in which to put the copied thing. So a "stat" of sorts is run on the
destination path. If the stat comes back with "there's no such thing
as .../tags/1.2.3", then we assume that the copy operation is going to
be creating a new thing called "1.2.3" in the ...tags directory. If
it comes back with ".../tags/1.2.3 is a directory" then we know we are
going to be creating a new item called "trunk" (in your example) in
the ...tags/1.2.3 directory.
What you might be seeing above is the answer to the stat question. I
can't state this matter-of-factly, though.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:53 2006