RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1113671 - arch specific submodules like python-backports-lzma are no longer supported
Summary: arch specific submodules like python-backports-lzma are no longer supported
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-backports
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: pre-dev-freeze
: 7.1
Assignee: Endi Sukma Dewata
QA Contact: Martin Frodl
URL:
Whiteboard:
Depends On: 1158538 1175305
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-26 15:14 UTC by Pádraig Brady
Modified: 2016-01-04 14:44 UTC (History)
10 users (show)

Fixed In Version: python-backports-1.0-8.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1061051
Environment:
Last Closed: 2015-03-05 13:33:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0576 0 normal SHIPPED_LIVE python-backports bug fix update 2015-03-05 17:07:31 UTC

Description Pádraig Brady 2014-06-26 15:14:06 UTC
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

Comment 2 Endi Sukma Dewata 2014-07-21 16:29:50 UTC
Fixed in 7.1 branch: 0f19456405003452ecc5d3f72f833b5adef87970

Comment 6 Martin Frodl 2014-10-29 14:08:02 UTC
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.

Comment 8 Martin Frodl 2014-12-18 13:43:07 UTC
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?

Comment 9 Endi Sukma Dewata 2015-01-05 16:24:40 UTC
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.

Comment 10 Martin Frodl 2015-01-12 11:54:44 UTC
That sounds like a reasonable solution to me. Shall the erratum be respun, then?

Comment 11 Endi Sukma Dewata 2015-01-13 18:09:46 UTC
Fixed in 7.1 branch: 27c9796342098ac1da62e4a22f28db28a621db35

Comment 15 errata-xmlrpc 2015-03-05 13:33:19 UTC
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


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