Confirm
4,971
edits
Changes
→How to start a mozilla-central based repo conversion from scratch
#* 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.
# Second, you need a config file for the conversion type. This is probably covered with the beagle, gecko-git, and project-branches config files [http://hg.mozilla.org/build/mozharness/file/7d9425c91051/configs/vcs_sync here].
#Clone the appropriate mozharness repo + branch (see [https://wiki.mozilla.org/ReleaseEngineering/VCSSync/HowTo#Branch here], unless you're working off a separate development branch). This will go into the base_work_dir. For instance, if you want to use <code>/opt/vcs2vcs</code> as the base_work_dir, this will be <code>/opt/vcs2vcs/mozharness</code> .# Extract the contents of initial3.tar.bz2 into the appropriate location. For instance, if I want to use /opt/vcs2vcs/ as my base_work_dir, and I'm using [http://hg.mozilla.org/build/mozharness/file/7d9425c91051/configs/vcs_sync/gecko-git.py#l21 this config file] (which specifies "gecko-git" as my conversion_dir), I'll need to move some files around.<pre>cd /opt/vcs2vcstar xjvf initial3.tar.bz2 # this creates conversion/beaglemkdir -p build/conversion# move the extracted directory from initial3.tar.bz2 to where# the mozharness script expects the gecko-git conversion dir to bemv conversion/beagle build/conversion/gecko-git</pre>
== Troubleshooting ==
