From: Markus Volk <f_l_k@t-online.de>
To: Ross Burton <Ross.Burton@arm.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH] dbus: disable ptest if using dbus-broker
Date: Thu, 26 Feb 2026 11:32:07 +0100 [thread overview]
Message-ID: <JLA2BT.T07GFLRURYD21@t-online.de> (raw)
In-Reply-To: <D5BYAT.10AVL7ICWFKN@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On Tue, Feb 24 2026 at 07:53:37 +01:00:00, Markus Volk
<f_l_k@t-online.de> wrote:
> On Mon, Feb 23 2026 at 18:08:09 +00:00:00, Ross Burton
> <Ross.Burton@arm.com> wrote:
>> So the situation is you have an image that uses dbus-broken but as
>> that is just the daemon you also have libdbus
Resend this answer because it was bouncing back
The situation is that I want to use dbus-broker but not additionally
libdbus. dbus-broker.bb adds a runtime dependency on dbus-common and
dbus-tools.
<https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-core/dbus/dbus-broker_37.bb#n38>
Thats why dbus recipe is built despite setting VIRTUAL_RUNTIME_dbus =
"dbus-broker" and because of that we end up with a runtime dependency
on dbus if ptests
is in DISTRO_FEATURES.
<https://git.openembedded.org/openembedded-core/tree/meta/classes-recipe/ptest.bbclass#n26>
That causes an error at do_rootfs, because dbus-broker.bb makes dbus
and dbus-broker mutually exclusive:
<https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-core/dbus/dbus-broker_37.bb#n37>
I dont know, if the dbus tests are meant to be run with dbus-broker but
dbus-broker installs its own ptest. Shouldn't that be sufficient?
[-- Attachment #2: Type: text/html, Size: 1948 bytes --]
prev parent reply other threads:[~2026-02-26 10:32 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
[not found] ` <D5BYAT.10AVL7ICWFKN@t-online.de>
2026-02-26 10:32 ` Markus Volk [this message]
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=JLA2BT.T07GFLRURYD21@t-online.de \
--to=f_l_k@t-online.de \
--cc=Ross.Burton@arm.com \
--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