Hello Justin, or anyone else affected,
Accepted keystone into quantal-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/keystone/2012.2.1-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package keystone -
2013.1~g1~20121101.2629-0ubuntu1
---
keystone (2013.1~g1~20121101.2629-0ubuntu1) raring; urgency=low
* New upstream release.
* debian/tests/test_overrides.conf: Update for Grizzly test suite.
* debian/control: Drop python-nova.
--
Hi Justin, thanks for the bug. It looks like the dependency between
keystone and python-keystone is explicit in that it requires the same
version, so those should be upgraded together. The python-
keystoneclient dependency is loosely defined, for sure. Can you confirm
that this is the case?
** Branch linked: lp:~openstack-ubuntu-testing/keystone/raring-grizzly-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1073273
Title:
keystone package has incorrect dep
** Branch linked: lp:~openstack-ubuntu-testing/keystone/quantal-folsom-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1073273
Title:
keystone package has incorrect dep
** Branch linked: lp:~ubuntu-branches/ubuntu/raring/keystone/raring-
proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1073273
Title:
keystone package has incorrect dep on
I have been using the folsom-trunk-testing PPA as I thought those
packages would eventually make their way into the Ubuntu Cloud archive.
And yes.. it seems that the keystone, python-keystone, python-
keystoneclient packages all have to be upgraded together as a unit.
--
You received this bug
