Bug 604578

See bz588914 for more details.

OK, so tog-pegasus and libcmpiCppImpl0 will conflict with each other. 
Moving to releng to get their input as well. 

Dennis,
is there something we can do wrt those two packages?

Additional commentaries to this issue are within bz608846.

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?

Bill -- That was our hope too, but that won't work: https://bugzilla.redhat.com/show_bug.cgi?id=608846#c6

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?

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 :-/.

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?)

I think we're good.

$ find RHEL6.0-20100729.1/6 -name libcmpiC*
RHEL6.0-20100729.1/6/Server/i386/os/Packages/libcmpiCppImpl0-2.0.1-5.el6.i686.rpm
RHEL6.0-20100729.1/6/Server/s390x/os/Packages/libcmpiCppImpl0-2.0.1-5.el6.s390x.rpm
RHEL6.0-20100729.1/6/Server/s390x/os/Packages/libcmpiCppImpl0-2.0.1-5.el6.s390.rpm
RHEL6.0-20100729.1/6/Server/ppc64/os/Packages/libcmpiCppImpl0-2.0.1-5.el6.ppc64.rpm
RHEL6.0-20100729.1/6/Server/ppc64/os/Packages/libcmpiCppImpl0-2.0.1-5.el6.ppc.rpm
RHEL6.0-20100729.1/6/Server/x86_64/os/Packages/libcmpiCppImpl0-2.0.1-5.el6.i686.rpm
RHEL6.0-20100729.1/6/Server/x86_64/os/Packages/libcmpiCppImpl0-2.0.1-5.el6.x86_64.rpm
RHEL6.0-20100729.1/6/Workstation/i386/os/Packages/libcmpiCppImpl0-2.0.1-5.el6.i686.rpm
RHEL6.0-20100729.1/6/Workstation/x86_64/os/Packages/libcmpiCppImpl0-2.0.1-5.el6.i686.rpm
RHEL6.0-20100729.1/6/Workstation/x86_64/os/Packages/libcmpiCppImpl0-2.0.1-5.el6.x86_64.rpm

Moving to VERIFIED per Jan's testing, see comment #23

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.

(In reply to comment #9 and comment #31)

They still conflict. 

rpm -qpl libcmpiCppImpl0-2.0.1-5.el6.x86_64.rpm
/usr/lib64/libcmpiCppImpl.so
/usr/lib64/libcmpiCppImpl.so.0
/usr/lib64/libcmpiCppImpl.so.0.0.0

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?

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.

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.

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.