Description of problem: it doesnt want to install! [root@notebook ~]# yum install qpid-cpp-server Loaded plugins: fastestmirror, langpacks, presto, protectbase, refresh-packagekit Loading mirror speeds from cached hostfile * fedora: mirror.its.dal.ca * rpmfusion-free: mirror.us.leaseweb.net * rpmfusion-free-updates: mirror.us.leaseweb.net * rpmfusion-nonfree: mirror.us.leaseweb.net * rpmfusion-nonfree-updates: mirror.us.leaseweb.net * updates: mirror.us.as6453.net 0 packages excluded due to repository protections Resolving Dependencies --> Running transaction check ---> Package qpid-cpp-server.x86_64 0:0.16-1.fc17.2 will be installed --> Restarting Dependency Resolution with new changes. --> Running transaction check ---> Package qpid-cpp-server.x86_64 0:0.16-1.fc17.2 will be installed --> Finished Dependency Resolution [root@notebook ~]# Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I believe this may be a bug in the spec file. The "Obsoletes" line below seems to cause this package to instantly obsolete itself. -------------- lines 177-179 from qpid-cpp.spec --------------- %package -n qpid-cpp-server Summary: An AMQP message broker daemon Obsoletes: qpid-cpp-server <= %{version}-%{release}
For the record, rpmlint detect this error : qpid-cpp-server.x86_64: W: self-obsoletion qpid-cpp-server <= 0.16-1.fc17.2 obsoletes qpid-cpp-server = 0.16-1.fc17.2 I guess that's just a typo, since the goal was to obsolete qpid-cpp-server-devel according to the changelog
well this package is a dependency of openstack essex and it is stopping the installation of it on any fedora 17 system.
FWIW, we are getting around this in F17 temporarily by downloading the package from a mirror and installing it manually: $ sudo yum install qpid-cpp-client qpid-cpp-server # gets all dependencies $ wget http://path/to/package/on/a/mirror $ sudo rpm -i qpid-cpp-server-0.16-1.fc17.2.x86_64.rpm
As of 2012-06-20, there is a new qpid-cpp-0.16-1.fc17.5 pushed to F17 that fixes this issue. Please give that a try.
Closing this since the fix was promoted to stable.
*** Bug 860330 has been marked as a duplicate of this bug. ***
qpid-cpp-0.18-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/qpid-cpp-0.18-2.fc17
qpid-cpp-0.18-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/qpid-cpp-0.18-2.fc18
Package qpid-cpp-0.18-2.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 qpid-cpp-0.18-2.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14840/qpid-cpp-0.18-2.fc18 then log in and leave karma (feedback).
qpid-cpp-0.18-3.1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/qpid-cpp-0.18-3.1.fc18
qpid-cpp-0.18-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/qpid-cpp-0.18-4.fc18
qpid-cpp-0.18-5.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/qpid-cpp-0.18-5.fc18