Re: 1.7 write-through proxy to 1.6 master

2011-08-04 Thread Daniel Shahaf
Philip Martin wrote on Thu, Jul 14, 2011 at 17:01:30 +0100: > It's possible to setup a 1.7 write-through proxy to a 1.6 master. Revisiting this thread: is it a fair conclusion that, in a write-through proxy setup, the proxy shouldn't be newer than the master, but the opposite is safe?

Re: 1.7 write-through proxy to 1.6 master

2011-07-15 Thread Philip Martin
Another potential problem is in the 1.7 "atomic revprops" capability. The 1.7 slave will proxy atomic revprop changes to the 1.6 master where the atomic change is not implemented. The master will do the old style overwrite, and the client will not be aware that this happened. The revprop change d

Re: 1.7 write-through proxy to 1.6 master

2011-07-14 Thread C. Michael Pilato
On 07/14/2011 01:16 PM, Philip Martin wrote: > "C. Michael Pilato" writes: > >> Another less-obvious one was with the introduction of merge >> tracking, where the repository format version dictated support (or lack >> thereof) for a client-visible feature. You might have had an existing 1.4 >> s

Re: 1.7 write-through proxy to 1.6 master

2011-07-14 Thread Philip Martin
"C. Michael Pilato" writes: > Another less-obvious one was with the introduction of merge > tracking, where the repository format version dictated support (or lack > thereof) for a client-visible feature. You might have had an existing 1.4 > server (no merge tracking), popped up a 1.5 slave when

Re: 1.7 write-through proxy to 1.6 master

2011-07-14 Thread Mark Phippard
On Thu, Jul 14, 2011 at 12:30 PM, C. Michael Pilato wrote: > On 07/14/2011 12:01 PM, Philip Martin wrote: >> It's possible to setup a 1.7 write-through proxy to a 1.6 master. > > It's also a really bad idea. I think that opinion is overly extreme. While it is certainly true that you cannot just

Re: 1.7 write-through proxy to 1.6 master

2011-07-14 Thread C. Michael Pilato
On 07/14/2011 12:01 PM, Philip Martin wrote: > It's possible to setup a 1.7 write-through proxy to a 1.6 master. It's also a really bad idea. The simple fact of the matter is that mixing and matching server versions in a WebDAV proxy configuration doesn't work. And it really never has without ca

1.7 write-through proxy to 1.6 master

2011-07-14 Thread Philip Martin
It's possible to setup a 1.7 write-through proxy to a 1.6 master. This works provided that the 1.7 proxy uses "SVNAdvertiseV2Protocol off", but if the proxy doesn't disable V2 it forwards V2 requests to the V1 master which results in ugly errors: svn: E175002: Commit failed (details follow): svn: