fc8be03bae
1. What is the problem? The older hacking library has a cap on pbr <2.0, which is causing issues with the recent 2.0.0 release of pbr 2. What is the solution for the problem? Hacking isn't kept in sync via the usual proposal bot updates so update it manually to fix the pep8 gate. 3. What the features need to be implemented to the Tricircle to realize the solution? None Partial-Bug: #1668848 Change-Id: I805565843c9228b729e242c3f2fddf14b6a3130e
23 lines
783 B
Plaintext
23 lines
783 B
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.
|
|
hacking>=0.12.0,!=0.13.0,<0.14 # Apache-2.0
|
|
|
|
coverage>=4.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
mock>=2.0 # BSD
|
|
python-subunit>=0.0.18 # Apache-2.0/BSD
|
|
requests-mock>=1.1 # Apache-2.0
|
|
docutils>=0.11 # OSI-Approved Open Source, Public Domain
|
|
sphinx>=1.5.1 # BSD
|
|
oslosphinx>=4.7.0 # Apache-2.0
|
|
testrepository>=0.0.18 # Apache-2.0/BSD
|
|
testtools>=1.4.0 # MIT
|
|
testresources>=0.2.4 # Apache-2.0/BSD
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
oslotest>=1.10.0 # Apache-2.0
|
|
os-testr>=0.8.0 # Apache-2.0
|
|
tempest-lib>=0.14.0 # Apache-2.0
|
|
ddt>=1.0.1 # MIT
|
|
reno>=1.8.0 # Apache-2.0
|