Bug 857852 - missing dependency on qpid-cpp-server-daemon
Summary: missing dependency on qpid-cpp-server-daemon
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openstack-utils
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pádraig Brady
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-17 09:10 UTC by Jan van Eldik
Modified: 2012-12-20 16:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-20 16:17:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan van Eldik 2012-09-17 09:10:49 UTC
Description of problem:

The /usr/bin/openstack-demo-install tries to start the qpid service,
which is now provided by RPM qpid-cpp-server-daemon

Version-Release number of selected component (if applicable):

openstack-utils-2012.1-2.fc17.noarch

How reproducible:

100%

Steps to Reproduce:
1. run /usr/bin/openstack-demo-install

Comment 1 Fedora Update System 2012-10-10 14:42:55 UTC
openstack-utils-2012.2-5.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/openstack-utils-2012.2-5.fc18

Comment 2 Fedora Update System 2012-10-10 18:07:23 UTC
Package openstack-utils-2012.2-5.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing openstack-utils-2012.2-5.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-15805/openstack-utils-2012.2-5.fc18
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2012-12-20 16:17:54 UTC
openstack-utils-2012.2-5.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.