From: Ross Burton <Ross.Burton@arm.com>
To: "f_l_k@t-online.de" <f_l_k@t-online.de>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe-core][PATCH] dbus: disable ptest if using dbus-broker
Date: Mon, 23 Feb 2026 18:08:09 +0000 [thread overview]
Message-ID: <FB1758B8-BC23-4F97-9C11-DFA240E7FE77@arm.com> (raw)
In-Reply-To: <20260218203844.2846590-1-f_l_k@t-online.de>
On 18 Feb 2026, at 20:38, Markus Volk via lists.openembedded.org <f_l_k=t-online.de@lists.openembedded.org> wrote:
>
> 'inherit ptest' adds a runtime dependency on ${PN} that conflicts with
> 'RCONFLICTS:${PN} = "dbus"' in the dbus-broker recipe.
>
> This commit attempts to fix an issue where VIRTUAL-RUNTIME_dbus is set to
> 'dbus-broker' and ptest is included in DISTRO_FEATURES by installing ptest
> only when dbus is used as the daemon.
So the situation is you have an image that uses dbus-broken but as that is just the daemon you also have libdbus (from dbus.bb), and then using the ptest-pkgs IMAGE_FEATURE you automatically get dbus-ptest installed, which then tries to pull in the dbus daemon. Correct?
It feels like being able to run the dbus tests against dbus-broker would be a good thing. Do you know if this is feasible? I’m wondering if the dependency on a daemon should be some virtual name that dbus and dbus-broken provide.
Cheers,
Ross
next prev parent reply other threads:[~2026-02-23 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 20:38 [oe-core][PATCH] dbus: disable ptest if using dbus-broker Markus Volk
2026-02-23 18:08 ` Ross Burton [this message]
[not found] ` <D5BYAT.10AVL7ICWFKN@t-online.de>
2026-02-26 10:32 ` Markus Volk
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=FB1758B8-BC23-4F97-9C11-DFA240E7FE77@arm.com \
--to=ross.burton@arm.com \
--cc=f_l_k@t-online.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox