PSA: Shutting down my mozilla git mirror in three weeks

Aki Sasaki aki at mozilla.com
Mon Nov 25 21:46:35 UTC 2013


Github has closed access to https://github.com/mozilla/mozilla-central :

    This repository has been disabled.
    Access to this repository has been disabled by GitHub staff.
    Contact support to restore access to this repository.

We're currently trying to reach github support to reverse this decision;
it would be much better to do a scheduled rollout than have to scramble
like this.

In the meantime, if you rely on git-based mozilla-central and can move
to gecko-dev sooner, please do so.  gecko-dev is also on
git.mozilla.org, so should the same thing happen there, we have more
options.

If you require support to switch, let's take over #git and see if we can
figure this out together.

On 11/25/13 7:39 AM, Ehsan Akhgari wrote:
> Dear all,
> 
> For the past two and a half years I have been maintaining a git mirror of
> mozilla-central plus a lot of the other branches that people found useful
> at https://github.com/mozilla/mozilla-central.  Over the years this proved
> to be too much work for me to keep up with, and given the existence of the
> new git mirrors that are supported by RelEng, I'm planning to shut down the
> update jobs for this repository on Friday, Dec 13, 2013 and take the
> repository down.
> 
> I strongly suggest that if you have been using and relying on this
> repository before, please consider switching to the RelEng repositories as
> soon as possible.  https://github.com/mozilla/gecko-dev is the main
> repository where you can find branches such as trunk/aurora/b2g
> branches/etc and https://github.com/mozilla/gecko-projects is a repository
> which contains project branches and twigs.  (Note that my repository hosts
> all of these branches in a single location, but from now on if you use both
> of these branch subsets you will need to have two upstream remotes added in
> your local git clone.)
> 
> The RelEng repositories have a similar history line including the CVS
> history but they have completely different commit SHA1s, so pulling that
> repo into your existing clones is probably not what you want.  If you don't
> have a lot of non-merged branches, your safest bet is cloning from scratch
> and then port your existing branches manually.  If you have a lot of local
> branches, you may want to wait for the script that John Schoenick is
> working on in bug 929338 which will assist you in rebasing those branches
> on top of the new history line.
> 
> Last but not least, I really hate to have to disrupt your workflow like
> this.  I do hope that three weeks is enough advance notice for everybody to
> successfully switch over to the new mirrors, but if you have a reason for
> me to delay this please let me know and I will do my best to accommodate.
> 
> Cheers,
> --
> Ehsan
> <http://ehsanakhgari.org/>
> 




More information about the firefox-dev mailing list