Project

General

Profile

Bug #2639

Debian nightly packages don't have versions from git-version-gen

Added by laforge 10 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
11/15/2017
Due date:
% Done:

100%

Estimated time:
Spec Reference:

Description

It would be useful if the debian nightly package versions have the version information that we generate from our git-version-gen scripts, like "0.7.0.9-2564"

This way, the package version directly reflects a specific commit in a specific repository and it is uniquely identified what is contained in the package.

Also, it will be clear that it's not in fact a plain 0.7.0, but a 0.7.0 with some additions (9 commits)

History

#1 Updated by laforge 10 months ago

#2 Updated by laforge 5 months ago

  • Priority changed from Normal to High

#3 Updated by lynxis 5 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 30

OBS is building atm new packages. I'll check the version of the package and the binaries as soon they're built.
https://build.opensuse.org/project/show/home:lynxis:osmocom

#4 Updated by lynxis 5 months ago

  • Status changed from In Progress to Stalled
  • % Done changed from 30 to 90

https://gerrit.osmocom.org/7976

    osmocom-nightly-packages: replace version string with by git-version-gen

    E.g. old version 0.10.2.20180501 (0.10.2 last deb version,
    20180501 was the date)

    The new version will look like 0.10.2.279.178b
     - 0.10.2 is the last tag
     - .279 is 279 commits since the tag
     - 178b is the actual short git rev

    The direct output of ./git-version-gen couldn't be used because
    debian forbids using a minus (-) in upstream versions.

#5 Updated by lynxis 5 months ago

  • Status changed from Stalled to Resolved
  • % Done changed from 90 to 100

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)