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

Re: TortoiseSVN and Apache subversion version compatibility

From: Andy Levy <andy.levy_at_gmail.com>
Date: Fri, 18 Oct 2013 08:26:03 -0400

On Thu, Oct 17, 2013 at 6:16 PM, Anthony Perlinski <awperli_at_sandia.gov> wrote:
> I just upgraded my TortoiseSVN (Windows 7, 64-bit) to 1.8.2. Now I cannot access my repository which is at subversion 1.7 (or earlier). I have access to another repository that is at subversion 1.8 and I do not have any issues accessing the repository.
> If someone knows for sure, I would like to verify that this is indeed a version issue. Is it true that 1.8 cannot access repositories with a subversion version of 1.7 or earlier? I have seen articles that state that TortoiseSVN 1.8 is backwards compatible with earlier versions (pre 1.8) of subversion 1.8.

When using remote access (svnserve, Apache) for a repository, all 1.x
clients are compatible with all 1.x servers. When mixing minor
versions, some features may be disabled because one end or the other
doesn't support them. There have been some glitches with the change in
HTTP library with 1.8 but "I cannot access my repository" is not
enough information to say if that's what's happening to you.

I would not recommend mixing client versions when accessing via the
file:/// scheme - it *may* work, but there may be some oddities. You
shouldn't be using this scheme anyway except for a single-user
scenario with the repository stored locally.

Working copies can only be accessed by multiple client versions if
those clients have matching minor numbers - a working copy that needs
to be accessed by a 1.6 client can only be accessed by other 1.6
clients, for example.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-10-18 14:26:47 CEST

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

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