... | @@ -73,7 +73,8 @@ This implies that you will be submitted to the (hpefully minor) inconvenience of |
... | @@ -73,7 +73,8 @@ This implies that you will be submitted to the (hpefully minor) inconvenience of |
|
your current working copies.
|
|
your current working copies.
|
|
|
|
|
|
For example, my working copy of spec-sw has the following remotes:
|
|
For example, my working copy of spec-sw has the following remotes:
|
|
```$ git remote -v
|
|
```
|
|
|
|
$ git remote -v
|
|
ohwr ssh://git@ohwr.org/fmc-projects/spec/spec-sw.git (fetch)
|
|
ohwr ssh://git@ohwr.org/fmc-projects/spec/spec-sw.git (fetch)
|
|
ohwr ssh://git@ohwr.org/fmc-projects/spec/spec-sw.git (push)
|
|
ohwr ssh://git@ohwr.org/fmc-projects/spec/spec-sw.git (push)
|
|
origin git://ohwr.org/fmc-projects/spec/spec-sw.git (fetch)
|
|
origin git://ohwr.org/fmc-projects/spec/spec-sw.git (fetch)
|
... | @@ -87,12 +88,14 @@ the project page, i.e. |
... | @@ -87,12 +88,14 @@ the project page, i.e. |
|
```
|
|
```
|
|
and issue the commands
|
|
and issue the commands
|
|
|
|
|
|
```$ git remote set-url origin https://ohwr.org/project/spec-sw.git
|
|
```
|
|
|
|
$ git remote set-url origin https://ohwr.org/project/spec-sw.git
|
|
$ git remote set-url ohwr ssh://git@ohwr.org:7999/project/spec-sw.git
|
|
$ git remote set-url ohwr ssh://git@ohwr.org:7999/project/spec-sw.git
|
|
```
|
|
```
|
|
Now you're set:
|
|
Now you're set:
|
|
|
|
|
|
```$ git remote -v
|
|
```
|
|
|
|
$ git remote -v
|
|
ohwr ssh://git@ohwr.org:7999/project/spec-sw.git (fetch)
|
|
ohwr ssh://git@ohwr.org:7999/project/spec-sw.git (fetch)
|
|
ohwr ssh://git@ohwr.org:7999/project/spec-sw.git (push)
|
|
ohwr ssh://git@ohwr.org:7999/project/spec-sw.git (push)
|
|
origin https://ohwr.org/project/spec-sw.git (fetch)
|
|
origin https://ohwr.org/project/spec-sw.git (fetch)
|
... | @@ -109,7 +112,17 @@ To avoid this scenario, we have tried our best to keep mirrors of the old reposi |
... | @@ -109,7 +112,17 @@ To avoid this scenario, we have tried our best to keep mirrors of the old reposi |
|
|
|
|
|
This is the least horrible way we have found till now to keep unbroken builds in case old repository URLs (and commits) are referenced. In particular, remote URLs with intermediate path components other than `/project/` are certain to be *invalid* for any other purpose than the uses former submodule references gave to them.
|
|
This is the least horrible way we have found till now to keep unbroken builds in case old repository URLs (and commits) are referenced. In particular, remote URLs with intermediate path components other than `/project/` are certain to be *invalid* for any other purpose than the uses former submodule references gave to them.
|
|
|
|
|
|
If this sounds terrible, it is, but the sentence at the beginning says it all.
|
|
If this sounds terrible, it is, but the sentence at the beginning says it all. Below are 3 simple steps to update URLs to the submodules and have your project working fine again:
|
|
|
|
1. In the top folder of your repository with submodules, edit manually the file .gitmodules updating the URLs (for each submodule project, see what is the new HTTPS URL)
|
|
|
|
2. Synchronize URLs of submodules:
|
|
|
|
```
|
|
|
|
$ git submodule sync
|
|
|
|
```
|
|
|
|
3. add and commit the change
|
|
|
|
```
|
|
|
|
$ git add .gitmodules
|
|
|
|
$ git commit -m "update of submodule URLs after OHWR migration"
|
|
|
|
```
|
|
|
|
|
|
### Files
|
|
### Files
|
|
* [notification-users-ohwr.org](/uploads/d6595f47e1b40eb473fa9307fe860dff/notification-users-ohwr.org)
|
|
* [notification-users-ohwr.org](/uploads/d6595f47e1b40eb473fa9307fe860dff/notification-users-ohwr.org)
|
... | | ... | |