keystone package has incorrect dep on python-keystone (= 2012.1-0ubuntu1)

Bug #1073273 reported by Justin Shepherd
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
keystone (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS"

Using the following package repo:

# cat /etc/apt/sources.list.d/folsom-source.list
deb http://ppa.launchpad.net/openstack-ubuntu-testing/folsom-trunk-testing/ubuntu precise main

 dpkg -l keystone
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-============================================-============================================-========================================================================================================
ii keystone 2012.2+git201209252030~precise-0ubuntu1 OpenStack identity service - Daemons

 apt-cache show keystone | grep -i depends
Depends: python, debconf (>= 0.5) | debconf-2.0, upstart-job, python-keystone (= 2012.2+git201209252030~precise-0ubuntu1), adduser, ssl-cert (>= 1.0.12), dbconfig-common
Depends: python, debconf (>= 0.5) | debconf-2.0, upstart-job, python-keystone (= 2012.1+stable~20120824-a16a0ab9-0ubuntu2.2), adduser, ssl-cert (>= 1.0.12), dbconfig-common
Depends: python, debconf (>= 0.5) | debconf-2.0, upstart-job, python-keystone (= 2012.1-0ubuntu1), adduser, ssl-cert (>= 1.0.12), dbconfig-common

This will allow an upgrade to the keystone package with the incorrect python-keystone and python-keystoneclient packages

Related branches

Revision history for this message
Adam Gandelman (gandelman-a) wrote :

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?

Also, please note that the folsom-trunk-testing PPA will be deprecated and eventually renamed folsom-stable-testing as we open the PPAs and build jobs for Grizzly. I'd advise using the Ubuntu Cloud archive for your testing at this point. http://www.ubuntu.com/download/help/cloud-archive-instructions

Revision history for this message
Justin Shepherd (jshepher) wrote :

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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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.
 -- Adam Gandelman <email address hidden> Fri, 02 Nov 2012 13:48:49 +0100

Changed in keystone (Ubuntu):
status: New → Fix Released
Revision history for this message
Clint Byrum (clint-fewbar) wrote : Please test proposed package

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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.