[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: write-thru proxy lossage

From: Steve Byrne <sbb_at_penguinis.org>
Date: Mon, 14 Sep 2009 07:29:12 -0700

Thanks for getting back to me on this.
> - Set up two different Hosts (I think in your case, you could use two
> different virtual hosts, two distinct machines would be better, however)
> - have the same <location> on both of them for client access (the client
> needs to see the same path, while the hostnames can differ)
This I think you have provided me with the key: only one or two messages
in the scant email traffic on this problem say "must have the same
path". Oh. Which path??? Location? File system path to repo???
Proxy sync path? Something else??? Arrrgh. Thank you VERY much for
disambiguating this for me.
> Verbose explanation I found:
> When copying, is basically sends the command to create a copy
> of /svn-mirror/testrepo/path_to_source
> at /svn-mirror/testrepo/copy_of_path_to_source. The slave knows it
> should forward that request to the master, so it does. It even rewrites
> one of the paths to match the master path. The master, however, knows
> nothing about the (non-rewritten) copy source (I think it rewrote the
> destination - the change sent contains a COPYFROM: ...), it doesn't know
> about the /svn-mirror/ path, so it gets confused and sends an error.
Wonderful -- I'd seen a hint about this "confusion", which to me sounded
like a bug in the code whereby it was using the wrong frame of reference
for creating these paths.
> I hope this helps solving your problem.
I bet it will!

Thanks again for your very detailed and clear explanation of not only
what to fix but why. I'm sure this will put me on the path to success!



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-14 16:42:40 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.