Open larsbutler opened 9 years ago
We should be compatible with upstream python-swiftclient. Thus I don't quite understand why we carry it in our repo.
The issue is just with the devstack dev environment. For everything else, it's fine.
I'm working on a workaround, to avoid installing the incompatible version of oslo.config with devstack.
The reason why we have oslo in our PPA is so that we have a zpm
package. The deps are: zpm -> python-swiftclient -> python-keystoneclient -> python-oslo.config.
So it's just kind of irritating to not be able to the use the latest packages in Trusty (Utopic is a different story) with DevStack.
Hmm, probably backporting the package is not the right solution.
There's a problem running ZeroCloud in DevStack using the
contrib/vagrant
scripts.Our package archive has
oslo.config
1.2.1. ZeroCloud requirespython-swiftclient
, and the package we have forpython-swiftclient
is pinned to this version ofoslo.config
. Basically, we needoslo.config>=1.4
, otherwise we get crashes like this in DevStack:The other alternative would be to pin the DevStack versions for the vagrant dev environment to a compatible revision. This could be tricky.