Bug 860330

Summary: qpid-cpp-server obsoletes itself, again
Product: [Fedora] Fedora Reporter: Michael Hrivnak <mhrivnak>
Component: qpid-cppAssignee: Darryl L. Pierce <dpierce>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: dpierce, jose.p.oliveira.oss, nsantos, tross
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-26 11:19:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael Hrivnak 2012-09-25 15:51:13 UTC
Description of problem:

 qpid-cpp-0.18-1.1.fc17 will not be installed by yum because it obsoletes itself.

How reproducible:
 $ yum update
  
Actual results:
I see that yum wants to upgrade qpid-cpp-client, qpid-tools, and qpid-qmf from 0.16 to 0.18, but not qpid-cpp-server

Expected results:
I expect qpid-cpp-server to also be upgraded

Additional info:

The spec file is wrong. Excerpt from qpid-cpp.spec:

 184 %package -n qpid-cpp-server
 185 Summary:   An AMQP message broker daemon
 186 Obsoletes: qpid-cpp-server-devel <= %{version}-%{release}
 187 Obsoletes: qpid-cpp-server-daemon <= %{version}-%{release}
 188 Provides:  qpid-cpp-server-daemon = %{version}-%{release}

Line 187 should have "<", not "<=".

This is similar to a previous bug where qpid-cpp-server obsoleted itself: https://bugzilla.redhat.com/show_bug.cgi?id=832724

Comment 1 Michael Hrivnak 2012-09-25 16:06:39 UTC
You can work around this problem by explicitly uninstalling qpid-cpp-server-daemon, and then yum will happily install qpid-cpp-server version 0.18.

 $ sudo yum uninstall qpid-cpp-server-daemon
 $ sudo yum update

Comment 2 Darryl L. Pierce 2012-09-26 11:19:08 UTC

*** This bug has been marked as a duplicate of bug 832724 ***