71a6aa21c6
Because of a conflict between how the oslo.upgradecheck library uses oslo config and how we want to use it in placement, two different ConfigOpts were needed to avoid an args already parsed error. The new release of the oslo.upgradecheck library is change to allow the two steps in main (registering the CLI opts and running the command) to be called separately if desired. Doing so allows us to use just one ConfigOpts. Requirements and constraints are updated. Change-Id: I792df18cb17da95659628bfe7f7a69897c6f37ab
29 lines
1.1 KiB
Plaintext
29 lines
1.1 KiB
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
pbr!=2.1.0,>=2.0.0 # Apache-2.0
|
|
SQLAlchemy!=1.1.5,!=1.1.6,!=1.1.7,!=1.1.8,>=1.0.10 # MIT
|
|
keystonemiddleware>=4.18.0 # Apache-2.0
|
|
Routes>=2.3.1 # MIT
|
|
WebOb>=1.8.2 # MIT
|
|
jsonschema<3.0.0,>=2.6.0 # MIT
|
|
requests>=2.14.2 # Apache-2.0
|
|
six>=1.10.0 # MIT
|
|
setuptools!=24.0.0,!=34.0.0,!=34.0.1,!=34.0.2,!=34.0.3,!=34.1.0,!=34.1.1,!=34.2.0,!=34.3.0,!=34.3.1,!=34.3.2,!=36.2.0,>=21.0.0 # PSF/ZPL
|
|
oslo.concurrency>=3.26.0 # Apache-2.0
|
|
oslo.config>=6.7.0 # Apache-2.0
|
|
oslo.context>=2.19.2 # Apache-2.0
|
|
oslo.log>=3.36.0 # Apache-2.0
|
|
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
|
|
oslo.utils>=3.37.0 # Apache-2.0
|
|
oslo.db>=4.40.0 # Apache-2.0
|
|
oslo.policy>=1.35.0 # Apache-2.0
|
|
oslo.i18n>=3.15.3 # Apache-2.0
|
|
oslo.middleware>=3.31.0 # Apache-2.0
|
|
oslo.upgradecheck>=0.2.0 # Apache-2.0
|
|
oslo.versionedobjects>=1.31.2 # Apache-2.0
|
|
os-resource-classes>=0.2.0 # Apache-2.0
|
|
os-traits>=0.4.0 # Apache-2.0
|
|
microversion-parse>=0.2.1 # Apache-2.0
|