Description of problem: Conflicts between attempted installs of python27 and python33 tbb-debuginfo Version-Release number of selected component (if applicable): python27-tbb-debuginfo-4.1-5.20130314.el6.x86_64.rpm python33-tbb-debuginfo-4.1-5.20130314.el6.x86_64.rpm Steps to Reproduce: 1. yum install python33-tbb-debuginfo python27-tbb-debuginfo 2. 3. Actual results: file /usr/lib/debug/.build-id/df/e4ae9804b2269dabb1b41347c679732359bc86 conflicts between attempted installs of python33-tbb-debuginfo-4.1-5.20130314.el6.x86_64 and python27-tbb-debuginfo-4.1-5.20130314.el6.x86_64 file /usr/lib/debug/.build-id/df/e4ae9804b2269dabb1b41347c679732359bc86.debug conflicts between attempted installs of python33-tbb-debuginfo-4.1-5.20130314.el6.x86_64 and python27-tbb-debuginfo-4.1-5.20130314.el6.x86_64 Expected results: debuginfo packages installed Additional info:
We were trying to workaround this by adding some unused symbols so hashes would differ. Unfortunately this introduced new issue in /usr/src/debug/ -- source files started conflicting: file /usr/src/debug/tbb41_20130314oss/src/tbb/tbb_main.cpp from install of python33-tbb-debuginfo-4.1-5.20130314.el6.x86_64 conflicts with file from package python27-tbb-debuginfo-4.1-5.20130314.el6.x86_64 file /usr/src/debug/tbb41_20130314oss/src/tbb/tbb_main.h from install of python33-tbb-debuginfo-4.1-5.20130314.el6.x86_64 conflicts with file from package python27-tbb-debuginfo-4.1-5.20130314.el6.x86_64 'tbb41_20130314oss' is a root directory inside tarball with sources. Subsequently we could rename dir in tarball too but I think it's way too hacky. From my point of view, since packages python{27,33}-tbb-debuginfo are practically identical I would prefer supplying only on of these packages.
Fortunately, this is easy to workaround. One just need to change directory structure during build process.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0610.html