Upgrading eclipse-titan in the Osmocom OBS » History » Version 4
osmith, 05/27/2024 08:23 AM
store the debian packaging in a git repository
| 1 | 1 | osmith | h1. Upgrading eclipse-titan in the Osmocom OBS |
|---|---|---|---|
| 2 | |||
| 3 | 4 | osmith | This article explains how maintainers of obs.osmocom.org can upgrade the eclipse-titan package or add patches to it, e.g. to fix building against a newer GCC. |
| 4 | 1 | osmith | |
| 5 | Running the testsuite against new/different versions of eclipse can be done with *-titan-master in docker-playground (see "this patch":https://gerrit.osmocom.org/c/docker-playground/+/31623). |
||
| 6 | |||
| 7 | 4 | osmith | h2. Find the Osmocom git repository |
| 8 | 1 | osmith | |
| 9 | 4 | osmith | The OBS package gets built from a git repository. Find the path to it in @osmo-ci/scripts/obs/update_obs_eclipse_titan.sh@. As of writing: https://gitea.osmocom.org/osmith/titan.core |
| 10 | 1 | osmith | |
| 11 | 4 | osmith | h2. Add patches to current version |
| 12 | 1 | osmith | |
| 13 | 4 | osmith | Push a patch to the current branch, e.g. @osmocom/9.0.0@. Then run: |
| 14 | 1 | osmith | <pre> |
| 15 | 4 | osmith | $ ./update_obs_eclipse_titan.sh PROJ |
| 16 | 1 | osmith | </pre> |
| 17 | |||
| 18 | 4 | osmith | Replace @PROJ@ with @home:yourusername@ first, to build the package there and test it. Afterwards set @PROJ@ to @osmocom:latest@. |
| 19 | 1 | osmith | |
| 20 | 4 | osmith | h3. Upgrade the version |
| 21 | 1 | osmith | |
| 22 | 4 | osmith | * Clone the git repository |
| 23 | * Add the upstream repository as second remote: https://gitlab.eclipse.org/eclipse/titan/titan.core/ |
||
| 24 | * Push the git tag of the next version to the Osmocom git repository (this is needed, so the package version gets calculated properly) |
||
| 25 | * Rebase the @osmocom/<OLD-VERSION>@ branch on that release tag |
||
| 26 | * Create a @osmocom/<NEW-VERSION>@ branch based on that rebase |
||
| 27 | * Run @update_obs_eclipse_titan.sh@ as described above |
