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.

Bug 1757833

Summary: %py_build uses --executable="%{__python2}
Product: Red Hat Enterprise Linux 8 Reporter: Miro Hrončok <mhroncok>
Component: python-rpm-macrosAssignee: Python Maintainers <python-maint>
Status: CLOSED ERRATA QA Contact: RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: carlwgeorge, cstratak, jhouska, pviktori, torsava
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-rpm-macros-3-38.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 15:34:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Miro Hrončok 2019-10-02 14:15:40 UTC 
Apparently, the %py_build macro should respect the global definition of %__python, however it hardcodeds --executable="%{__python2} and hence it makes it impossible to do the following:

%global __python %__python3
...
%py_build

python-rpm-macros 3-37
Comment 1 Miro Hrončok 2019-10-02 14:17:53 UTC 
Fedora fix: https://src.fedoraproject.org/rpms/python-rpm-macros/c/90b0bf74804e4b20ce2bad9bd1ed61ff1f0d1e3d

RHEL 7 bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1757834
Comment 2 Tomas Orsava 2019-10-03 09:35:52 UTC 
In RHEL8, this might be a bigger issue than in RHEL7 since we don't define %__python as far as I recall.

However, the only Python 2 packages that we ship in RHEL8 itself are python27, which should be fine and we can check them all by hand.
It might cause havoc in the buildroot though, where lots of Python 2 packages remain.
Comment 3 Miro Hrončok 2019-10-03 09:40:26 UTC 
This does not impact Python 2 packages. This only impacts Python 3 packages which define %__python to %__python3 AND use %py_build (not %py3_build).
Comment 4 Tomas Orsava 2019-10-03 11:23:01 UTC 
(In reply to Miro Hrončok from comment #3)
> This does not impact Python 2 packages. This only impacts Python 3 packages
> which define %__python to %__python3 AND use %py_build (not %py3_build).

How about Python 2 packages that use %py_build and it worked, since it used %__python2, but now it won't, since %__python is not defined?
Comment 5 Miro Hrončok 2019-10-03 11:43:47 UTC 
Now:

%py_build is: %{__python} ... --executable %{__python2}

It already doesn't work when %{__python} is not defined.

It also doesn't work when %{__python} is defined to anything other than %{__python2}.



Desired:

%py_build is: %{__python} ... --executable %{__python}

It already doesn't work when %{__python} is not defined.

It works when %{__python} is defined to anything reasonable, such as %{__python2} or %{__python3}.
Comment 6 Tomas Orsava 2019-10-03 11:46:46 UTC 
Oh I see, in that case I don't see any backwards incompatibility. +1
Comment 9 Jan Houska 2019-11-28 11:53:12 UTC 
Verified: as SanityOnly


Version:
python-rpm-macros-3-38.el8


Content of is now :
rpmbuild/SOURCES/macros.python

%py_build() %{expand:\\\
  CFLAGS="${CFLAGS:-${RPM_OPT_FLAGS}}" LDFLAGS="${LDFLAGS:-${RPM_LD_FLAGS}}"\\\
  %{__python} %{py_setup} %{?py_setup_args} build --executable="%{__python} %{py_shbang_opts}" %{?*}
  sleep 1
}
Comment 11 errata-xmlrpc 2020-04-28 15:34:56 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/RHBA-2020:1591