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 1919348

Summary: go-compilers-golang-compiler and go-srpm-macros provide different %gobuild macros
Product: Red Hat Enterprise Linux 8 Reporter: Edjunior Barbosa Machado <emachado>
Component: go-srpm-macrosAssignee: David Benoit <dbenoit>
Status: CLOSED MIGRATED QA Contact: Edjunior Barbosa Machado <emachado>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.4CC: cfergeau, dbenoit, obudai, opohorel
Target Milestone: rcKeywords: FutureFeature, MigratedToJIRA, Reopened, Triaged
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 16:34:20 UTC Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Edjunior Barbosa Machado 2021-01-22 16:01:11 UTC
Description of problem:
Both go-compilers-golang-compiler-1-20.el8 from CRB repo and go-srpm-macros-2-17.el8 from AppStream provide different versions of %gobuild macro.

In a system with both installed, %gobuild macro from go-compilers-golang-compiler takes precedence over the definition from go-srpm-macros.

Version-Release number of selected component (if applicable):
go-srpm-macros-2-17.el8
go-compilers-golang-compiler-1-20.el8

Steps to Reproduce:

When only go-srpm-macros installed, %gobuild is defined as:

[root@ci-vm-10-0-138-246 ~]# rpm -qa go-srpm-macros go-compilers-golang-compiler
go-srpm-macros-2-17.el8.noarch
[root@ci-vm-10-0-138-246 ~]# rpm -E '%gobuild'

CGO_CPPFLAGS="-D_FORTIFY_SOURCE=2 -fstack-protector-all" go build -compiler gc -buildmode pie '-tags=rpm_crashtraceback libtrust_openssl ' -ldflags "-linkmode=external -compressdwarf=false ${LDFLAGS:-} -B 0x$(head -c20 /dev/urandom|od -An -tx1|tr -d ' \n') -extldflags '%__global_ldflags'" -a -v -x ;
[root@ci-vm-10-0-138-246 ~]# 

Compared to another system with both go-compilers-golang-compiler and go-srpm-macros installed:

[root@ci-vm-10-0-139-131 ~]# rpm -qa go-srpm-macros go-compilers-golang-compiler
go-srpm-macros-2-17.el8.noarch
go-compilers-golang-compiler-1-20.el8.x86_64
[root@ci-vm-10-0-139-131 ~]# rpm -E '%gobuild'

%ifnarch ppc64 
go build -buildmode pie -compiler gc -tags=rpm_crashtraceback -ldflags "-compressdwarf=false ${LDFLAGS:-} -B 0x$(head -c20 /dev/urandom|od -An -tx1|tr -d ' \n') -extldflags '%__global_ldflags'" -a -v -x ;
%else 
go build -compiler gc -tags=rpm_crashtraceback -ldflags "-compressdwarf=false ${LDFLAGS:-} -B 0x$(head -c20 /dev/urandom|od -An -tx1|tr -d ' \n') -extldflags '%__global_ldflags'" -a -v -x ;
%endif
[root@ci-vm-10-0-139-131 ~]#

Comment 12 RHEL Program Management 2022-07-22 07:28:05 UTC
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.

Comment 13 Ondřej Pohořelský 2022-07-22 13:36:04 UTC
Reopening this bug, because both packages still exist in RHEL 8 and both provide different %gobuild macro.
Adding FutureFeature keyword, so this doesn't get automatically closed again.

Comment 18 RHEL Program Management 2023-01-22 07:27:37 UTC
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.

Comment 23 RHEL Program Management 2023-07-23 07:31:14 UTC
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.

Comment 25 RHEL Program Management 2023-09-22 16:32:31 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 26 RHEL Program Management 2023-09-22 16:34:20 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.