You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Eric Manceau <Er...@ec-nantes.fr> on 2011/05/13 17:32:23 UTC
subversion 1.4.2
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?
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.
Best regards,
E. MANCEAU
Re: subversion 1.4.2
Posted by Eric Manceau <Er...@ec-nantes.fr>.
Nico Kadel-Garcia a écrit :
> On Fri, May 13, 2011 at 11:32 AM, Eric Manceau
> <Er...@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.
>
>
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
>> |--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*?
>
That's an idea.
I will not use it first because I want to have a try with the original
first.
But I will keep this solution for a later time.
Best Regards.
Eric
--
+++
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.
Re: subversion 1.4.2
Posted by Nico Kadel-Garcia <nk...@gmail.com>.
On Fri, May 13, 2011 at 11:32 AM, Eric Manceau
<Er...@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*?
Re: subversion 1.4.2
Posted by Eric Manceau <Er...@ec-nantes.fr>.
Thorsten Schöning a écrit :
> Guten Tag Eric Manceau,
> am Freitag, 13. Mai 2011 um 17:50 schrieben Sie:
>
>
>> As you can see we want to gather all tests of several differents repos
>> into a unique repo but we want to keep revision of the original repos
>> and it seems to be hard to achieve.
>> Maybe impossible?
>>
>
> If disk space is not a problem, just copy your existing repository and
> delete unneeded folders during svn as a new revision. Upgrade
> subversion, dump your existing repository, create two new ones using
> svn 1.6.x and load your dump into both new repos. The new repository
> format will save you space anyway in most situations.
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
>
That is a wise way I should follow.
Thank you for all your help.
I shall go forward now.
Best Regard
Eric
--
+++
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.
Re: subversion 1.4.2
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Eric Manceau,
am Freitag, 13. Mai 2011 um 17:50 schrieben Sie:
> As you can see we want to gather all tests of several differents repos
> into a unique repo but we want to keep revision of the original repos
> and it seems to be hard to achieve.
> Maybe impossible?
If disk space is not a problem, just copy your existing repository and
delete unneeded folders during svn as a new revision. Upgrade
subversion, dump your existing repository, create two new ones using
svn 1.6.x and load your dump into both new repos. The new repository
format will save you space anyway in most situations.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning
AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig
Telefon: Potsdam: 0331-743881-0
E-Mail: tschoening@am-soft.de
Web: http://www.am-soft.de
AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam
Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
Re: subversion 1.4.2
Posted by Eric Manceau <Er...@ec-nantes.fr>.
Thanks for quick answer.
Bob Archer a écrit :
>> 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?
>>
>
> Yes... make sure you svn upgrade the repo or do a dump/load cycle to bring it up to the newest repository format.
>
Okay I will have a try.
>
>
>> 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?
>>
>
> Not sure what you meant by "did not help". That is the primary method for moving a subset of paths from one repository to another. Do you really NEED to break it into two repositories? What is the reason you want to do this, it might not be necessary.
>
> BOb
>
I did use svndumpfilter to isolate test and load into New Repo 2 but
after checking we notice that the new repos did not hold the last
revision of a file but instead an old one.
Sorry about my schema which is false.
Here is the corrected version :
New Repo 2
| --test
As you can see we want to gather all tests of several differents repos
into a unique repo but we want to keep revision of the original repos
and it seems to be hard to achieve.
Maybe impossible?
Eric
--
+++
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.
RE: subversion 1.4.2
Posted by Bob Archer <Bo...@amsi.com>.
> 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?
Yes... make sure you svn upgrade the repo or do a dump/load cycle to bring it up to the newest repository format.
> 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?
Not sure what you meant by "did not help". That is the primary method for moving a subset of paths from one repository to another. Do you really NEED to break it into two repositories? What is the reason you want to do this, it might not be necessary.
BOb