| Summary: | Multiple providers for runtime module-init-tools cause build failures | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Beth Flanagan <elizabeth.flanagan> |
| Component: | kernel | Assignee: | Khem Raj <raj.khem> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bruce.ashfield, elizabeth.flanagan, jiajun.xu, sgw, tom.zanussi |
| Version: | unspecified | ||
| Target Milestone: | 1.3 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | (No QA needed) | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Beth Flanagan
2012-05-08 19:29:23 UTC
I had a patch to remove module-init-tools which would then take care of this issue has not yet been applied the other option is to add PREFERRED_PROVIDER I thought we would replace the module-init-tools with kmod but if they have to coexist then we have add it through IMAGE_FEATURES or some such. I will check if kmod is not providing any of the packages that module-init-tools provided before. I have sent a pull request form kmod I would be interested to know if this problem still happens with patches in that series. http://patchwork.openembedded.org/patch/27319/ Verified as fixed. |