Hide Forgot
Description of problem: Following file conflicts have been found: Transaction check error: file /usr/lib/python2.7/site-packages/sos/plugins/leapp.py from install of leapp-repository-sos-plugin-0.9.0-4.el7.noarch conflicts with file from package sos-3.8-6.el7.noarch file /usr/lib/python2.7/site-packages/sos/plugins/leapp.pyc from install of leapp-repository-sos-plugin-0.9.0-4.el7.noarch conflicts with file from package sos-3.8-6.el7.noarch file /usr/lib/python2.7/site-packages/sos/plugins/leapp.pyo from install of leapp-repository-sos-plugin-0.9.0-4.el7.noarch conflicts with file from package sos-3.8-6.el7.noarch Version-Release number of selected component (if applicable): leapp-repository-sos-plugin-0.9.0-4.el7 sos-3.8-6.el7 Steps to Reproduce: 1. yum install leapp-repository-sos-plugin sos
This is a leapp-repository problem. No one (other than sos) ever should install anything into /usr/lib/python2.7/site-packages/sos/plugins/ directory. Reasons for this - see mail on os-devel-list I compose. Both leapp-repository-sos-plugin and sos (3.8 or newer, as delivered since 7.8/8.2) contains equivalent leapp.py that collects same data at some situations. Please, remove the leapp-repository-sos-plugin package from RHEL distributions (7.8+ and 8.2+).
Hi Pavel, I guess that here is misunderstanding. There were reasons why the file has been delivered in the past inside of the leapp-repository subpackage. But yes, we plan to remove it as the reasons are obsoleted when the plugin has been added in RHEL 7.8. The next release of leapp-repository will happen on RHEL 8.2 GA release day. Btw, the issue is already resolved by Obsoletes in sos-3.8-8.
Feel free to assign it back to sos if you want to track delivery of the fix in RHEL 7.8 and release the sos-3.8-8+ through z-stream earlier than RHEL 8.2 GA date.
(In reply to Petr Stodulka from comment #3) > Btw, the issue is already resolved by Obsoletes in sos-3.8-8. Indeed, jjansky++ added it in the version that will go to 7.8.z (.1, I guess). Thanks for removal anyway!
*** Bug 1825960 has been marked as a duplicate of this bug. ***
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. https://access.redhat.com/errata/RHBA-2020:1959