[op25-dev] migration of git.osmocom.org to gitea?

Dear Osmocom community, [please follow-up-to the openbsc(a)lists.osmocom.org mailing list, if there is any discussion, we don't want to drag it over tons of mailing lists in parallel] Back in February I was posting a related RFC, and now the migration is complete, at least for all externally visible aspects relevant to users and developers. I've tried to make it as backwards-compatible as possible, meaning that; * we do have https://gitea.osmocom.org/ by now * gitea is the primary system for all non-gerrit repositories (mostly projects outside the cellular network infrastructure), see e.g. https://gitea.osmocom.org/phone-side/osmo-qcdiag * gitea is a secondary/mirror for all gerrit hosted repositories (mostly projects within the cellular network infrastructure). Those repositories are marked as mirros with an icon next to the repository name, see e.g. https://gitea.osmocom.org/osmocom/libosmocore * https://cgit.osmocom.org/ renders the old cgit user interface for time to come * https://git.osmocom.org/ main page redirects to gitea * per-project https://git.osmocom.org/libosmocore redirects to the right gitea URL for each project (by means of a series of about 200 nginx rewrite rules). This also means that cloning from old https URLs remains working * cloning from the git:// URLs also remains working * deep links to individual commits, or to the /patch URL as used in our Dockerfiles for cache invalidation on source code change remain valid So this means that all existing links, search engines, read-only clones, etc. will continue to work for those repositories that were still created in the pre-gitea time. However, for developers with commit/push access to non-gerrit repositories, there are some changes: 1) you will neeed to create an account on https://gitea.osmocom.org/ - and register your SSH public key[s] there. Unfortunately due to a bug in redmine we cannot yet use the redmine OpenID provider, so you need to create a separate account. If you're missing permissions for certain respositories, please contact me by private mail or create an issue in https://osmocom.org/projects/osmocom-servers 2) you will need to change the git+ssh push URLs if you want to push to repositories *not* hosted on gerrit. I've attached a CSV file for the old vs. new URLs to https://osmocom.org/attachments/5148. You can change the URL in your .git/config files manually, or you can use the 'git remote set-url' command to do that. If something is not working as expected, please let me know. The main ticket for the gitea migration is https://osmocom.org/issues/5397 Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)