Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] utils/getdeveloperlib.py: fix regexp used to find package infra
Date: Tue, 15 Sep 2026 19:11:13 +0200	[thread overview]
Message-ID: <6ae8acf63efea3c90d2b3c01a47767a2@free.fr> (raw)
In-Reply-To: <20260914075245.1749775-1-thomas.petazzoni@bootlin.com>

On 14/09/2026 09:52, Thomas Petazzoni via buildroot wrote:
> There's recently been autobuilder failures on
> toolchain-external-bootlin, but I wasn't getting notified in the daily
> autobuilder e-mail for those failures, which sounded odd as DEVELOPERS
> contains:
> 
> N:      Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> [...]
> F:      toolchain/
> 
> And indeed, testing:
> 
> $ ./utils/get-developers -p toolchain-external-bootlin
> 
> returned nothing.
> 
> Turns out that the regexp FIND_INFRA_IN_PATCH and FIND_INFRA_IN_MK
> used to find the package infrastructure, and ultimately decide if a
> given .mk file contains a package, was a bit too strict:
> 
> "^\+\$\(eval \$\((host-)?([^-]*)-package\)\)$"
> 
> This would only allow packages named <something>-package or
> host-<something>-package, but the <something> should not contain any
> dash ("-"). So this works fine for cmake-package,
> host-autotools-package, but not for toolchain-external-package where
> <something> is toolchain-external and it contains a dash.
> 
> We fix this by relaxing the regexp a bit and allowing any character in
> <something>. Consider the rest of the regexp that expects $(eval
> $(<host>-<something>-package)), it seems highly unlikely to match
> anything else but the line we're interested in.
> 
> With this fix:
> 
> $ ./utils/get-developers -p toolchain-external-bootlin
> Giulio Benetti <giulio.benetti@benettiengineering.com>
> Romain Naour <romain.naour@gmail.com>
> Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> 
> This issue has existed since the toolchain-external-package
> infrastructure had been added.
> 
> Fixes: 1c99d70e5210f9d7b475736e0360ed63d16584f2 ("toolchain-external: 
> introduce toolchain-external-package")
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-09-15 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14  7:52 [Buildroot] [PATCH] utils/getdeveloperlib.py: fix regexp used to find package infra Thomas Petazzoni via buildroot
2026-09-15 17:11 ` Julien Olivain via buildroot [this message]
2026-09-25 14:44 ` Raphaël Mélotte via buildroot

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=6ae8acf63efea3c90d2b3c01a47767a2@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox