Project

General

Profile

Bug #3449

network:osmocom:nightly packages have VERSION="UNKNOWN"

Added by laforge about 2 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Target version:
-
Start date:
08/06/2018
Due date:
% Done:

100%

Estimated time:
Spec Reference:

Description

It seems that the way the nightly packages are generated doesn't involve "make dist" and hence no ".tarball-version" file is part of the archive, which in turn menas that the pkg-config .pc files contain "UNKNOWN" as version string.

This is what currently happens to osmo-hlr (libosmo-gsup-client) and is why osmo-msc can not be built after migrating over to using libosmo-gsup-client.


Related issues

Related to Cellular Network Infrastructure - Feature #3555: debian-repo-install-test: check if binaries report UNKNOWN as version stringResolved2018-09-14

Related to Cellular Network Infrastructure - Bug #3551: A few projects still set up .tarball-version incorrectly in debian/rulesResolved2018-09-13

History

#1 Updated by laforge about 2 months ago

  • % Done changed from 0 to 40

#2 Updated by laforge about 2 months ago

  • Status changed from New to In Progress
  • Priority changed from Immediate to Urgent
  • % Done changed from 40 to 80

patch merged, new nightly build running

#3 Updated by laforge about 2 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100

patch merged, osmo-msc nightly OBS builds "green" again.

#4 Updated by osmith 9 days ago

  • Related to Feature #3555: debian-repo-install-test: check if binaries report UNKNOWN as version string added

#5 Updated by pespin 6 days ago

  • Related to Bug #3551: A few projects still set up .tarball-version incorrectly in debian/rules added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)