Bug 1349450

Summary:	Use something else that chroot to build rpm
Product:	[Community] GlusterFS	Reporter:	M. Scherer <mscherer>
Component:	project-infrastructure	Assignee:	Nigel Babu <nigelb>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
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:	2017-05-22 03:09:39 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:

Description M. Scherer 2016-06-23 13:16:00 UTC

While I suspect chroot are fine to build rpms, there is some case where the kernel might matter when building, such as http://www.fewbytes.com/docker-selinux-and-the-myth-of-kernel-indipendence/ 

So opening a bug to track that;

Comment 1 Nigel Babu 2017-05-22 03:09:39 UTC

Having read the associated blog post, I'm going to close this issue. We tend to build on the target OS for Ubuntu, Debian, and Fedora. So this shouldn't be a problem for us. In the near term, there isn't much we can do to fix this.