Reviewed: https://review.openstack.org/24645 Committed: http://github.com/openstack/quantum/commit/4e290b713d58f52151db6632bd1ae82c8d26b607 Submitter: Jenkins Branch: milestone-proposed
commit 4e290b713d58f52151db6632bd1ae82c8d26b607 Author: Dirk Mueller <[email protected]> Date: Tue Mar 12 23:08:27 2013 +0100 Pin SQLAlchemy to 0.7.x 0.7.10 has been released and is compatible with 0.7.x. Instead of pinning to 0.7.9, simply pin to 0.7.x to avoid SQLAlchemy 0.8 Unfortuantely '<0.8' matches '0.8.0b2', which is what we don't want. Therefore pinning it to '<=0.7.99' instead. This matches a corresponding change in openstack/requirements Fixes: Bug #1153983 Change-Id: Icf680a933c6092cce52706fd9616a0d208164d1e (cherry picked from commit 2f2aaf2a89445590e01a7c288de9f5c93b20e87f) ** Changed in: quantum Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to quantum. https://bugs.launchpad.net/bugs/1153983 Title: Consolidate SQLAlchemy requirements to 0.7.x Status in OpenStack Image Registry and Delivery Service (Glance): Triaged Status in Orchestration API (Heat): Fix Committed Status in OpenStack Quantum (virtual network service): Fix Released Bug description: SQLAlchemy 0.7.10 has been released and is compatible with 0.7.9. It seems desireable to relax the requirement in Heat to accept any 0.7.x version. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1153983/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
