From: Tom Rini <trini@konsulko.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: leon.anavi@konsulko.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [[PATCHv3] meta: Add pam to the defaults if using systemd
Date: Thu, 16 Jul 2026 12:27:37 -0600 [thread overview]
Message-ID: <20260716182737.GP749385@bill-the-cat> (raw)
In-Reply-To: <7e6827804a7b8da37204e54171d8fb9f7b490b35.camel@linuxfoundation.org>
On Thu, Jul 16, 2026 at 12:25:00PM +0100, Richard Purdie wrote:
> On Wed, 2026-07-08 at 17:37 +0300, Leon Anavi via lists.openembedded.org wrote:
> > This fixes issues with test_machine_world when running the
> > yocto-check-layer script for BSP layers that include weston in the
> > dependency chain, for example meta-tegra:
> >
> > ERROR: Required build target 'meta-world-pkgdata' has no buildable
> > providers.
> > Missing or unbuildable dependency chain was: ['meta-world-pkgdata',
> > 'l4t-graphics-demos', 'weston']
>
> Why wouldn't l4t-graphics-demos just list pam as a required distro
> feature for that recipe?
Because it doesn't come from l4t-graphics-demos it comes from weston?
And l4t-graphics-demos supports wayland or x11. Doing something here
would be the not satisfying approach Paul mentioned on v1 or so of this
thread. It shuts yocto-check-layer up while doing nothing of value.
--
Tom
next prev parent reply other threads:[~2026-07-16 18:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 14:37 [[PATCHv3] meta: Add pam to the defaults if using systemd Leon Anavi
2026-07-09 8:45 ` Philipp Zabel
2026-07-13 20:30 ` [OE-core] " Joshua Watt
2026-07-16 10:02 ` Leon Anavi
2026-07-16 10:44 ` Richard Purdie
2026-07-16 11:13 ` Philipp Zabel
2026-07-16 19:10 ` Joshua Watt
2026-07-16 11:25 ` Richard Purdie
2026-07-16 18:27 ` Tom Rini [this message]
2026-07-16 20:28 ` Richard Purdie
2026-07-16 21:17 ` Joshua Watt
2026-07-16 23:20 ` Tom Rini
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=20260716182737.GP749385@bill-the-cat \
--to=trini@konsulko.com \
--cc=leon.anavi@konsulko.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.