Primary targets need version conflict dependencies
Bug #1422442 reported by
Stig Telfer
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| anvil |
Fix Committed
|
Undecided
|
Unassigned | ||
Bug Description
Packages built using RPM specfile templates include RPM dependencies generated by transformation of the Python package requirements. However, they do not include RPM dependency conflicts, which could be used to express Python '!=' version constraints.
For example, the Cinder requirements.txt includes:
pbr>=0.6,!=0.7,<1.0
Anvil converts this into RPM dependencies:
python-pbr >= 0.6
python-pbr <= 1.0.0
But no conflicting versions are specified.
The result is that the requirements are too loosely specified for these packages.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to anvil (master) | #1 |
| Changed in anvil: | |
| status: | New → Fix Committed |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 7a6b074e278fc43
Author: Stig Telfer <email address hidden>
Date: Mon Feb 16 16:15:39 2015 +0000
Anvil not creating RPM 'Conflicts' terms in spec files
Use RPM 'Conflicts' dependencies to express Python version constraints in
which versions are excluded using '!=' syntax.
Change-Id: I2f7cc87e6c3ba4
Co-Authored-By: Sam Gasper <email address hidden>
Closes-bug: #1422442