Pin keystonemiddleware max version
To resolve requirements conflicts in most painless way before 6.1 GA let's ping keystonemiddleware to max version 2.0.0 and in 7.0 we can remove upper bounds as well update packages in our mirros. Change-Id: I98055060480a2ef80b9d56a211812e98e27fa2e1 Closes-Bug: #1466733
This commit is contained in:
parent
6fec8de17f
commit
1ca432833e
|
@ -31,7 +31,7 @@ urllib3>=1.7
|
|||
web.py==0.37
|
||||
wsgilog==0.3
|
||||
wsgiref==0.1.2
|
||||
keystonemiddleware>=1.2.0
|
||||
keystonemiddleware>=1.2.0,<2.0.0
|
||||
# we might still need keystone command
|
||||
python-keystoneclient>=0.11,<=1.4.0
|
||||
python-novaclient>=2.17.0,<=2.24.1
|
||||
|
|
Loading…
Reference in New Issue