Version of update packages for 6.0 is not updated automatically with new commits

Bug #1479080 reported by Eugene Nikanorov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Alexander Nevenchannyy
5.1.x
Invalid
High
Alexander Nevenchannyy

Bug Description

This results in confusion in versions and contents.
Customers will not be able to install newer update packages in a regular way.

The problem is apparently in a build system that should automatically account for changes and bump the versions.

Changed in fuel:
importance: Undecided → High
assignee: nobody → Alexander Nevenchannyy (anevenchannyy)
milestone: none → 5.1.1-mu-2
milestone: 5.1.1-mu-2 → 6.0-mu-5
status: New → Confirmed
Revision history for this message
Alexander Tsamutali (astsmtl) wrote :

This is not true. Package version contains number of commits counted as `git rev-list --no-merges HEAD | wc -l'. You can check it for ex. here: http://osci-jenkins.srt.mirantis.net/view/5.x-updates,%206.0-updates/job/f-i-build-fuel-deb-updates/9/console

+ osc -A https://osci-obs.vm.mirantis.net:444 addremove
A fuel-library6.0_6.0.0-6205.1.dsc
D fuel-library6.0_6.0.0-6204.1.dsc
D fuel-library6.0_6.0.0-6204.1.debian.tar.gz
A fuel-library6.0_6.0.0-6205.1.debian.tar.gz

Changed in fuel:
status: Confirmed → Invalid
Changed in fuel:
milestone: 6.0-mu-5 → 6.0-updates
Changed in fuel:
milestone: 6.0-updates → 6.0.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.