Sync two repos for dolphin builds on master

RESOLVED FIXED

Status

Developer Services
Mercurial: hg.mozilla.org
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: nthomas, Unassigned)

Tracking

Details

Attachments

(1 attachment)

From b2g_bumper with spreadtrum added as a mapping:

15:01:20     INFO - needs sync? http://sprdsource.spreadtrum.com:8085/b2g/android/platform/external/libpcap -> https://git.mozilla.org/external/sprd-aosp/platform/external/libpcap
15:01:20     INFO - needs sync? http://sprdsource.spreadtrum.com:8085/b2g/android/platform/external/tcpdump -> https://git.mozilla.org/external/sprd-aosp/platform/external/tcpdump
mwu, hwine asked me to check that this build should be using sprd repos here, rather than something like caf. It seems to come in via dolphin.xml including base-kk.xml, then setting the default to sprd-aosp.
Flags: needinfo?(mwu)
note to self - docs if we go ahead
  http://people.mozilla.org/~hwine/tmp/vcs2vcs/cookbook.html#mirroring-a-git-repository

Comment 3

3 years ago
Yeah that's correct. CAF is used for Nexus and Qualcomm devices, but other SoCs usually have their own sets of full mirrors.
Flags: needinfo?(mwu)
Created attachment 8475061 [details] [diff] [review]
[repo-sync-configs] As generated by create_repo.py

I've done up to the end of step 5 at http://people.mozilla.org/~hwine/tmp/vcs2vcs/cookbook.html#mirroring-a-git-repository (probably should have stopped a half step earlier than that, but oh well). Could you do a sanity check ?
Attachment #8475061 - Flags: review?(hwine)
Comment on attachment 8475061 [details] [diff] [review]
[repo-sync-configs] As generated by create_repo.py

lgtm - going through step 5 is fine -- I'll update the docs.
Attachment #8475061 - Flags: review?(hwine) → review+
Comment on attachment 8475061 [details] [diff] [review]
[repo-sync-configs] As generated by create_repo.py

https://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/c682e5e29238
Attachment #8475061 - Flags: checked-in+
In production on github-sync3.dmz.scl3 (is that the production box right now ? looks like it from quick inspection of github-sync[124]).
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(Assignee)

Updated

3 years ago
Product: Release Engineering → Developer Services
You need to log in before you can comment on or make changes to this bug.