Bug 6581 - Build failures as confined SELinux user
Summary: Build failures as confined SELinux user
Status: RESOLVED DUPLICATE of bug 6580
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.8
Assignee: Seebs
QA Contact:
URL:
Whiteboard:
Depends on: 6580
Blocks:
  Show dependency tree
 
Reported: 2014-07-26 12:43 UTC by Enrico Scholz
Modified: 2015-01-09 17:15 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Enrico Scholz 2014-07-26 12:43:35 UTC
Recent pseudo breaks 'install ... && sed -i' sequences within do_install() (see bug #6580).  Unfortunately, this is done in a lot of recipes (base-files, base-passwd, python, glib-2.0, ...).

There are various fixes (in order of my preference):

1. modify 'pseudo' to ignore 'selinux.*' xattrs for now

2. modify 'pseudo' to emulate SELinux behavior

3. change affected recipes to do the 'sed -i' in do_configure() or do_compile()

4. revert to a previous 'pseudo' version

5. create a 'sed' wrapper in a preferred $PATH which catches 'sed -i' and executes it in a 'pseudo' friendly way

6. change 'install' to skip setting of SELinux context; IMO this is not a practical solution because 'install' comes from the linux distribution. ditto for 'sed'

7. document that OE builds must be done as unconfined SELinux user resp. with disabled SELinux.  IMO, this would be a very bad fix because it lowers security significantly.
Comment 1 Seebs 2015-01-09 17:15:37 UTC
This and 6580 appear to be the same thing, so I'm closing one as a dup.

*** This bug has been marked as a duplicate of bug 6580 ***