Version number generator chokes on .is. revert packages.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
CI Train [cu2d] |
Fix Released
|
Undecided
|
Robert Bruce Park |
Bug Description
Just saw this mess in a changelog:
unity-notifications (0.1.2+
unity-notifications (0.1.2+
unity-notifications (0.1.2+
unity-notifications (0.1.2+
unity-notifications (0.1.2+
Apparently somebody did a revert once and then several subsequent releases just kept building on that revert version number rather than generating a proper version. Saviq had to version bump to 0.1.3 to get around this. Definitely need to add both .is. and .~is. examples to the version generator test cases to ensure they're handled correctly.
Related branches
- PS Jenkins bot: Approve (continuous-integration)
- CU2D maintainers: Pending requested
-
Diff: 35 lines (+11/-2)2 files modifiedcupstream2distro/version.py (+3/-2)
tests/unit/test_version.py (+8/-0)
Changed in cupstream2distro: | |
status: | Fix Committed → Fix Released |
Fix committed into lp:cupstream2distro at revision 1152, scheduled for release in cupstream2distro, milestone Unknown