Plus, you need to set a number of properties on the zeroeth revision of
the target repository (if I recall correctly) and add a hook script for
the sync user to be allowed to modify revision commit text in order for
svnsync to run successfully. (And delete the revo #0 properties when
you're done, though I don't think that was essential). Look in the red
bean book at svnsync.
Tony.
-----Original Message-----
From: Gingko [mailto:from_tigris_at_nospam.homelinux.org]
Sent: 06 November 2010 01:02
To: Subversion User List
Subject: Re: Promoting a mirror repository as a source repository
----- Original Message -----
From: "Andrey Repin" <anrdaemon_at_freemail.ru>
To: "Gingko" <from_tigris_at_nospam.homelinux.org>;
<users_at_subversion.apache.org>
Sent: Saturday, November 06, 2010 1:30 AM
Subject: Re: Promoting a mirror repository as a source repository
> Greetings, Gingko!
>
>> I have a (now theoretical) question :
>
>> Suppose I have a repository that is a mirror repository of a remote
>> source
>> repository, regularly synced using svnsync.
>
>> Suppose now that the source repository become broken or deleted for
any
>> reason (server breakdown, fire, etc)
>> So the only available copy of the repository is now the synced mirror
>> repository.
>
>> How could I promote my mirror repository in order to have it becoming
the
>> new source repository on the mirror server or on another server ?
>
>> (I think that just using the mirror repository without change is not
>> enough
>> as it contains somewhere inside it information about the old source
>> repository, given at the beginning by "svnsync initialize", which
would
>> certainly need to be removed)
>
> svn help switch
> http://svnbook.org/
Thank you very much for your answer, but I'm sorry, this is not an
answer to
my question.
"svn switch" is about changing URLs in working copies, I know how to do
this
(actually I made several of these changes today).
But what I want to know is what I have to do on the REPOSITORY side.
Gingko
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
Received on 2010-11-06 02:13:12 CET