1017464 - New git repositories to mirror for Flame

Status: RESOLVED FIXED

(Developer Services :: Mercurial: hg.mozilla.org, defect)

Description

[:gerard-majax]

We would need to fork and mirror on github and git.mozilla.org a couple of repositories for the Flame:

https://github.com/t2m-foxfone/kernel_msm
https://github.com/t2m-foxfone/platform_bootable_recovery
https://github.com/t2m-foxfone/kernel_lk

Comment 1

[viral [:viralwang]]

base on https://bugzilla.mozilla.org/show_bug.cgi?id=1008809#c7
We also need the mirror on git.mozilla.org

https://github.com/t2m-foxfone/platform_external_libnfc-nci.git

Comment 2

[:gerard-majax]

Michael, in bug 1016934 we landed stuff to use init.rc from system/core mainly for nfc stuff, but the root repo is CAF. Should we fork this CAF repo or get the T2M changed merged in CAF ?

Comment 3

[Hal Wine [:hwine] use NI!]

It is unclear what the request is here. We only provide mirroring services.

There are likely 2 cases for each of the , either:
 a) the above repos are perfect the way they are, and only need to be mirrored for the builds
 b) FFOS changes need to be made to those repos, and they need to be forked into the mozilla-b2g account on github.

All forking is handled by b2g development team. One the forks are created, please request the mirror for build purposes.

Please let me know how we can improve our documentation at https://wiki.mozilla.org/ReleaseEngineering/RepositoryCreationRequest#Requester.27s_Actions: to clarify this for future requesters.

Comment 4

[:gerard-majax]

Okay, my fault, I misunderstood your attributions. We need to fork the repos on github to the mozilla-b2g account and then we need your help to mirror them to git.mozilla.org :)

Comment 5

[:gerard-majax]

Michael or john, I think we need you to do the fork of the repos in comment 1 on the mozilla-b2g github account so that we can then mirror them on git.mozilla.org.

Comment 6

[Michael Wu [:mwu]]

(In reply to Alexandre LISSY :gerard-majax from comment #2)
> Michael, in bug 1016934 we landed stuff to use init.rc from system/core
> mainly for nfc stuff, but the root repo is CAF. Should we fork this CAF repo
> or get the T2M changed merged in CAF ?

I looked at the init.rc changes - looks like a lot of stuff that should've been in other init files like init.target.rc or init.qcom.rc. I think we can cherrypick the changes into a fork of init.target.rc or init.qcom.rc.

Comment 7

[viral [:viralwang]]

Hi Hwine,

For libnfc-nci, we don't need to modify the code in our side and only need to be mirrored for the builds
https://github.com/t2m-foxfone/platform_external_libnfc-nci.git

Shall I need to open a new bug to request again since there are difference cases in those repositories?
Thanks

Comment 8

[:gerard-majax]

(In reply to Alexandre LISSY :gerard-majax from comment #5)
> Michael or john, I think we need you to do the fork of the repos in comment
> 1 on the mozilla-b2g github account so that we can then mirror them on
> git.mozilla.org.

Looks like I forgot to needinfo? someone :)

Comment 9

[Hal Wine [:hwine] use NI!]

(In reply to viral [:viralwang] from comment #7)
> Shall I need to open a new bug to request again since there are difference
> cases in those repositories?
> Thanks

Either way -- what I need is a list of the upstream URLs for the repositories to mirror. There is no difference in the mirror operation, just on where the upstream repo is.

Since there are so many moving parts, I'd suggest the following:
 - get all the repos forked & modified as needed
 - have a dev build that builds/works with those repos
 - ask for the mirrors to be done
 - land your manifest changes when mirrors are in place

That will minimize any possible breakage of master as these are rolled into production.

Comment 10

[:gerard-majax]

(In reply to Hal Wine [:hwine] (use needinfo) from comment #9)
> (In reply to viral [:viralwang] from comment #7)
> > Shall I need to open a new bug to request again since there are difference
> > cases in those repositories?
> > Thanks
> 
> Either way -- what I need is a list of the upstream URLs for the
> repositories to mirror. There is no difference in the mirror operation, just
> on where the upstream repo is.
> 
> Since there are so many moving parts, I'd suggest the following:
>  - get all the repos forked & modified as needed
>  - have a dev build that builds/works with those repos
>  - ask for the mirrors to be done
>  - land your manifest changes when mirrors are in place
> 
> That will minimize any possible breakage of master as these are rolled into
> production.

That was the plan. Repos are forked on github:
 - https://github.com/mozilla-b2g/kernel_lk
 - https://github.com/mozilla-b2g/kernel_msm
 - https://github.com/mozilla-b2g/platform_bootable_recovery

Comment 11

[Michael Wu [:mwu]]

We already have a msm kernel repo. Can you switch to a branch on that repo?

Comment 12

[Jed Davis [:jld] ⟨⏰|UTC-7⟩ ⟦he/him⟧]

(In reply to Michael Wu [:mwu] from comment #11)
> We already have a msm kernel repo. Can you switch to a branch on that repo?

I took care of this: https://github.com/mozilla-b2g/codeaurora_kernel_msm/tree/t2m-flame-3.4-jb (copied from t2m branch "foxfone-one")

a=mwu via IRC.

Comment 13

[Hal Wine [:hwine] use NI!]

codeaurora_kernel_msm was already being mirrored

The following additional mirrors are now active:

https://github.com/mozilla-b2g/kernel_lk -> https://git.mozilla.org/b2g/kernel_lk
https://github.com/mozilla-b2g/platform_bootable_recovery -> https://git.mozilla.org/b2g/platform_bootable_recovery

In production via:
 http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/rev/e0a401d75764