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

Re: subversion 1.4.2

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Sat, 14 May 2011 09:11:28 -0400

On Fri, May 13, 2011 at 11:32 AM, Eric Manceau
<Eric.Manceau_at_ec-nantes.fr> wrote:
> Hello,
>
> I am struggling with an old version of subversion : 1.4.2
> Is it safe for the repository to adopt the 1.6.16 version?

It's also *wise* to upgrade, especially if your older repo is using
the older and notoriously fragile Berkeley DB. Doing a dump and reload
to a clean, new, working repo with the same UUID manually set should
be invisibble to your clients.

Do review the upgrade notes from the "Red Book" at
http://svnbook.red-bean.com/. And be aware that any working copy you
touch with a Subversion 1.6 client will no longer be compatible with
Subversion 1.4 clients.

> Moreover I want to split an old repos in 2 new repos without losing revision
> of my files :
>
> Old Repo
>   |--data
>   |-- test
>
> New Repo 1
>   | --data
>
> New Repo 2
>   | --data
>
> Svndumpfilter with 1.4 did not help and the svn command as well so did the
> tools evolve in the 1.6 version in order to achieve this goal?
>
> Thank you for your answer.

They're better. The new repos will have to be distinct, with twho new uuid's.

Why not build a new, upgraded repo first, and then split *that*?
Received on 2011-05-14 15:11:57 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.