Bug 1349450 - Use something else that chroot to build rpm
Summary: Use something else that chroot to build rpm
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nigel Babu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-23 13:16 UTC by M. Scherer
Modified: 2017-05-22 03:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-22 03:09:39 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

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.


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