From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/openscap: fix build failure with dbus and musl
Date: Mon, 31 Aug 2026 10:03:03 +0200 [thread overview]
Message-ID: <DL2Z0LY54M31.2D5J3ISTOPNK5@bootlin.com> (raw)
In-Reply-To: <apNMFCS2K3W1coCX@windsurf>
On Sat Aug 29, 2026 at 11:16 PM CEST, Thomas Petazzoni wrote:
> On Fri, Aug 14, 2026 at 02:06:13PM +0200, Alexis Lothoré via buildroot wrote:
>
>> Fixes: https://autobuild.buildroot.org/results/a874d4f34d36fa9f8566be90ad2d5facb99aec24/
>> Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
>> ---
>> The issue affects master, 2026.05.x and 2025.02.x
>
> Wait, how can this issue affects 2025.02.x, since openscap first
> appeared in 2026.02 ?
Ah, good catch, I forgot that that the 2025.02 tree on which I was
working had Openscap because I manually backported the patches
introducing it. Too much coupling between my different BR series, my bad
!
Alexis
> Thomas
--
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-08-31 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 12:06 [Buildroot] [PATCH] package/openscap: fix build failure with dbus and musl Alexis Lothoré via buildroot
2026-08-29 21:14 ` Thomas Petazzoni via buildroot
2026-08-29 21:16 ` Thomas Petazzoni via buildroot
2026-08-31 8:03 ` Alexis Lothoré via buildroot [this message]
2026-09-02 7:34 ` Alexis Lothoré 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=DL2Z0LY54M31.2D5J3ISTOPNK5@bootlin.com \
--to=buildroot@buildroot.org \
--cc=alexis.lothore@bootlin.com \
--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