Project

General

Profile

Actions
Copy link

Bug #6173

closed

OBS scripts: package was built with previous release number

Added by osmith 8 months ago. Updated 8 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
osmith
Target version:
-
Start date:
09/12/2023
Due date:
% Done:

100%

Spec Reference:

Description

There seems to be a bug in the OBS scripts that can appear right after creating a new release. For some reason, the commit for "Bump version: 1.7.0.56-abf26-dirty → 1.8.0" of libosmo-sccp was built with 1.7.0 as number, instead of 1.8.0.

My theory without looking much into it:
  • the version number gets taken from the latest git tag, not from debian/changelog
  • in this case, the tag was not pushed yet (it's always getting pushed after merging the commit)
  • the OBS scripts added a debian/changelog entry based on the wrong version
Actions
Copy link
 #1

Updated by osmith 8 months ago

In the current CNI release this happened with one package, as workaround I force upgraded it:

./update_obs_project.py -f master -v -n osmocom:master libosmo-sccp

EDIT: happened to more than one package

Actions
Copy link
 #2

Updated by osmith 8 months ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by osmith 8 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 90
Actions
Copy link
 #4

Updated by osmith 8 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100
Actions
Copy link

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)