Bazaar

need to move shared repository to a different machine

Asked by pkommoju

I have a need to move a shared repository from one machine to another because the existing machine is being decomissioned. The shared repository has many branches representing the different versions of the same product. Some of these branches are frozen in maintenance mode, meaning no changes from older product branch will be pushed into new product branch.

I am trying to figure out a way to move this shared repository with all these branches to another machine such that the branches in new repository (on new machine) keep the history and all references resolve into the new repository branches.

Graphically, what I have is something like this:

r10.10.10 -->|
                    |--> r10.4.0
                    |--> r10.5.0 -->|
                                           |--> r10.5.2
                                           |--> r10.5.4
                                           |--> r10.5.5
                                           |--> r10.6.1
                                           |--> r10.8.0

r10.4.0 is frozen. r10.5.0 or its children will not be merged into r10.10.10, and none of r10.5.0 except r10.8.0 will be merged into r10.5.0.

After migrating this repository to new machine I need the exact same relation to hold within the new repo.

If I clone these repository or create clones of these branches branches on the new machine, I think they will still refer to the old machine (and the repository and branches therein).

How do I go about achieving what is needed?

Thanks in advance.

Question information

Language:
English Edit question
Status:
Answered
For:
Bazaar Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
John A Meinel (jameinel) said : 		#1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

If you know that the machine is quiet, you should be able to just "cp
- -r" the repository and all branches to the new machine.

If you put it in the same path on disk, all the links should continue
to just work.

John
=:->

On 2013-05-13 11:16, pkommoju wrote:
> New question #228746 on Bazaar:
> https://answers.launchpad.net/bzr/+question/228746
>
> I have a need to move a shared repository from one machine to
> another because the existing machine is being decomissioned. The
> shared repository has many branches representing the different
> versions of the same product. Some of these branches are frozen in
> maintenance mode, meaning no changes from older product branch will
> be pushed into new product branch.
>
> I am trying to figure out a way to move this shared repository with
> all these branches to another machine such that the branches in new
> repository (on new machine) keep the history and all references
> resolve into the new repository branches.
>
> Graphically, what I have is something like this:
>
>
> r10.10.10 -->| |--> r10.4.0 |--> r10.5.0 -->| |--> r10.5.2 |-->
> r10.5.4 |--> r10.5.5 |--> r10.6.1 |--> r10.8.0
>
> r10.4.0 is frozen. r10.5.0 or its children will not be merged into
> r10.10.10, and none of r10.5.0 except r10.8.0 will be merged into
> r10.5.0.
>
> After migrating this repository to new machine I need the exact
> same relation to hold within the new repo.
>
> If I clone these repository or create clones of these branches
> branches on the new machine, I think they will still refer to the
> old machine (and the repository and branches therein).
>
> How do I go about achieving what is needed?
>
> Thanks in advance.
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlGTWlEACgkQJdeBCYSNAAMDvQCbBVAZ52tV2mEy7r3IYiiNW7Y1
r5gAn3BD3l8ASx4bgD5VUvJyEA+NRc4U
=0K+c
-----END PGP SIGNATURE-----

Can you help with this problem?

Provide an answer of your own, or ask pkommoju for more information if necessary.

To post a message you must log in.