Bug 1527772 - remove ExclusiveArch directive from SPEC file
Summary: remove ExclusiveArch directive from SPEC file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: build
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHGS 3.3.1 Async
Assignee: Milind Changire
QA Contact: Vivek Das
URL:
Whiteboard:
Depends On:
Blocks: 1445922 1534253
TreeView+ depends on / blocked
 
Reported: 2017-12-20 05:24 UTC by Milind Changire
Modified: 2018-01-14 15:01 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.8.4-52.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1534253 (view as bug list)
Environment:
Last Closed: 2018-01-11 02:46:39 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1527773 0 unspecified CLOSED remove ExclusiveArch directive from SPEC file 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2018:0083 0 normal SHIPPED_LIVE glusterfs bug fix update 2018-01-11 07:46:21 UTC

Internal Links: 1527773

Description Milind Changire 2017-12-20 05:24:08 UTC 
Description of problem:
ExclusiveArch: x86_64 aarch64

The above directive in the SPEC file prohibits builds for other architectures.
This should be removed so that builds can be done for choice of architectures whenever required
Comment 6 Yaakov Selkowitz 2017-12-20 15:22:08 UTC 
How will this get to the 3.4.0 branch too?
Comment 7 Atin Mukherjee 2017-12-21 04:23:39 UTC 
(In reply to Yaakov Selkowitz from comment #6)
> How will this get to the 3.4.0 branch too?

The same changes done in 3.3.1 branch will be taken care in 3.4.0 branch as well through BZ 1527773.
Comment 8 Vivek Das 2017-12-28 12:13:40 UTC 
Verified the bug in build log of the concerned errata.
Checked for the patch that includes the removal of "ExclusiveArch: x86_64 aarch64".
Marking the bug as verified.
Comment 10 errata-xmlrpc 2018-01-11 02:46:39 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-2018:0083
Note You need to log in before you can comment on or make changes to this bug.