Confirmed users
4,971
edits
ReleaseEngineering/How To/VCSSync: Difference between revisions
ReleaseEngineering/How To/VCSSync (view source)
Revision as of 22:31, 14 October 2013
, 14 October 2013→How to start a mozilla-central based repo conversion from scratch
| Line 53: | Line 53: | ||
=== How to start a mozilla-central based repo conversion from scratch === | === How to start a mozilla-central based repo conversion from scratch === | ||
0a3243fe5a6c8ffa4e47131e0eb0243e1f5676ea3cacd535d11b424f8f601511130a2e941670950b63c0b00726dafa9bd30bf7c3d040752fce824158021ef014 | # First, you need a copy of initial3.tar.bz2. This is mozilla-central-with-cvs-history, already converted to git for you, up to Spring, 2013. Without this file, you will need to run the [http://hg.mozilla.org/build/mozharness/file/7d9425c91051/scripts/vcs-sync/initial_beagle.py initial conversion] with [http://hg.mozilla.org/build/mozharness/file/7d9425c91051/configs/vcs_sync/gecko-git.py this config file] (or beagle) and let it run for about a week. | ||
#* The sha512 sum is <code>0a3243fe5a6c8ffa4e47131e0eb0243e1f5676ea3cacd535d11b424f8f601511130a2e941670950b63c0b00726dafa9bd30bf7c3d040752fce824158021ef014</code> | |||
#* This file exists on vcssync{1,2} at /opt/vcs2vcs/initial3.tar.bz2 , on github-sync{2,4} at /home/asasaki/initial3.tar.bz2 , and on Aki's laptop. | |||
== Troubleshooting == | == Troubleshooting == | ||