Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1219953

Summary:	The python-gluster RPM should be 'noarch'
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	packaging	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	3.7.0	CC:	hchiramm, kkeithle
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1219954 (view as bug list)		Environment:
Last Closed:	2015-06-20 09:48:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1219954
Bug Blocks:	1227206

Description Niels de Vos 2015-05-08 19:45:45 UTC

Description of problem:
When building RPMs from the Gluster sources, the python-gluster package is architecture dependent. This is wrong, the package does not contain any architecture dependent binaries, all normal Python packages should be 'noarch'.

Version-Release number of selected component (if applicable):
3.7.0

How reproducible:
100%

Steps to Reproduce:
1. clone the glusterfs repository
2. make -C extras/LinuxRPM glusterrpms


Additional info:
This should also get fixed in the Fedora package.

Comment 1 Anand Avati 2015-05-20 13:42:01 UTC

REVIEW: http://review.gluster.org/10848 (glusterfs.spec.in: python-gluster should be 'noarch') posted (#1) for review on release-3.7 by Kaleb KEITHLEY (kkeithle)

Comment 2 Anand Avati 2015-06-01 18:46:19 UTC

REVIEW: http://review.gluster.org/10848 (glusterfs.spec.in: python-gluster should be 'noarch') posted (#2) for review on release-3.7 by Kaleb KEITHLEY (kkeithle)

Comment 3 Niels de Vos 2015-06-02 08:20:18 UTC

The required changes to fix this bug have not made it into glusterfs-3.7.1. This bug is now getting tracked for glusterfs-3.7.2.

Comment 4 Niels de Vos 2015-06-20 09:48:12 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.2, please reopen this bug report.

glusterfs-3.7.2 has been announced on the Gluster Packaging mailinglist [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://www.gluster.org/pipermail/packaging/2015-June/000006.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user