| Summary: | bluez5 fails at do_package_write_* | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Paul Eggleton <bluelightning> |
| Component: | connectivity | Assignee: | Saul Wold <sgw> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | cristian.iorga, meta.mr.watcher, meta.watcher, sgw |
| Version: | 1.6 | ||
| Target Milestone: | 1.5 M5 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Paul Eggleton
2013-09-11 18:18:59 UTC
We can't build both recipes in the world build as there is a collision of package name and PR values. Specificly the libasound-module-bluez which is the same in both goes backwards from r5 (bluez4) -> r0 (bluez5) and the subpackage_metadata check fails:
> ERROR: Recipe lib32-bluez5 is trying to change PR from 'r0' to 'r5'. This will cause do_package_write_* failures since the incorrect data will be used and they will be unable to find the right workdir.
It's comparing the tmp/pkgdata/runtime/lib32-libasound-module-bluez (from bluez4) with the bluez5 version in ${WORKDIR}/pkgdata/... since bluez4 was built after bluez5 and populated the tmp/pkgdata later.
EXCLUDE_FROM_WORLD both of these.
|