f50d906c7e
These are detected as errors since the clean up was done[1] in the requirements repository. [1] 314734e938f107cbd5ebcc7af4d9167c11347406 Also remove the note about old pip's behavior because the resolver in recent pip no longer requires specific order. Change-Id: Ia761dcbc62648438f7fd5062b9b4b8acc71ee3ad
29 lines
1.0 KiB
Plaintext
29 lines
1.0 KiB
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.
|
|
|
|
pbr>=4.0.0 # Apache-2.0
|
|
|
|
Jinja2>=2.10 # BSD License (3 clause)
|
|
netaddr>=0.7.18 # BSD
|
|
SQLAlchemy>=1.3.0 # MIT
|
|
alembic>=1.6.5 # MIT
|
|
neutron-lib>=2.6.0 # Apache-2.0
|
|
oslo.concurrency>=3.26.0 # Apache-2.0
|
|
oslo.config>=8.0.0 # Apache-2.0
|
|
oslo.db>=4.44.0 # Apache-2.0
|
|
oslo.log>=4.5.0 # Apache-2.0
|
|
oslo.messaging>=7.0.0 # Apache-2.0
|
|
oslo.reports>=1.18.0 # Apache-2.0
|
|
oslo.serialization>=2.25.0 # Apache-2.0
|
|
oslo.service>=1.31.0 # Apache-2.0
|
|
oslo.utils>=4.5.0 # Apache-2.0
|
|
|
|
neutron>=17.0.0 # Apache-2.0
|
|
|
|
# The comment below indicates this project repo is current with neutron-lib
|
|
# and should receive neutron-lib consumption patches as they are released
|
|
# in neutron-lib. It also implies the project will stay current with TC
|
|
# and infra initiatives ensuring consumption patches can land.
|
|
# neutron-lib-current
|