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.

Description of problem:
The macro golang_arches_future is not properly populated during the installation of the go-rpm-macros package.

Version-Release number of selected component (if applicable):
3.2.0

How reproducible:
Use golang_arches_future in any specfile in CentOS Stream 9

Steps to Reproduce:
1. Use golang_arches_future in a specfile
2. Build the package
3. It will fail.

Actual results:

error: Architecture is not included: x86_64
Building target platforms: x86_64

Expected results:

No error.

Additional info:

golang_arches_future, golang_arches, and gccgo_arches are placeholders in the macros file, and later, during the installation of the package, substituted for a list of valid architectures. The solution is as simple as declare the golang_arches_future in the same way golang_arches and gccgo_arches are declared in the specfile.

See https://src.fedoraproject.org/rpms/go-rpm-macros/c/b98334becd4c52e98e433e17118f9bf0e27903cc?branch=rawhide

(In reply to Maxwell G from comment #1)
> See
> https://src.fedoraproject.org/rpms/go-rpm-macros/c/
> b98334becd4c52e98e433e17118f9bf0e27903cc?branch=rawhide

Thanks for the reference. I didn't realized that when I opened the bug I didn't link to the merge request that I already had opened.

https://gitlab.com/redhat/centos-stream/rpms/go-rpm-macros/-/merge_requests/12

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 (go-rpm-macros bug fix and enhancement update), 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-2023:6534