revisiting this old thread... i noticed from the committers' page on the spark site that the 'apache' remote should be 'github.com', and not 'gitbox' as instructed here.
so, i did a quick check of the spark repo and found we're still referencing gitbox in a few places: ➜ spark git:(fix-run-tests) grep -r gitbox * dev/create-release/release-tag.sh:ASF_SPARK_REPO=" gitbox.apache.org/repos/asf/spark.git" dev/create-release/release-util.sh:ASF_REPO=" https://gitbox.apache.org/repos/asf/spark.git"; dev/create-release/release-util.sh:ASF_REPO_WEBUI=" https://gitbox.apache.org/repos/asf?p=spark.git"; pom.xml: <developerConnection>scm:git: https://gitbox.apache.org/repos/asf/spark.git</developerConnection> should we update these entries to point to github vs gitbox? On Mon, Dec 10, 2018 at 8:30 AM Sean Owen <sro...@apache.org> wrote: > Per the thread last week, the Apache Spark repos have migrated from > https://git-wip-us.apache.org/repos/asf to > https://gitbox.apache.org/repos/asf > > > Non-committers: > > This just means repointing any references to the old repository to the > new one. It won't affect you if you were already referencing > https://github.com/apache/spark . > > > Committers: > > Follow the steps at https://reference.apache.org/committer/github to > fully sync your ASF and Github accounts, and then wait up to an hour > for it to finish. > > Then repoint your git-wip-us remotes to gitbox in your git checkouts. > For our standard setup that works with the merge script, that should > be your 'apache' remote. For example here are my current remotes: > > $ git remote -v > apache https://gitbox.apache.org/repos/asf/spark.git (fetch) > apache https://gitbox.apache.org/repos/asf/spark.git (push) > apache-github git://github.com/apache/spark (fetch) > apache-github git://github.com/apache/spark (push) > origin https://github.com/srowen/spark (fetch) > origin https://github.com/srowen/spark (push) > upstream https://github.com/apache/spark (fetch) > upstream https://github.com/apache/spark (push) > > In theory we also have read/write access to github.com now too, but > right now it hadn't yet worked for me. It may need to sync. This note > just makes sure anyone knows how to keep pushing commits right now to > the new ASF repo. > > Report any problems here! > > Sean > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > > -- Shane Knapp UC Berkeley EECS Research / RISELab Staff Technical Lead https://rise.cs.berkeley.edu
