From e373d9ea1311c2c071bc735637f25649b2c199ac Mon Sep 17 00:00:00 2001
From: Frode Nordahl <frode.nordahl@canonical.com>
Date: Tue, 29 May 2018 18:27:18 +0200
Subject: [PATCH] Freeze cmd2 library temporarilly

In need of landing changes before release and the upstream gate is
wedged at the moment.

Root of the issue is a release blunder by a upstream dependency:
https://github.com/python-cmd2/cmd2/issues/421

Upstream has made the same change to global requirements here:
https://review.openstack.org/#/c/570811

We can remove this again as soon as changes propagate out to all
dependencies.

Change-Id: Ib002d4534150c9c2aba025decfd0faef77f71297
---
 test-requirements.txt | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/test-requirements.txt b/test-requirements.txt
index 9edd4bbf..24a53ac1 100644
--- a/test-requirements.txt
+++ b/test-requirements.txt
@@ -7,6 +7,8 @@ flake8>=2.2.4,<=2.4.1
 os-testr>=0.4.1
 charm-tools>=2.0.0
 requests==2.6.0
+cmd2!=0.8.3,<0.9.0;python_version<'3.0'  # MIT
+cmd2!=0.8.3;python_version>='3.0'  # MIT
 # BEGIN: Amulet OpenStack Charm Helper Requirements
 # Liberty client lower constraints
 amulet>=1.14.3,<2.0