Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 604578 - File conflict between tog-pegasus and libcmpiCppImpl0
File conflict between tog-pegasus and libcmpiCppImpl0
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: releng (Show other bugs)
All Linux
high Severity high
: rc
: ---
Assigned To: Dennis Gregorovic
Release Test Team
Depends On:
Blocks: 582286 622919
  Show dependency treegraph
Reported: 2010-06-16 05:44 EDT by Alexander Todorov
Modified: 2014-12-30 20:15 EST (History)
13 users (show)

See Also:
Fixed In Version: sblim-cmpi-devel-2.0.1-5.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 622919 (view as bug list)
Last Closed: 2010-11-10 17:15:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alexander Todorov 2010-06-16 05:44:47 EDT
Description of problem:

Both tog-pegasus and libcmpiCppImpl0 packages provide the same files which causes a conflict when trying to install libcmpiCppImpl0. 

toge-pegasus is in the base repository while libcmpiCppImpl0 is in the optional.

tog-pegasus-2.9.1-3.el6.x86_64.rpm | grep libcmpi

# rpm -qpl libcmpiCppImpl0-2.0.1-2.el6.x86_64.rpm 

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

How reproducible:

Steps to Reproduce:
1. Try to install libcmpiCppImpl0 after tog-pegasus has been installed;
2. Alternatively try to install all packages from the optional repo which includes libcmpiCppImpl0 and tog-pegasus-devel.
Actual results:
File conflict, yum transaction is aborted.

Expected results:
No file conflicts.

Additional info:
It seems that the provided library from both packages is the same. Why do we have 2 packages providing the same library and what's the difference between them?
Comment 1 Vitezslav Crhonek 2010-06-16 06:03:14 EDT
See bz588914 for more details.
Comment 2 Alexander Todorov 2010-06-16 06:30:16 EDT
OK, so tog-pegasus and libcmpiCppImpl0 will conflict with each other. 
Moving to releng to get their input as well. 

is there something we can do wrt those two packages?
Comment 3 Vitezslav Crhonek 2010-06-30 10:11:40 EDT
Additional commentaries to this issue are within bz608846.
Comment 4 Bill Nottingham 2010-07-01 12:07:06 EDT
My preference would be to have a single implementation of libcmpiCppImpl0 packaged, that could be used by both tog-pegasus and other providers. Is this not possible to split it out of tog-pegasus and have tog-pegasus link against it?
Comment 5 Marizol Martinez 2010-07-01 14:08:47 EDT
Bill -- That was our hope too, but that won't work: https://bugzilla.redhat.com/show_bug.cgi?id=608846#c6
Comment 6 Marizol Martinez 2010-07-01 14:16:11 EDT
Wait a sec, I think Bill is suggesting to provide all of the following into libcmpiCppImpl0:

API for Pegasus C++ providers
API for Pegasus C++ clients
API for CMPI C providers
API for CMPI C++ wrapper library

And that way both tog-pegasus and other providers can use the same library. Duh! ;-).

Vita -- What do you think?
Comment 7 Marizol Martinez 2010-07-12 09:57:17 EDT
Please disregard my previous comment. After chatting with Vita, that won't work either. The version of the lib. tog-pegasus uses *is* diff. from the one SFCB uses although they are the named the same :-/.
Comment 8 Bill Nottingham 2010-07-13 13:48:08 EDT
Any chance we could move the tog-pegasus library out of ${libdir} to a private directory, so there's not a direct file/package conflict? (Possibly even rename it?)
Comment 20 Dennis Gregorovic 2010-07-29 15:58:38 EDT
I think we're good.

$ find RHEL6.0-20100729.1/6 -name libcmpiC*
Comment 26 Alexander Todorov 2010-08-05 04:19:38 EDT
Moving to VERIFIED per Jan's testing, see comment #23
Comment 31 releng-rhel@redhat.com 2010-11-10 17:15:41 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Comment 32 Zenon Panoussis 2011-03-10 16:40:12 EST
(In reply to comment #9 and comment #31)

They still conflict. 

rpm -qpl libcmpiCppImpl0-2.0.1-5.el6.x86_64.rpm

This comes from sblim-cmpi-devel-2.0.1-5.el6.src.rpm, the one that's supposed to have fixed it and the only one released in el6. And sblim-cmpi-devel.spec says

%package -n libcmpiCppImpl0
License:        EPL
Summary:        CMPI C++ wrapper library
Group:          Development/Libraries
Conflicts:      tog-pegasus

Could you please re-open?
Comment 33 Subhendu Ghosh 2011-03-10 17:09:22 EST
Please see the release notes. RHEL 5 introduced a feature known as @conflicts where a set of rpms that are known to conflict would be listed. RHEL6 supports that structure. 

All packages that include conflicts in RHEL6 are listed in a yum group call -@conflicts-<variant> (eg: -@conflicts-server ).

If you want to install packages from that group you have to take special care to select that package and nesure what its conflicting with is not installed.
Comment 34 Zenon Panoussis 2011-03-10 18:44:00 EST
But comment #9 says ".so* files moved to %{_libdir}/sblim subdir" and that has obviously not happened. It also says "explicit conflict in libcmpiCppImpl0 removed", but the explicit conflict is still there. To me, this looks like an accidentally reverted patch somewhere after the fix.
Comment 35 Ondrej Vasik 2011-03-11 01:43:34 EST
No, it was not accidently reverted, but different approach was requested by the customer - so the revert was intentional. I'll remove the comment #9 to prevent confusion in future.

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