As discussed in TC PTG[1] and TC resolution[2], we are dropping the lower-constraints.txt file and its testing. We will keep lower bounds in the requirements.txt file but with a note that these are not tested lower bounds and we try our best to keep them updated. This patch also fixes a broken test by updating the maximum payload size to match the current maximum in Barbican. [3] This patch also skips an additional broken test. It will be fixed in a separate patch. [1] https://etherpad.opendev.org/p/tc-zed-ptg#L326 [2] https://governance.openstack.org/tc/resolutions/20220414-drop-lower-constraints.html#proposal [3] https://opendev.org/openstack/barbican/src/branch/stable/yoga/barbican/common/config.py#L33 Change-Id: Id192b8eef2c2518b8a89f200727bd03c47dbd07e
16 lines
697 B
Plaintext
16 lines
697 B
Plaintext
# Requirements lower bounds listed here are our best effort to keep them up to
|
|
# date but we do not test them so no guarantee of having them all correct. If
|
|
# you find any incorrect lower bounds, let us know or propose a fix.
|
|
|
|
# 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
|
|
requests>=2.14.2 # Apache-2.0
|
|
six>=1.10.0 # MIT
|
|
cliff!=2.9.0,>=2.8.0 # Apache-2.0
|
|
keystoneauth1>=3.4.0 # Apache-2.0
|
|
oslo.i18n>=3.15.3 # Apache-2.0
|
|
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
|
|
oslo.utils>=3.33.0 # Apache-2.0
|