From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adrian Perez de Castro <aperez@igalia.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/wpewebkit: security bump to version 2.36.3
Date: Tue, 31 May 2022 08:54:24 +0200 [thread overview]
Message-ID: <20220531085424.344c46c8@windsurf> (raw)
In-Reply-To: <20220530215627.1441783-1-aperez@igalia.com>
On Tue, 31 May 2022 00:56:27 +0300
Adrian Perez de Castro <aperez@igalia.com> wrote:
> Bugfix release, mostly with build fixes, media playback improvements,
> an important fix for when using threaded rendering, and security patches
> for CVE-2022-26700, CVE-2022-26709, CVE-2022-26717, CVE-2022-26716, and
> CVE-2022-26719.
>
> Release notes:
>
> https://wpewebkit.org/release/wpewebkit-2.36.2.html
> https://wpewebkit.org/release/wpewebkit-2.36.3.html
>
> Accompanying security advisory:
>
> https://wpewebkit.org/security/WSA-2022-0005.html
>
> This also imports a build fix which has not made it into the release.
>
> Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>
> ---
> ...en-cross-building-for-64-bit-ARM-htt.patch | 32 +++++++++++++++++++
> package/wpewebkit/wpewebkit.hash | 8 ++---
> package/wpewebkit/wpewebkit.mk | 2 +-
> 3 files changed, 37 insertions(+), 5 deletions(-)
> create mode 100644 package/wpewebkit/0001-Build-failure-when-cross-building-for-64-bit-ARM-htt.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, 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:[~2022-05-31 6:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 21:56 [Buildroot] [PATCH 1/1] package/wpewebkit: security bump to version 2.36.3 Adrian Perez de Castro
2022-05-31 6:54 ` Thomas Petazzoni via buildroot [this message]
2022-06-07 12:16 ` Peter Korsgaard
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=20220531085424.344c46c8@windsurf \
--to=buildroot@buildroot.org \
--cc=aperez@igalia.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