Branko Čibej wrote on Wed, Dec 21, 2016 at 11:48:55 +0100: > [1] Except that, when using the file:// protocol, it is *highly > recommended* to for the client and server to be the same version. In the > case of administration tools (svnadmin, svnlook, etc.), version parity > is required.
All these — svnadmin, svnlook, and svn over file:// — access a repository on-disk directly, without a mediating server. In these cases, there _is_ in fact a certain amount of leeway — the 1.5 svn* tools can read repositories created by 1.6, for example — but in general it's recommended to use just one version of svnadmin/svnlook/svn on a repository. (For example, because that minimises the chance of running into compatibility bugs.) In general, we promise for on-disk structures — i.e., for the part of the stack where neither svn:// nor http:// is involved — that 1.x.y can read data created by 1.a.b if x ≥ a; which notably includes the case that x=a and y<b. However, mixing versions, or downgrading, is not recommended. Cheers, Daniel > These are essentially server-side restrictions and have > little bearing on a normal setup, when clients talk to the server using > the http:// or svn:// protocol. > > -- Brane > >
