Nico Kadel-Garcia a écrit :
> On Fri, May 13, 2011 at 11:32 AM, Eric Manceau
> <Eric.Manceau_at_ec-nantes.fr> wrote:
>> 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.
Thank you for the advise.
I was absolutely not aware of this compatibility problem on the client side.
>> Moreover I want to split an old repos in 2 new repos without losing revision
>> of my files :
>> Old Repo
>> |-- 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*?
That's an idea.
I will not use it first because I want to have a try with the original
But I will keep this solution for a later time.
Si vous recevez ce courriel par erreur, toutes mes coordonees sont dans "informations complémentaires" sur ma carte en piece jointe.
If you received this message in error, read "informations complementaires" in my card attached with this mail to contact me.
Received on 2011-05-16 09:34:05 CEST