Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: buildroot@buildroot.org, Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/openscap: drop duplicate patch
Date: Wed, 02 Sep 2026 21:26:29 +0200	[thread overview]
Message-ID: <956e555ffd8d5ac876e6abd129e1148b@free.fr> (raw)
In-Reply-To: <20260902-revert-openscap-patch-v1-1-f56161b6c7bd@bootlin.com>

On 02/09/2026 10:11, Alexis Lothoré via buildroot wrote:
> Commit bd5b267b1de0 ("package/openscap: fix build failure with dbus and
> musl") brought an upstream patch to fix a build failure on the openscap
> package, detected by the autobuilder on buildroot 2026.02.x, which had
> openscap 1.3.12 at that time. bd5b267b1de0 has recently been merged on
> master; openscap has already been bumped to 1.4.4 on this branch, and 
> so
> it already brings the needed fix for musl+dbus build configurations,
> hence making the patch step fail. This upstream patch is then not 
> needed
> anymore on any maintained branch.
> 
> Fixes: 
> https://autobuild.buildroot.org/results/d11d0b82dcdb4bf10f6c37db8bdbc42a78bdf28b/
> Fixes: 
> https://autobuild.buildroot.org/results/4397a4ef94ccf482f1ab9d24b6334adb0222a580/
> Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>

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

      reply	other threads:[~2026-09-02 19:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02  8:11 [Buildroot] [PATCH] package/openscap: drop duplicate patch Alexis Lothoré via buildroot
2026-09-02 19:26 ` Julien Olivain via buildroot [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=956e555ffd8d5ac876e6abd129e1148b@free.fr \
    --to=buildroot@buildroot.org \
    --cc=alexis.lothore@bootlin.com \
    --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