NFC emulation should be moved into a separate library to ease sharing between emulators in the future. Please merge the attached pull request and setup the repository. The source repo is at https://github.com/tdz/platform_external_libnfcemu
Attachment #8479671 - Flags: review?(mwu)
Thanks Thomas! The next steps will be: * mwu reviews the patch * when we get an r+ from mwu, we (Release Engineering) will set up the mirroring * when the mirroring is in place, mwu can merge the pull request Regarding knowing which repository to mirror from and the new mirror to create to mirror to, all the information we need is in the patch you already provided (<project name="platform_external_libnfcemu" path="platform/external/libnfcemu" remote="b2g" />) so we don't require any further information. From: https://github.com/tdz/b2g-manifest/blob/bug-1054934/emulator-jb.xml#L4 we see b2g remote is defined here: https://github.com/tdz/b2g-manifest/blob/bug-1054934/base-jb.xml#L5 i.e.: the full repo url is git://github.com/mozilla-b2g/platform_external_libnfcemu From here we see where the mirror should be made available on git.mozilla.org: http://hg.mozilla.org/build/mozharness/file/26e71e92141f/configs/b2g_bumper/master.py#l75 i.e.: https://git.mozilla.org/b2g/platform_external_libnfcemu Translating this from an https to an ssh url, this would be: ssh://email@example.com/b2g/platform_external_libnfcemu So the mirroring required would be: git://github.com/mozilla-b2g/platform_external_libnfcemu -> ssh://firstname.lastname@example.org/b2g/platform_external_libnfcemu Problem ======= The source repository "git://github.com/mozilla-b2g/platform_external_libnfcemu" currently does not exist: https://github.com/mozilla-b2g/?query=platform_external_libnfcemu "We couldn't find any matching repositories." When this github repository is available, and the b2g-manifests patch has been r+'d by mwu, we can set up the mirroring. At the moment the mirroring would fail, since the source repo does not exist, to mirror from. Many thanks! Pete
I think there's some confusion (at least on my side). I have a repository in my Github account at https://github.com/tdz/platform_external_libnfcemu It should be copied to Mozilla's official B2G account, probably https://github.com/mozilla-b2g/platform_external_libnfcemu That repository will become the new 'upstream'.
Thanks Thomas. Hal, if mwu approves the b2g-manifests patch, who can/should create https://github.com/mozilla-b2g/platform_external_libnfcemu? Is any RelEng member entitled to do that? Pete
(In reply to Thomas Zimmermann [:tzimmermann] [:tdz] from comment #2) > I think there's some confusion (at least on my side). I have a repository in > my Github account at > > https://github.com/tdz/platform_external_libnfcemu > > It should be copied to Mozilla's official B2G account, probably > > https://github.com/mozilla-b2g/platform_external_libnfcemu > > That repository will become the new 'upstream'. Also for anyone else stumbling on this bug, this is worth a line or two of explanation: The repo can live on mozilla-b2g github account, but RelEng systems build from git.mozilla.org repositories. Therefore a one-time import of this repository is required to make it available under the mozilla-b2g github account, and then subsequently the mirroring request takes care of actively keeping git.mozilla.org updated with changes as and when they land on mozilla-b2g github account, so that they remain in sync.
Summing up the questions for mwu: - Are you okay adding https://github.com/tdz/platform_external_libnfcemu to the builds (r+ on patch can confirm that) - Any objection to moving the upstream repo to the mozilla-b2g account? Our systems run smoother if upstream is on a mozilla managed account in a case like this. - Assuming we're moving the repo -- do you want to do that or just let me know which teams should have access to the repo?
Flags: needinfo?(hwine) → needinfo?(mwu)
(In reply to Pete Moore [:pete][:pmoore] from comment #3) > Hal, > > Is any RelEng member entitled to do that? It's in the docs, but there may be additional issues depending on where upstream is located. I'll respond to this and comment 1 in more detail in email.
(In reply to Hal Wine [:hwine] (use needinfo) from comment #5) > Summing up the questions for mwu: > > - Are you okay adding https://github.com/tdz/platform_external_libnfcemu to > the builds (r+ on patch can confirm that) > > - Any objection to moving the upstream repo to the mozilla-b2g account? Our > systems run smoother if upstream is on a mozilla managed account in a case > like this. > We'll want to move it upstream to mozilla-b2g. > - Assuming we're moving the repo -- do you want to do that or just let me > know which teams should have access to the repo? I'll move/copy it. BTW, I'm going to rename the repo to libnfcemu since the platform_external prefixing is more for repos mirrored from upstream.
https://github.com/mozilla-b2g/libnfcemu now available.
Assignee: nobody → hwine
The repository seems to have been copied, but it's not been added to the manifest. Is there anything required from my side to make progress here?
You have a PR that adds it, but it needs to be updated to pull from https://github.com/mozilla-b2g/libnfcemu.
Comment on attachment 8479671 [details] Github pull request for manifest OK, updated the PR's manifest to include the correct repository.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Product: Release Engineering → Developer Services
You need to log in before you can comment on or make changes to this bug.