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

Re: Subversion 1.5 repository/client compatibility

From: Andy Levy <andy.levy_at_gmail.com>
Date: Mon, 2 Feb 2009 21:54:39 -0500

On Mon, Feb 2, 2009 at 20:03, <petesea_at_bigfoot.com> wrote:
> I was hoping someone could clarify a question with regards to
> compatibility...
>
> According to the 1.5 release notes:
>
> ... merge-tracking is not supported unless you upgrade the repository
> as well as the server
>
> OK..., but then later, with regards to "sharding", there's this:
>
> ... These repositories will only be compatible with other Subversion
> 1.5 clients...

I think you may have taken this quote out of context. Repository
sharding is transparent to the client, only the server libraries will
ever see the sharded directories. If you're using file:/// access,
then the client is also the server, so you'll need matching version
numbers in that case.

> Sooo... I read this to mean that in order to support the new
> merge-tracking features we need to upgrade the server and the repository.
> .. OK, that's fine. But I also read it to mean that if ANY user wants to
> use the new merge-tracking features, ALL users will need to upgrade their
> clients to 1.5... even the users that don't care about the new 1.5
> features?

All 1.x clients are compatible with all 1.x servers. When one is older
than the other, the newer features will be disabled for the operations
being performed. If you have some people doing merges with 1.5 clients
and your 1.5 server, and others doing merges with 1.4 clients and your
1.4 server, things could get a little messy.

> IS that really true? In other words, a 1.4 (or earlier) client can NOT
> access a 1.5 repository?
>
> Also... with regards to upgrading repositories. Can I upgrade ANY
> previous repository version with the 1.5 svnadmin upgrade command? ie, if
> I have a 1.2 or 1.3 repository can those be upgraded directly to 1.5 or do
> they need to first be upgraded to 1.4 (or 1.3)?

Yes, you should be able to do that upgrade. The existing revisions
will not be sharded (IIRC there's a python script that'll do it), you
won't get the improved diffing algorithm (which *may* save you a bunch
of space on the server), and you'll also need to run
svn-populate-node-origins-index per the release notes.

If you do the dump/load cycle, that will all be taken care of for you.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1094110

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-03 03:55:25 CET

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