Bug #5650
closedgit.osmocom.org: not available via https://
0%
Description
OsmoUPF is available at git.osmocom.org via old git:// protocol:
git clone git://git.osmocom.org/osmo-upf Cloning into 'osmo-upf'... remote: Enumerating objects: 970, done. remote: Counting objects: 100% (970/970), done. remote: Compressing objects: 100% (813/813), done. remote: Total 970 (delta 537), reused 295 (delta 131), pack-reused 0 Receiving objects: 100% (970/970), 266.32 KiB | 432.00 KiB/s, done. Resolving deltas: 100% (537/537), done.
but not via https://
git clone https://git.osmocom.org/osmo-upf fatal: destination path 'osmo-upf' already exists and is not an empty directory.
It's also not accessible in cgit: https://cgit.osmocom.org/osmo-upf/.
Updated by fixeria over 1 year ago
I posted wrong output for https://, it should be:
git clone https://git.osmocom.org/osmo-upf Cloning into 'osmo-upf'... fatal: repository 'https://git.osmocom.org/osmo-upf/' not found
Updated by fixeria over 1 year ago
- Assignee set to laforge
By the way, this is why master-osmo-upf job is currently broken.
https://jenkins.osmocom.org/jenkins/view/master/job/master-osmo-upf/932/
https://jenkins.osmocom.org/jenkins/view/master/job/master-osmo-upf/933/
https://jenkins.osmocom.org/jenkins/view/master/job/master-osmo-upf/934/
...
Updated by neels over 1 year ago
osmith your patch is fixing this issue, right? https://gerrit.osmocom.org/c/osmo-ci/+/29153
Updated by osmith over 1 year ago
neels wrote in #note-3:
osmith your patch is fixing this issue, right? https://gerrit.osmocom.org/c/osmo-ci/+/29153
yes
Updated by laforge over 1 year ago
- Status changed from New to Rejected
Those redirects from https://git.osmocom.org/repo to https://git.osmocom.org/org/repo were added for backwards copatibility of old projects, i.e. projects that existed before we introduced gitea, where people already had clones of old URLs.
I don't think it is a good idea to start introducing those HTTP redirects to our nginx proxy for newly introduced projects like osmo-upf. This just means additional effort to maintain those manually, defeating the purpose of being able to create new projects in gerrit or gitea via the UI or API.
