Bug #5342
closednightly: debian 11 / bullseye wrong package version
100%
Description
The nightly still shows 0.2.2-... while the current tag is 0.2.4.
The hashes matches the last commit on headd.
Related issues
Updated by laforge over 2 years ago
- Related to Bug #5341: nightly: debian 11 / bullseye have wrong dependencies added
Updated by osmith over 2 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 20
The tags 0.2.3 and 0.2.4 were not branched from master, these are backports of fixes to 0.2.2. Therefore debian/changelog on master is still on 0.2.2.
I see how this is confusing though... suddenly a package from latest has a higher version than one from nightly.
How should we fix this? I guess when submitting packages to gerrit, we could regenerate the debian/changelog with either 0.2.2 (use the latest tag in the tree) or 0.3.0 (bump the minor version, assuming that all backports only get a patch release in MAJOR.MINOR.PATCH).
Should we do that, leave it as-is or do something else?
Updated by pespin over 2 years ago
I'd leave it as it is. It may be confusing but anyway anyone using nightly should know what he's doing if mixing it with latest.
IIRC the version of the nightly it's anyway not only "0.2.2", but "0.2.2-XYZ", at least when doing program --version, meaning it's some commits after 0.2.2, and it really describes the fact that they may not be in the same branch as latest, etc.
Updated by osmith over 2 years ago
- Status changed from Feedback to Resolved
- % Done changed from 20 to 100
Agreed with Pau.
Meanwhile, a 1.0.0 has been tagged, so osmo-remsim nightly has a higher version than latest again.
