Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionPanu Matilainen
2019-06-27 10:23:07 UTC
Description of problem:
Commit 046d218998fa972862e6ed9bc6542a1035fe656f dropped %__python as the first argument to brp-python-bytecompile, shifting what are positional arguments without adjusting the script accordingly.
This means that the script still expects the path of the python interpreter as the first argument, but receives "1" from %_python_bytecompile_errors_terminate_build macro. The script uses this for the value of $default_python:
# If we don't have a default python interpreter, we cannot proceed
default_python=${1:-/usr/bin/python}
if [ ! -x "$default_python" ]; then
exit 0
fi
...and presumably will exist because there's no executable named "1". With the result that the script will never do any byte-compilation at all on RHEL.
To shed some light on this:
On RHEL8, brp-python-bytecompile is called with wrong arguments
On Fedora, brp-python-bytecompile is called with correct arguments
(In reply to Miro Hrončok from comment #4)
> What Fedora change?
I was referring to bug#1721147 as I thought that we need to fix it first.
(In reply to Miro Hrončok from comment #5)
> To shed some light on this:
> On RHEL8, brp-python-bytecompile is called with wrong arguments
> On Fedora, brp-python-bytecompile is called with correct arguments
Thanks for clarification.
Comment 10Vratislav Hutsky
2020-01-08 09:01:58 UTC
So Panu and I investigated this a bit more, and it turns out the regular python binaries/libraries within the /usr/lib*/python*/ directories are not affected by this issue; they continue to be bytecompiled just fine on RHEL-8. What is affected is the ability of the script to bytecompile other locations, and the %{?_python_bytecompile_errors_terminate_build} macro which is not honored anymore.
Luckily, there's an easy way to fix this for 8.2, so I'm switching the ITR back and will do a build in a few moments.
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:1730
Description of problem: Commit 046d218998fa972862e6ed9bc6542a1035fe656f dropped %__python as the first argument to brp-python-bytecompile, shifting what are positional arguments without adjusting the script accordingly. This means that the script still expects the path of the python interpreter as the first argument, but receives "1" from %_python_bytecompile_errors_terminate_build macro. The script uses this for the value of $default_python: # If we don't have a default python interpreter, we cannot proceed default_python=${1:-/usr/bin/python} if [ ! -x "$default_python" ]; then exit 0 fi ...and presumably will exist because there's no executable named "1". With the result that the script will never do any byte-compilation at all on RHEL.