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.
DescriptionYaakov Selkowitz
2016-06-10 06:49:33 UTC
golang has been enabled on aarch64 for 7.3 in bug 1330711. For feature parity with x86, this package also can and should be enabled. As it it technically noarch, setting BuildArch accordingly is the proper way; it can be excluded from the composes by RCM if that's an issue.
Please let us know if you need any help getting this on the ACL.
(In reply to Yaakov Selkowitz from comment #2)
> Either this should be made noarch, or ExclusiveArch: %{go_arches}, for
> enablement of aarch64, ppc64le, and s390x.
Due to how go_arches is provided, this actually needs to be:
+ExclusiveArch: %{?go_arches:%{go_arches}}%{!?go_arches:x86_64 aarch64 ppc64le s390x}
(In reply to Yaakov Selkowitz from comment #3)
> (In reply to Yaakov Selkowitz from comment #2)
> > Either this should be made noarch, or ExclusiveArch: %{go_arches}, for
> > enablement of aarch64, ppc64le, and s390x.
>
> Due to how go_arches is provided, this actually needs to be:
>
> +ExclusiveArch: %{?go_arches:%{go_arches}}%{!?go_arches:x86_64 aarch64
> ppc64le s390x}
That definition didn't work. It tried to build on ppc64 as well for some reason that I don't know.
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13012563
I went with a straight ExclusiveArch: i686 x86_64 ppc64le aarch64 s390x and it built fine:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=13012621
I'll attach the patch.
Created attachment 1271413[details]
Patch to enable multi-arch in 7.4
Can we please get this committed and built? The missing package on these architectures is breaking the compose of Server-optional in 7.4 (bug 1429054)
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-2017:2278