Fix requiremt check job
The old excludes are no longer accepted. Bump the min to the minimum known good version. Also remove the note about old pip's behavior. Change-Id: I51088a668229570f423aca5f8f538036f840e123
This commit is contained in:
parent
d74365969e
commit
28180a633b
@ -1,7 +1,3 @@
|
|||||||
# 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.
|
|
||||||
|
|
||||||
sphinx>=2.0.0,!=2.1.0 # BSD
|
sphinx>=2.0.0,!=2.1.0 # BSD
|
||||||
sphinxcontrib-httpdomain>=1.3.0 # BSD
|
sphinxcontrib-httpdomain>=1.3.0 # BSD
|
||||||
sphinxcontrib-pecanwsme>=0.10.0 # Apache-2.0
|
sphinxcontrib-pecanwsme>=0.10.0 # Apache-2.0
|
||||||
|
@ -1,6 +1,6 @@
|
|||||||
# The order of packages is significant, because pip processes them in the order
|
# Requirements lower bounds listed here are our best effort to keep them up to
|
||||||
# of appearance. Changing the order has an impact on the overall integration
|
# date but we do not test them so no guarantee of having them all correct. If
|
||||||
# process, which may cause wedges in the gate later.
|
# you find any incorrect lower bounds, let us know or propose a fix.
|
||||||
|
|
||||||
pbr>=0.11,!=2.1.0 # Apache-2.0
|
pbr>=0.11,!=2.1.0 # Apache-2.0
|
||||||
pecan>=1.0.0,!=1.0.2,!=1.0.3,!=1.0.4,!=1.2 # BSD
|
pecan>=1.0.0,!=1.0.2,!=1.0.3,!=1.0.4,!=1.2 # BSD
|
||||||
@ -19,7 +19,7 @@ oslo.upgradecheck>=0.1.0 # Apache-2.0
|
|||||||
oslo.utils>=4.5.0 # Apache-2.0
|
oslo.utils>=4.5.0 # Apache-2.0
|
||||||
oslo.versionedobjects>=1.31.2 # Apache-2.0
|
oslo.versionedobjects>=1.31.2 # Apache-2.0
|
||||||
oslo.policy>=3.7.0 # Apache-2.0
|
oslo.policy>=3.7.0 # Apache-2.0
|
||||||
SQLAlchemy>=0.9.0,!=1.1.5,!=1.1.6,!=1.1.7,!=1.1.8 # MIT
|
SQLAlchemy>=1.1.9 # MIT
|
||||||
alembic>=0.8.10 # MIT
|
alembic>=0.8.10 # MIT
|
||||||
stevedore>=1.5.0 # Apache-2.0
|
stevedore>=1.5.0 # Apache-2.0
|
||||||
keystonemiddleware>=4.17.0 # Apache-2.0
|
keystonemiddleware>=4.17.0 # Apache-2.0
|
||||||
|
@ -1,7 +1,3 @@
|
|||||||
# 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.
|
|
||||||
|
|
||||||
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
||||||
|
|
||||||
bandit>=1.6.0 # Apache-2.0
|
bandit>=1.6.0 # Apache-2.0
|
||||||
|
Loading…
Reference in New Issue
Block a user