Fix requirement version pinning

We previously used the compatible release operator ~=.
This operator is not well understood by pybuild, making the packaging
fail.

We now resort to version bounding with <= and >.

Change-Id: Ibf09d202559a15dbe775ebe9f06bade3e280824e
This commit is contained in:
Vincent Llorens 2016-09-28 17:28:45 +02:00
parent d72333562b
commit 7090f679f0

View File

@ -2,12 +2,12 @@
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
pbr~=1.8
pbr>=1.8,<1.9
oslo.config~=2.4
oslo.messaging~=2.5
oslo.serialization~=1.9
oslo.versionedobjects~=0.10
oslo.config>=2.4,<2.5
oslo.messaging>=2.5,<2.6
oslo.serialization>=1.9,<1.10
oslo.versionedobjects>=0.10,<0.11
requests>=2.0.0,<3.0.0 # availability: 2.10.0 on CentOS 7, 2.7.0 on Ubuntu 14.04
sqlalchemy~=1.0
synergy-service~=1.0.1
sqlalchemy>=1.0,<1.1
synergy-service>=1.1,<1.2