All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	akuster808 <akuster808@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	 Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 3/5] insane.bbclass: add a RECIPE_MAINTAINER check (oe-core recipes only)
Date: Fri, 28 Apr 2023 12:36:51 +0200	[thread overview]
Message-ID: <CA+chaQf+evL-UwG4RComw=y5zQfxbSN0=aXzVNQghL+ra_usAw@mail.gmail.com> (raw)
In-Reply-To: <20230427073528.3956414-3-alex@linutronix.de>

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

On Thu, Apr 27, 2023 at 9:35 AM Alexander Kanavin <alex.kanavin@gmail.com>
wrote:

> Absent maintainer entries are as well a frequent source of friction, as
> they are checked
> only in selftest, and so aren't revealed until autobuilder runs.
>
> The selftest is retained as it also checks for obsolete entries in
> maintainers.inc
> (not possible to do in insane class).
>

I've seen many errors triggered by this and was wondering what's going on
and it's caused by meta-security layers which provide own
conf/distro/include/maintainers.inc:

meta-security $ find . -name maintainers.inc
./meta-tpm/conf/distro/include/maintainers.inc
./conf/distro/include/maintainers.inc

So this doesn't work well with:
meta/conf/distro/defaultsetup.conf:include
conf/distro/include/maintainers.inc

as it "replaces" the file instead of adding more RECIPE_MAINTAINERs.

I think this should be fixed somehow before this gets enabled in oe-core.

[-- Attachment #2: Type: text/html, Size: 1378 bytes --]

  reply	other threads:[~2023-04-28 10:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27  7:35 [PATCH 1/5] insane.bbclass: add a SUMMARY/HOMEPAGE check (oe-core recipes only) Alexander Kanavin
2023-04-27  7:35 ` [PATCH 2/5] selftest/distrodata: clean up exception lists in recipe maintainers test Alexander Kanavin
2023-04-27  7:35 ` [PATCH 3/5] insane.bbclass: add a RECIPE_MAINTAINER check (oe-core recipes only) Alexander Kanavin
2023-04-28 10:36   ` Martin Jansa [this message]
2023-04-28 11:54     ` [OE-core] " Alexander Kanavin
2023-04-27  7:35 ` [PATCH 4/5] dhcpcd: use git instead of tarballs Alexander Kanavin
2023-04-27  7:35 ` [PATCH 5/5] perl: patch out build paths from native binaries Alexander Kanavin
2023-05-05 11:43 ` [OE-core] [PATCH 1/5] insane.bbclass: add a SUMMARY/HOMEPAGE check (oe-core recipes only) Ross Burton
2023-05-05 16:51   ` Alexander Kanavin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+chaQf+evL-UwG4RComw=y5zQfxbSN0=aXzVNQghL+ra_usAw@mail.gmail.com' \
    --to=martin.jansa@gmail.com \
    --cc=akuster808@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.