Project

General

Profile

Feature #4145

osmo-release.sh: Add check to make sure dependency requirements in configure.ac and debian/control match

Added by pespin 4 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
08/07/2019
Due date:
% Done:

100%

Spec Reference:

Description

So today while issuing a release for most osmocom CNI stuff, I ended up finding that while I was updating configure requirements by manually attempting builds (eg. PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore >= 1.2.0)), I forgot to update similar lines in debian/control(eg. libosmocore-dev (>= 1.2.0),).

That's bad. Let's add some checks to make sure that changes in configure.ac are matched in debian/control.

It should be enough for osmocom libraries, not needed for all dependencies.

Also make sure all osmocom dependencies under debian/control of all projects have dependency requirements set (the >= x.y.z part set).

History

#1 Updated by pespin 4 months ago

What's described in the original ticket is implemented here: https://gerrit.osmocom.org/c/libosmocore/+/15110

Another feature is needed: Make sure that $GIT_DIR/$project/debian/patches/build-for-debian8.patch can be applied (if file exists). If applying patch fails, abort release.

#2 Updated by pespin 4 months ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

patch applying verification merged: https://gerrit.osmocom.org/c/libosmocore/+/15117

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)