Cap hacking version to <2

Hacking received a major update to version 2.0.0 that added new checks
that fail on stable branches. Instead of addressing those new check
errors on stable branches, it is better to cap hacking to <2. This way
we'll not see lint errors again should new checks be added in the
future.

Support for hacking 2.0.0 in master branch is being worked in
https://review.opendev.org/#/c/699302/

Since this patch touches requirements file, the requirements-check CI
job also runs and does not find matching gunicorn and sphinx
requirements. This patch fixes that too.

Change-Id: I4706972095d42815a3f3cec0bc5aa82a34922bf3
This commit is contained in:
Carlos Goncalves 2020-01-10 14:35:52 +01:00
parent d603c817f4
commit 85f7abbbaf
2 changed files with 4 additions and 3 deletions

View File

@ -57,5 +57,6 @@ netifaces>=0.10.4 # MIT
ipaddress>=1.0.17;python_version<'3.3' # PSF
cryptography>=2.1 # BSD/Apache-2.0
pyroute2>=0.4.21;sys_platform!='win32' # Apache-2.0 (+ dual licensed GPL2)
gunicorn>=19.9.0 # MIT
gunicorn>=19.9.0,<20.0.0;python_version<'3.0' # MIT
gunicorn>=19.9.0;python_version>='3.0' # MIT
Werkzeug>=0.14.1 # BSD License

View File

@ -1,7 +1,7 @@
# 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>=1.1.0 # Apache-2.0
hacking>=1.1.0,<2 # Apache-2.0
requests-mock>=1.2.0 # Apache-2.0
coverage!=4.4,>=4.0 # Apache-2.0
fixtures>=3.0.0 # Apache-2.0/BSD
@ -20,4 +20,4 @@ bandit>=1.1.0 # Apache-2.0
tempest>=17.1.0 # Apache-2.0
# Required for pep8 - doc8 tests
sphinx!=1.6.6,!=1.6.7,>=1.6.2,<2.0.0;python_version=='2.7' # BSD
sphinx!=1.6.6,!=1.6.7,>=1.6.2;python_version>='3.4' # BSD
sphinx!=1.6.6,!=1.6.7,!=2.1.0,>=1.6.2;python_version>='3.4' # BSD