Project

General

Profile

OBS Maintenance » History » Version 18

osmith, 03/14/2023 10:01 AM

1 3 osmith
h1. OBS Maintenance
2
3 2 osmith
{{>toc}}
4 1 osmith
5
6 14 laforge
The Osmocom [[binary packages]] are built with [[OBS]] (Open Build Service) hosted on "obs.osmocom.org":https://obs.osmocom.org. In order to do that, the jenkins jobs "Osmocom_OBS_latest":https://jenkins.osmocom.org/jenkins/job/Osmocom_OBS_latest_obs.osmocom.org/ / "_nightly":https://jenkins.osmocom.org/jenkins/job/Osmocom_OBS_nightly_obs.osmocom.org/ ("config":https://gitea.osmocom.org/osmocom/osmo-ci/src/branch/master/jobs/osmocom-obs.yml) checkout the source repositories and build debian *source* packages, then upload these to OBS.
7 1 osmith
8
h2. Install osc
9
10
Get the command-line client for managing OBS. When using for the first time, it will ask for the credentials.
11
12
<pre>
13
$ sudo apt install osc
14
$ osc ls
15
</pre>
16
17 15 osmith
h2. Upgrading specific packages
18
19
h3. eclipse-titan
20
21
See the article [[upgrading eclipse-titan in the Osmocom OBS]].
22
23
h3. nftables / libnftnl
24
25
As of writing, the nftables and libnftnl packages from the Osmocom OBS are linked to openSUSE.org:security:netfilter. When the package gets upgraded there, the build will fail in the Osmocom OBS with:
26
27
<pre>
28
[   29s] error: Bad source: /home/abuild/rpmbuild/SOURCES/libnftnl-1.2.4.tar.bz2: No such file or directory
29
</pre>
30
31
That is because the source tarballs get upgraded, but the spec file has differences and so it does not get upgraded automatically.
32
33
Diff the "upstream spec file":https://build.opensuse.org/package/view_file/security:netfilter/libnftnl/libnftnl.spec?expand=1 against the one in the Osmocom OBS and apply the changes, then it should work again.
34
35 16 osmith
<pre>
36
$ $EDITOR /tmp/upstream.spec  # put the upstream spec file here
37
$ mkdir /tmp/obs
38
$ cd /tmp/obs
39
$ osc co osmocom:nightly libnftnl
40
$ cd osmocom:nightly/libnftnl
41
$ diff libnftnl.spec /tmp/upstream.spec
42
$ $EDITOR libnftnl.spec  # apply changes
43
$ diff libnftnl.spec /tmp/upstream.spec  # verify
44
$ osc commit
45
$ rm -rf /tmp/obs
46
</pre>
47 1 osmith
48 16 osmith
Wait until the package has built, then copy it to the other feeds:
49
<pre>
50
$ osc copypac osmocom:nightly libnftnl osmocom:latest
51
$ osc copypac osmocom:nightly libnftnl osmocom:master
52
</pre>
53
54 18 osmith
Eventually the nftables version >= 1.0.2 that osmo-upf requires should make it into the distributions we support, at which point we can remove the nftables and libnftnl packages.
55 15 osmith
56 1 osmith
h2. Workflow for testing OBS configurations
57
58 4 osmith
OBS has a "project configuration":https://en.opensuse.org/openSUSE:Build_Service_prjconf, which may need to be adjusted to state preferred dependencies for example. Before we apply project configurations to the official Osmocom OBS projects, we can test them in our own OBS project. Copy the relevant package first (adjust the username accordingly in all following examples):
59 1 osmith
60
<pre>
61 11 laforge
$ osc copypac osmocom:nightly osmo-gsm-manuals home:osmith42
62 1 osmith
</pre>
63
64
Visit the site in your browser:
65 10 osmith
* https://obs.osmocom.org/package/show/home:osmith42/osmo-gsm-manuals
66 1 osmith
67
Set up build targets:
68 10 osmith
* https://obs.osmocom.org/project/add_repository_from_default_list/home:osmith42
69 1 osmith
70
The package should get added to the queue already.
71
72
Open your project config next to the osmocom:nightly one:
73 10 osmith
* https://obs.osmocom.org/project/prjconf/home:osmith42
74 11 laforge
* https://obs.osmocom.org/project/prjconf/osmocom:nightly
75 1 osmith
76
First copy everything from the Osmocom project over to your own project. Then make changes to your config, until the builds are working as expected (dependency problems are resolved etc.). Whenever you change the config, OBS will immediately re-evaluate the build dependencies, no need to upload the source packages again.
77
78
When everything works as expected, copy the config changes you have made to the Osmocom project (nightly and latest).
79
80 12 laforge
Note that changing osmocom's project config did not seem to have any effect. It seems that we really must change both @osmocom:nightly@ and @osmocom:latest@ instead.
81 1 osmith
82
h2. Workflow for modifying packages
83
84
h3. (Optional) modify the debian dir
85
86
* clone the source git repository
87
* make changes to the debian dir
88
* commit your changes
89
* push to a "user/..." branch
90
91
h3. Build source packages and upload to your own OBS project
92
93
* clone osmo-ci.git
94 13 laforge
* open "osmo-nightly-packages.sh":https://gitea.osmocom.org/osmocom/osmo-ci/src/branch/master/scripts/osmocom-nightly-packages.sh
95 1 osmith
* if you intend to make changes to the script, do them and commit the changes
96
* change "PROJ":https://git.osmocom.org/osmo-ci/tree/scripts/osmocom-nightly-packages.sh?id=dc5fc51c1fa76e64db774ecb9e71fc25ad6c46cd#n10 to home:USERNAME
97
* if you made changes to the debian dir, insert your branch name after the related "checkout line":https://git.osmocom.org/osmo-ci/tree/scripts/osmocom-nightly-packages.sh?id=dc5fc51c1fa76e64db774ecb9e71fc25ad6c46cd#n172 (e.g. <code>checkout osmo-gsm-manuals osmith/some-random-change</code>)
98
* run osmocom-nightly-packages.sh
99
* check in your browser if all packages have been built by OBS as expected (iterate until you get everything right)
100
101
When everything works fine, contribute your patches with [[Gerrit]] as usually.
102
103
h2. Troubleshooting
104
105
h3. Debian dir doesn't work for multiple debian versions
106
107
Following what has been done for osmo-trx:
108
* create the debian dir to work with the latest debian stable
109
* create a patch that would make it work with an earlier release (debian 8) and save it as debian/patches/build-for-debian8.patch
110
* adjust the osmocom-*-packages.sh scripts to upload a second debian source package, which has the patch applied
111
* configure OBS to build the patched package only for the older debian releases, and the unpatched package only for the stable release
112
113
h3. Package is not resolvable
114
115
<pre>
116
have choice for jadetex needed by docbook-utils: jadetex texlive-formats-extra
117
</pre>
118
119
You'll need to adjust the OBS project configuration (mind the testing workflow above):
120
<pre>
121
Prefer: texlive-htmlxml
122
</pre>
123
124 8 osmith
h3. Reproduce the nightly builds locally
125
126
<pre>
127
$ osc co
128
$ osc build
129
</pre>
130 1 osmith
131 9 osmith
h2. E-Mail Notifications of build failures
132
133
Build failure notifications are sent to the "gerrit-log mailing list":https://lists.osmocom.org/mailman/listinfo/gerrit-log
134
135 1 osmith
h2. See also
136
137
* https://en.opensuse.org/Portal:Build_Service
138
* https://en.opensuse.org/openSUSE:Build_Service_prjconf
Add picture from clipboard (Maximum size: 48.8 MB)