Bug 1691402 - rpm: brp-python-bytecompile breaks for new Python 3 packages in RHEL7
Summary: rpm: brp-python-bytecompile breaks for new Python 3 packages in RHEL7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rpm
Version: 7.7
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Pavlina Moravcova Varekova
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks: 1597718 1639030 1660563 1660573
TreeView+ depends on / blocked
 
Reported: 2019-03-21 14:31 UTC by Tomas Orsava
Modified: 2019-08-06 13:11 UTC (History)
6 users (show)

Fixed In Version: rpm-4.11.3-39.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 13:11:23 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:2259 None None None 2019-08-06 13:11:37 UTC

Description Tomas Orsava 2019-03-21 14:31:36 UTC
Hi,
the brp-python-bytecompile script on RHEL7 has a bug that's affecting the newly added Python 3 packages (see blocked bugs).

I've just noticed that the brp-python-bytecompile script contains an old bug:
When I'm building a Python 3 package, brp-python-bytecompile first checks if the default python interpreter (/usr/bin/python) in installed, and because it isn't it quits. However, it does not need the default python to compile the /usr/lib/python3.6/ files.

The bug was fixed upstream 2 years ago:
https://github.com/rpm-software-management/rpm/commit/a8e51b3bb05c6acb1d9b2e3d34f859ddda1677be

I'll open a PR.



We're adding the new Python 3 packages in RHEL7.7, so it would be great if this could be fixed in the same release as well. If you agree, I'll ask the PM for an ack, and the QE too if you tell me who's the right person.

Comment 1 Tomas Orsava 2019-03-21 14:44:30 UTC
Pull Request: https://src.osci.redhat.com/rpms/rpm/pull-request/10

Comment 6 errata-xmlrpc 2019-08-06 13:11:23 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://access.redhat.com/errata/RHEA-2019:2259


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