Bug 1534253 – remove ExclusiveArch directive from SPEC file

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1534253 - remove ExclusiveArch directive from SPEC file

Summary:	remove ExclusiveArch directive from SPEC file

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Gluster Storage
Classification:	Red Hat
Component:	build (Show other bugs)
Sub Component:
Version:	3.4
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	---
Target Release:	RHGS 3.4.0
Assigned To:	Milind Changire
QA Contact:	Rahul Hinduja
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	1527773 (view as bug list)
Depends On:	1527772
Blocks:	1481451 1503137
	Show dependency tree / graph

Reported:	2018-01-14 10:01 EST by Atin Mukherjee
Modified:	2018-09-04 02:42 EDT (History)
CC List:	9 users (show)

See Also:
Fixed In Version:	glusterfs-3.12.2-2
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1527772
Environment:
Last Closed:	2018-09-04 02:40:51 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2018:2607	None	None	None	2018-09-04 02:42 EDT

Groups: None (edit)

Comment 5 Sunil Kumar Acharya 2018-01-24 04:48:05 EST

*** Bug 1527773 has been marked as a duplicate of this bug. ***

Comment 6 Ambarish 2018-03-01 03:55:12 EST

Both RHEL 7 Client and Server builds have rpms built for multi-archs

Client : https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=653416
Server : https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=653415

I am moving this bug to Verified.

Comment 9 errata-xmlrpc 2018-09-04 02:40:51 EDT

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/RHSA-2018:2607

Note You need to log in before you can comment on or make changes to this bug.