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:
Fedora doesn't have BUILDTAGS in their version of go-rpm-macros. This makes builds that assume the macros are consistent between distros build with unexpected results.

I've tried to submit a patch for Fedora, but Neal Gompa is insisting on GOBUILDTAGS. I assume that's going to cause issues since people are already using BUILDTAGS as the name.

Could the maintainers of go-rpm-macros please coordinate with each other so that users have a consistent experience between distros?

Forgot the Fedora PR - https://pagure.io/go-rpm-macros/pull-request/34

For what it's worth, before today, I had no idea that RHEL forked and rewrote almost all the Go macros downstream. This was quite a shock to me. I hadn't heard from anyone working on RHEL's Go compiler stack about this, nor had anyone reached out to me or anyone else in the Fedora Go SIG about this issue before today (after everything happened). So I am extremely confused and slightly upset about the current situation.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.