From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: "Alexis Lothoré" <alexis.lothore@bootlin.com>,
buildroot@buildroot.org,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2] package/openscap: bump to version 1.4.3
Date: Fri, 03 Apr 2026 20:03:09 +0200 [thread overview]
Message-ID: <23497d25f46611f800f019eebbad6ca3@free.fr> (raw)
In-Reply-To: <6b1475adada2414a1bdf9321c4352be6@free.fr>
On 03/04/2026 19:56, Julien Olivain via buildroot wrote:
> On 03/04/2026 14:38, Alexis Lothoré via buildroot wrote:
>> The custom patch to enforce project as C project has been merged
>> upstream
>> since then, but it is not released yet. This commit updates the patch
>> to
>> apply it on top of 1.4.3, and use the opportunity to fix the patch
>> file
>> name to match the commit title.
>>
>> Since version 1.4.0, openscap depends on PCRE2 rather than PCRE
>>
>> https://github.com/OpenSCAP/openscap/compare/1.3.12...1.4.3
>>
>> Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
>
> Applied to master, thanks. For info, I removed the
> "select BR2_PACKAGE_PCRE_UTF" in Config.in, which was generating a
> Kconfig warning. This completes the switch to pcre2. See:
> https://gitlab.com/buildroot.org/buildroot/-/commit/ce8f905bac2184bdfc466b072d2e5cc5bbd1e149
For info, I applied the v1 of the patch. Sorry about that.
> Best regards,
>
> Julien.
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-04-03 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 12:38 [Buildroot] [PATCH v2] package/openscap: bump to version 1.4.3 Alexis Lothoré via buildroot
2026-04-03 17:56 ` Julien Olivain via buildroot
2026-04-03 18:03 ` Julien Olivain via buildroot [this message]
2026-04-03 18:11 ` 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=23497d25f46611f800f019eebbad6ca3@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