Bug #6446
closedDrop rpms (.spec.in) from Osmocom repositories
100%
Description
I wrote a mailing list post a week ago, explaining that we are thinking about dropping rpms completely from the Osmocom OBS, and removing the spec files from the git repositories: https://lists.osmocom.org/hyperkitty/list/openbsc@lists.osmocom.org/thread/UT6C5CHM2DSZL6CO2USWTTM6MEYLU2HW/
There was no feedback on the mailing list, but I've discussed this with roox at OsmoDevCon. He is maintaining separate spec files in the OpenSUSE OBS, for both latest and nightly.
We concluded that it makes sense to just drop the redundant rpms from the Osmocom OBS, as well as redundant .spec.in files from the Osmocom git repositories then, and to point people who would like to have Osmocom binary packages for openSUSE to the repositories that roox maintains.
So I would post the following news announcement and then start removing the rpms and spec files.
laforge: does this look good, do you want me to proceed with it like this?
Removal of official RPM packages¶
As announced previously, the rpm binary packages for CentOS 8 / AlmaLinux 8 are unmaintained.
There were also binary packages for openSUSE Tumbleweed in the Osmocom OBS, but these had no further testing besides making sure that they build.
sysmocom was still ensuring that the rpm binary packages build from the rpm spec files in our own git repositories. But this
is also significant effort that we would rather spend elsewhere, and so we decided to stop providing rpm builds altogether
and that we will remove the spec files from the git repositories.
Checklist
- get ack on announcement
- post the announcement
- remove rpm packages from Osmocom OBS
- remove .spec.in files from all Osmocom repositories
- update the wiki
Updated by laforge 12 days ago
- Assignee changed from laforge to osmith
osmith wrote:
There was no feedback on the mailing list, but I've discussed this with roox at OsmoDevCon. He is maintaining separate spec files in the OpenSUSE OBS, for both latest and nightly.
We concluded that it makes sense to just drop the redundant rpms from the Osmocom OBS, as well as redundant .spec.in files from the Osmocom git repositories then, and to point people who would like to have Osmocom binary packages for openSUSE to the repositories that roox maintains.
[...]
laforge: does this look good, do you want me to proceed with it like this?
I would of course have always preferred if roox (or somebody else) would maintain the spec files upstream (i.e. in the osmocom git repos) rather than having that somewhere else. But of course, those who do the work get to say how it is done.
The announcement looks clear to me, except
A separate set of rpm binary packages and spec files are maintained by Martin Hauke in the openSUSE OBS instance:
it should probably be clarified what is the difference between those two feeds.
Updated by osmith 11 days ago
- Checklist item get ack on announcement set to Done
- Checklist item post the announcement set to Done
- % Done changed from 10 to 20
laforge wrote in #note-1:
The announcement looks clear to me, except
A separate set of rpm binary packages and spec files are maintained by Martin Hauke in the openSUSE OBS instance:it should probably be clarified what is the difference between those two feeds.
Ack, I've added a clarification after the bullet points and posted it:
https://osmocom.org/news/255
Updated by osmith 11 days ago
- % Done changed from 40 to 90
I realized that we still need to build osmo-pcap and its dependency libosmocore for centos7 due to SYS#6760. So in order to make sure that these will continue to build fine (and we don't remove the spec files by accident), I've added them to CI with: https://gerrit.osmocom.org/c/osmo-ci/+/36718
For other git repositories, I've pushed patches to gerrit to remove the spec files:
https://gerrit.osmocom.org/q/topic:rpm-removal
