| Summary: | Unexpected file ownership in do_install | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Robert Wortman <rww.mce> |
| Component: | multimedia | Assignee: | Ross Burton <ross.burton> |
| Status: | VERIFIED NOTABUG | QA Contact: | Alexandru Georgescu <alexandru.c.georgescu> |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | alexandru.c.georgescu, kergoth, meta.mr.watcher, meta.watcher, poky.bs.watcher, poky.watcher, ross.burton |
| Version: | 1.8 | ||
| Target Milestone: | 2.0 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Robert Wortman
2015-09-03 22:50:33 UTC
Fakeroot runs *as root*, so you can change owner to root or other users, it doesn't change the existing ownership of existing files, those are left alone. Any do_install which blindly copies files to ${D} without chown'ing them will end up with incorrect ownership in the binary packages, this is expected behavior. Generally buildsystems we call adjust ownership to be correct for the files they install when they run 'make install', so in most cases it's not an issue, only when files are manually installed does it become problematic. Basically, this is working as expected.
What Chris says is right - this is working as expected and the problem is in a recipe and/or class. Since this bug was filed there's been a new QA test added to vet recipes for this problem at packaging time instead hopefully tripping a rootfs warning, and the problems in oe-core are all fixed (caused by bad ptest install logic which was copying a file without fixing ownership, fixed in ptest.bbclass). verified as per above comments |