Red Hat Bugzilla – Bug 1113671
arch specific submodules like python-backports-lzma are no longer supported
Last modified: 2016-01-04 09:44:29 EST
The changes done for cleanup bug #1061051 should be reverted as the existing structure is required to support arch specific submodules like python-backports-lzma The specific issue is that one can't import %{buildroot}%{python_sitearch}/backports/lzma/... if there is no %{buildroot}%{python_sitearch}/backports/__init__.py See bug #1061051 for details on how to address this
Fixed in 7.1 branch: 0f19456405003452ecc5d3f72f833b5adef87970
I would like to point out that the upgrade fails if python-backports-lzma is installed because the files /usr/lib64/python2.7/site-packages/backports/__init__.py{,c,o} conflict. I don't think the update should be shipped as long as python-backports-lzma owns these files.
Is there a way to ensure that python-backports-lzma -- iff installed -- will be upgraded to python-backports-lzma-0.0.2-8.el7 whenever python-backports is upgraded to python-backports-1.0-7.el7 in order to prevent the scenario outlined in bug 1158538? Currently, python-backports-lzma simply depends on python-backports without a version specification, meaning that python-backports upgrade does not automatically trigger python-backports-lzma upgrade. Apparently, making python-backports depend on python-backports-lzma >= 0.0.2-8 is not enough, since it would install python-backports-lzma even if it were not present on the system in the first place. Can you think of a solution to this problem?
I'm not sure if it will trigger python-backports-lzma upgrade, but we probably can add a conflicts tag in python-backports to explicitly say that it will not work with older python-backports-lzma.
That sounds like a reasonable solution to me. Shall the erratum be respun, then?
Fixed in 7.1 branch: 27c9796342098ac1da62e4a22f28db28a621db35
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://rhn.redhat.com/errata/RHBA-2015-0576.html