Grab the UUID for old repository. When you create the new one, make sure use the UUID for that repository. Doing so will keep your users from having to do anything. To do this, when you create the new repo, use the '--force-uuid' switch.
Johnathan
>>> On Fri, Jan 26, 2007 at 9:31 AM, in message
<C1DF8918.318E%steven.bakke@amd.com>, "Steve Bakke" <steven.bakke@amd.com>
wrote:
> Hi all,
>
> I have a question regarding the necessary procedure for upgrading a 1.2.x
> repository to 1.4.x. I understand that you might get significant space
> savings by upgrading the format. My general question is whether or not
> doing this upgrade will impact users' working copies assuming that I don't
> change the repository location. Here was the general sequence of steps I
> was considering:
>
> 1. Disable checkins.
> 2. Do a full repository dump.
> 3. Reload dump into fresh repo.
> 4. Move the fresh repo in place of the old one. (rename the old one to
> something else.)
> 5. Enable checkins
>
> The main question was whether you have to create fresh working copies in
> this situation. If not that would be wonderful. If we do then I have to go
> through the hassle of requiring everyone to checkin their stuff.
>
> Any comments? Is the series of steps above correct? This really isn't much
> different from a backup/restore process.
>
> - Steve
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e- mail: users- unsubscribe@subversion.tigris.org
> For additional commands, e- mail: users- help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 26 16:38:22 2007