Version number generator chokes on .is. revert packages.

Bug #1506417 reported by Robert Bruce Park
6
This bug affects 1 person
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+15.10.20150623.is.0.1.2+15.10.20151015-0ubuntu1) wily; urgency=medium
unity-notifications (0.1.2+15.10.20150623.is.0.1.2+15.10.20150804-0ubuntu1) wily; urgency=medium
unity-notifications (0.1.2+15.10.20150623.is.0.1.2+15.10.20150706.1-0ubuntu2~gcc5.1) wily; urgency=medium
unity-notifications (0.1.2+15.10.20150623.is.0.1.2+15.10.20150706.1-0ubuntu1) wily; urgency=medium
unity-notifications (0.1.2+15.10.20150623-0ubuntu1) wily; urgency=medium

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

Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:cupstream2distro at revision 1152, scheduled for release in cupstream2distro, milestone Unknown

Changed in cupstream2distro:
status: Triaged → Fix Committed
Changed in cupstream2distro:
status: Fix Committed → Fix Released
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.