From d03e347e7b69a1d34ce0f9418509e5dcebe18b4c Mon Sep 17 00:00:00 2001 From: Brian Waldon Date: Thu, 8 Dec 2011 13:11:11 -0500 Subject: [PATCH] Lock keystone to specific commit in pip-requires We'll use commit b9dde8d0e317203e349b8e4bca5bc9923c11974e. This will help ensure our tests don't fail due to a changing keystone trunk Change-Id: Ie9b8f0bd13b974817e8ce7de08033ab3f5bcce0c --- tools/pip-requires | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/tools/pip-requires b/tools/pip-requires index 693431d5c2..49a206eb4c 100644 --- a/tools/pip-requires +++ b/tools/pip-requires @@ -27,8 +27,11 @@ kombu pycrypto # The following allow Keystone to be installed in the venv -# along with all of Keystone's dependencies --e git://github.com/openstack/keystone.git#egg=keystone +# along with all of Keystone's dependencies. We target a specific +# commit hash so we can code to a constant version of keystone. +# Trying to hit a moving target causes our local unittests to fail +# when they should remain unaffected. +-e git://github.com/openstack/keystone.git@b9dde8d0e317203e349b8e4bca5bc9923c11974e#egg=keystone # Note you will need gcc buildtools installed and must # have installed libxml headers for lxml to be successfully