All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Perez de Castro <aperez@igalia.com>
To: "François Perrad" <francois.perrad@gadz.org>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/wpewebkit: bump to version 2.36.2
Date: Tue, 31 May 2022 01:06:07 +0300	[thread overview]
Message-ID: <20220531010607.GD740429@momiji> (raw)
In-Reply-To: <20220519201219.GB3682468@momiji>


[-- Attachment #1.1: Type: text/plain, Size: 1742 bytes --]

Hello, all,

On Thu, 19 May 2022 20:12:19 +0300 Adrian Perez de Castro <aperez@igalia.com> wrote:
 
> On Thu, 19 May 2022 18:31:30 +0200 François Perrad <francois.perrad@gadz.org> wrote:
> > Le mer. 18 mai 2022 à 16:19, Adrian Perez de Castro <aperez@igalia.com> a
> > écrit :
> > 
> > > Bugfix release, mostly with build fixes, and an important fix for
> > > when using threaded rendering. Release notes:
> > >
> > >   https://wpewebkit.org/release/wpewebkit-2.36.2.html
> > >
> > > This release fails to build when X11 headers are not present, but there
> > > is already a fix accepted upstream and slated for inclusion in the next
> > > release in the series, so in the meantime imported it locally.
> > >
> > >
> > webkitgtk 2.36.1 (from BR 2022.05-rc1) has also this issue.
> > patch from https://bugs.webkit.org/show_bug.cgi?id=239039 solves it.
> 
> I was in the middle of preparing the 2.36.2 update for webkitgtk, which
> would include this patch as well; but then I found a different build
> issue. Then while looking into it Apple published a new list of security
> bugs, which means we need to make a new (which will be 2.36.3) for both
> ports including the fixes... so I have merged the build fix for the X11
> headers in the release branch and we won't even need to import the patch
> in Buildroot.
> 
> FWIW: let's not merge the 2.36.2 update for wpewebkit, because in a few
> days I will send anyway patches to go directly to 2.36.3

Done, here's the updates to 2.36.3 for both wpewebkit and webkitgtk:

  https://patchwork.ozlabs.org/project/buildroot/patch/20220530215627.1441783-1-aperez@igalia.com/
  https://patchwork.ozlabs.org/project/buildroot/patch/20220530220141.1445578-1-aperez@igalia.com/

Cheers,
—Adrián

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-05-30 22:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 14:19 [Buildroot] [PATCH 1/1] package/wpewebkit: bump to version 2.36.2 Adrian Perez de Castro
2022-05-19 16:31 ` François Perrad
2022-05-19 17:12   ` Adrian Perez de Castro
2022-05-24 10:25     ` Michael Nosthoff via buildroot
2022-05-30 22:18       ` Adrian Perez de Castro
2022-05-31  9:14         ` Michael Nosthoff via buildroot
2022-06-01  7:39           ` Adrian Perez de Castro
2022-06-01 14:18             ` Adrian Perez de Castro
2022-06-11  0:06               ` Adrian Perez de Castro
2022-06-11  9:14                 ` André Zwing
2022-05-30 22:06     ` Adrian Perez de Castro [this message]
2022-06-12 18:17 Michael Nosthoff 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=20220531010607.GD740429@momiji \
    --to=aperez@igalia.com \
    --cc=buildroot@buildroot.org \
    --cc=francois.perrad@gadz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.