On Wed, 2023-06-21 at 10:58 +0200, Martin Jansa wrote:
> There is maybe unexpected change in behavior caused by this.
>
> Before it was triggering error only for .patch files in oe-core,
> while now it seems to apply for all recipes from oe-core layer
> (independently from where the .patch file
There is maybe unexpected change in behavior caused by this.
Before it was triggering error only for .patch files in oe-core, while now
it seems to apply for all recipes from oe-core layer (independently from
where the .patch file was added), so e.g. meta-raspberrypi is now causing
bluez5
On Tue, 2023-06-20 at 22:16 +0200, Luca Ceresoli wrote:
> Hi Richard,
>
> On Mon, 19 Jun 2023 15:06:02 +0100
> "Richard Purdie" wrote:
>
> > Now that we have layer overrides, we can easily enable patch-status in
> > ERROR_QA without the hardcoded code making it easier for other layers
> > to
> On 19 Jun 2023, at 15:06, Richard Purdie via lists.openembedded.org
> wrote:
>
> Now that we have layer overrides, we can easily enable patch-status in
> ERROR_QA without the hardcoded code making it easier for other layers
> to opt into the checks.
>
> Signed-off-by: Richard Purdie
>
Now that we have layer overrides, we can easily enable patch-status in
ERROR_QA without the hardcoded code making it easier for other layers
to opt into the checks.
Signed-off-by: Richard Purdie
---
meta/classes-global/insane.bbclass | 16 +++-
1 file changed, 3 insertions(+), 13
