Osmocom nightly packages

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Martin Hauke mardnh at gmx.de
Fri Mar 3 20:13:58 UTC 2017


Hi,

i'm building osmocom-related packages for openSUSE since a few years on OBS.
https://build.opensuse.org/project/show/home:mnhauke:osmocom
https://build.opensuse.org/project/show/home:mnhauke:osmocom-iuh

Now i'd like to add support for RPM-based distributions to the
osmocom-nightly packages.
My current plan is to first add support for (open)SUSE based
distributions and if there's interest then find out all the subtle
changes that are needed for the spec-file to also add support for
Redhat/Fedora/CentOS.

# Phase1
- openSUSE_Leap_42.2 (x86_64)
- openSUSE_Tumbleweed (i586, x86_64)
- openSUSE_Factory_ARM (armv7l, aarch64)
- SLE_12_SP2 (x86_64)

# Phase2
- CentOS_7 (x86_64)
- Fedora_25 (i586, x86_64)
- RHEL_7 (x86_64)

How does the current workflow for the daily check-in of the nightly
debian/ubuntu packages look like?

There's probably a bunch of scripts that do
- git checkout from all relevant repositories
- update changelog based on git commit messages
- change the package version
- create the new tarball
- maybe osc local build
- upload the tarball and the dsc to OBS
- monitor if all the OBS-packages are successfully built and in state
published

Thanks in advance,
Martin




More information about the OpenBSC mailing list