| Summary: | Some QA errors no longer enabled | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Paul Eggleton <bluelightning> |
| Component: | configuration | Assignee: | Paul Eggleton <bluelightning> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | High | CC: | alexandrux.palalau, jessica.zhang, kergoth |
| Version: | 1.5 | ||
| Target Milestone: | 1.5 M2 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | Regression (Used to work) |
| Verified: | Documentation change: | Don't know | |
|
Description
Paul Eggleton
2013-06-19 16:01:18 UTC
We'll also need to mention this in the migration notes for 1.5 as users may have set their own values for these variables. It turns out that OE-Core's default ERROR_QA and WARN_QA (from insane.bbclass) were fine here, it was just poky.conf that didn't mention a number of the checks in its values. A patch has been sent for review to add these back additionally with a lean towards making them errors rather than warnings. For reference, the list of QA checks that were affected by this issue: already-stripped compile-host-path dep-cmp files-invalid incompatible-license installed-vs-shipped install-host-path libdir packages-list perm-config perm-line perm-link pkgv-undefined pn-overrides split-strip var-undefined xorg-driver-abi That's a relief, thanks for looking into this, and sorry about the hassle. No problem. The silver lining is that some of these were defined as errors in OE-Core but were being treated as warnings in Poky so we had an undiscovered inconsistency already; also, I found that a bunch of the checks aren't documented in the reference manual section on insane.bbclass (I have added bug 4788 to fix the latter). Fix merged to master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=c1df5188bb2851bcc5a3f483b0a0b4c4f884e3c7 Swithing to verified. Commit ID: a1d9b6df86b0829d591cae57ae351f6d96e63557 |