| Summary: | Taints are not being held | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Richard Purdie <richard.purdie> |
| Component: | bitbake | Assignee: | Paul Eggleton <bluelightning> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | poky.bs.watcher, poky.watcher |
| Version: | 1.6 | ||
| Target Milestone: | 1.6 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
If you "bitbake systemd", then hack something in ${WORKDIR}/image, then "bitbake systemd -c package -f", it correctly adds a taint and then packages the modification in /image. If you then "bitbake systemd", you'd expect it to rebuild the other systemd packages and use them. It does not, it restores the original do_package output from sstate. This would appear to be a bug with the taint handling.