Versionbump script needs to deal with setup.cfg version stamp
Bug #1358455 reported by
John Wood
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Barbican |
Fix Released
|
High
|
John Wood | ||
Bug Description
The versionbump script used to supply a monotonically increasing version for rpm packages was modified to supply a 'version=' attribute to setup.cfg, to override the pbr-generated version. Unfortunately, this change breaks devstack deployments. So the version attribute was added back to setup.cfg. Now versionbump functionality needs to be reverted back to adding the timestamp to the hard-coded version stamp, but with the more Pythonic mods suggested in the previous CR.
| Changed in barbican: | |
| assignee: | nobody → John Wood (john-wood-w) |
| Changed in barbican: | |
| milestone: | none → juno-3 |
| importance: | Undecided → High |
| status: | New → Confirmed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to barbican (master) | #1 |
| Changed in barbican: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to barbican (master) | #2 |
| Changed in barbican: | |
| status: | In Progress → Fix Committed |
| Changed in barbican: | |
| status: | Fix Committed → Fix Released |
| Changed in barbican: | |
| milestone: | juno-3 → 2014.2 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/