In order to be able to build tcpdump for jb/kk flavors based devices, please mirror those repo to git.mozilla.org: - libpcap, needed as a dependency, from https://www.codeaurora.org/cgit/external/gigabyte/platform/external/libpcap/ - tcpdump itself, from https://www.codeaurora.org/cgit/external/gigabyte/platform/external/tcpdump/

deployed with http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/49c1e397c3d1 Live as: http://git.mozilla.org/external/gigabyte/platform/external/libpcap.git http://git.mozilla.org/external/gigabyte/platform/external/tcpdump.git

https://android.googlesource.com/platform/external/libpcap/ https://android.googlesource.com/platform/external/tcpdump/

Hal, sorry, but can you fix my mistake ?

Alexandre -- just to confirm, you're asking for: 1) current libpcap & tcpdump to be removed from mirror 2) new mirror of the repositories in comment 2

(In reply to Hal Wine [:hwine] (use needinfo) from comment #4) > Alexandre -- just to confirm, you're asking for: > 1) current libpcap & tcpdump to be removed from mirror > 2) new mirror of the repositories in comment 2 Yes, that's this. Sorry for the mistake the first time :(

repos from comment 2 now in production with http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/ca15c54de92f will wait to close until old repos removed.

old comment 1 repos not mentioned in any current manifest. Stopped mirroring with http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/0fff04bf6937

bug 1036727 filed to remove old repositories from system. That doesn't impact use of the new repositories at all, so not marking as blocking.

As per https://bugzilla.mozilla.org/show_bug.cgi?id=1025788#c27: Michael and Alexandre, please can you (both) confirm that this is exactly what you want: * git://codeaurora.org/platform/external/libpcap => mirrored to => ssh://gitolite3@git.mozilla.org/external/caf/platform/external/libpcap.git * git://codeaurora.org/platform/external/tcpdump => mirrored to => ssh://gitolite3@git.mozilla.org/external/caf/platform/external/tcpdump.git Please be so kind and double check, as this will now be the third version of this request. Thanks, Pete

Given that I have never been able to find a way to get the list of repositories from CAF, I'm sorry for breaking stuff but when guessing ... I suspect the root repositories are the proper one, but I'm out for the magic of mirroring.

The lists are here - https://www.codeaurora.org/cgit/quic/la/ https://www.codeaurora.org/cgit/quic/lf/ The new mirrors in comment 9 look correct.

deployed to production and live with: http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/5924f6ede69e As previously, will leave open until old repos removed

Many thanks Hal!

(In reply to Michael Wu [:mwu] from comment #11) > The lists are here - > https://www.codeaurora.org/cgit/quic/la/ > https://www.codeaurora.org/cgit/quic/lf/ > > The new mirrors in comment 9 look correct. Excellent. I think we need to document this somewhere.

Agreed. Alexandre, as a person that would want to know this information, can you say where you would look for it? I can create a wiki page about b2g-manifest - but is there already a place where b2g-manifest information is described? I figure since you are a typical user that would want to read this information, you probably already have several information sources you would go to - and is probably best if we add it to that. Another option that occurs to me today - maybe while it is not entirely automatic yet, the dev could attach the b2g-manifest patch to a bugzilla ticket, and then file a dependent bug for release engineering off that first bug to set up the mirroring. We then have enough information (I realise now) to determine a) where the source repo is and b) where the mirror repo is, so we have enough information to manage the mirroring. If we choose to do this, also let me know where you think the best place is to document that. Another option is if only e.g. :mwu and a select group should review patches to b2g-manifest, maybe the write permissions to b2g-manifest should be reduced, so only :mwu and select others can merge in pull requests. Then we can also make sure the selected few with write permission know that a dependent bug needs to be filed. However, more and more, I think it might be best to implement the full solution, rather than multiple baby steps, and get it done. The b2g bumper knows the source and target repo for the mirroring, should be able to manage a list of such mappings, and feed them to vcs sync. If they don't exist in vcs sync, it should be able to add the config. It can then wait for vcs sync to do its job, and when it sees that the target repo has been created, it can then put the frozen version in the manifest pertaining to the new repo. Thoughts?

no work left at this point. Operations as of comment 12