From f0f930b12ee39c6e4623526471b83cacd40c1a40 Mon Sep 17 00:00:00 2001 From: Sean McGinnis Date: Wed, 25 Apr 2018 12:10:41 -0500 Subject: [PATCH] Add reno to test-requirements Reno was moved over to doc/requirements.txt when that was created because it is needed for releasenotes builds. But with its removal from the other requirements files, doing something like the recommended "tox -e venv -- reno new xxx" to create a new release note fails with reno missing from any venv's created since it was removed. This adds reno back in to test-requirements.txt so it is installed when creating the venv, ummm... venv. Change-Id: Id2e0325b0ce8e18bb9a65318fb3fc52777753536 --- lower-constraints.txt | 1 + test-requirements.txt | 1 + 2 files changed, 2 insertions(+) diff --git a/lower-constraints.txt b/lower-constraints.txt index 290d364b940..7a91ea44a1c 100644 --- a/lower-constraints.txt +++ b/lower-constraints.txt @@ -122,6 +122,7 @@ python-swiftclient==3.2.0 pytz==2013.6 pyudev==0.21.0 PyYAML==3.12 +reno==2.5.0 repoze.lru==0.7 requests==2.14.2 requestsexceptions==1.4.0 diff --git a/test-requirements.txt b/test-requirements.txt index 7993564b0c9..28ee878f0ac 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -19,3 +19,4 @@ testscenarios>=0.4 # Apache-2.0/BSD oslo.versionedobjects[fixtures]>=1.31.2 # Apache-2.0 tempest>=17.1.0 # Apache-2.0 bandit>=1.1.0 # Apache-2.0 +reno>=2.5.0 # Apache-2.0