From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Jack Hill <jackhill@jackhill.us>
Cc: 55078@debbugs.gnu.org, Zhu Zihao <all_but_last@163.com>
Subject: [bug#55078] Acknowledgement ([PATCH]: Update webkitgtk & wpewebkit to 2.36.1.)
Date: Mon, 06 Jun 2022 20:24:26 +0200 [thread overview]
Message-ID: <9dc10afca2f5c7dbab84eecaf501944d73a02bb7.camel@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2206061319430.11587@marsh.hcoop.net>
Am Montag, dem 06.06.2022 um 13:25 -0400 schrieb Jack Hill:
> On Mon, 6 Jun 2022, Liliana Marie Prikler wrote:
>
> > Am Montag, dem 06.06.2022 um 23:53 +0800 schrieb Zhu Zihao:
> > > ping again and again.
> > Last time Raghav reviewed this, they said to base it off of core-
> > updates. Since 2.36.1 has security fixes, we should aim for master
> > instead, but use grafts (we can later ungraft on core-updates or a
> > dedicated branch).
> >
> > Can you resend this as a grafting patch for master?
> >
> > Thanks
>
> Is grafting really needed (I'm not confident I'm not adept enough
> with `git log` to tell for sure if we've done this before)?
Webkit is the base for a bunch of browsers. Most of them are
lightweight compared to webkit itself, but still nasty to recompile.
> I guess technically it should go via staging as `guix refresh -l
> webkitgtk` reports 359 dependent package to rebuild (which and
> additional 75 from webkitgtk-with-libsoup2), but many of those are
> python packages which will presumably be fast rebuilds.
Staging it is, then. (Unless our security team says we should directly
push to master without a graft, which hasn't worked that well for us
last time.)
> Also, WebKitGTK 2.36.3 is out:
> https://webkitgtk.org/2022/05/28/webkitgtk2.36.3-released.html
Yeah, let's do 2.36.3 then.
Cheers
next prev parent reply other threads:[~2022-06-06 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 9:09 [bug#55078] [PATCH]: Update webkitgtk & wpewebkit to 2.36.1 Zhu Zihao
[not found] ` <handler.55078.B.165070504322391.ack@debbugs.gnu.org>
2022-05-01 15:56 ` [bug#55078] Acknowledgement ([PATCH]: Update webkitgtk & wpewebkit to 2.36.1.) Zhu Zihao
2022-05-06 10:47 ` Zhu Zihao
2022-05-09 18:22 ` Jack Hill
2022-06-06 15:53 ` Zhu Zihao
2022-06-06 17:07 ` Liliana Marie Prikler
2022-06-06 17:25 ` Jack Hill
2022-06-06 18:24 ` Liliana Marie Prikler [this message]
2022-06-06 18:27 ` Liliana Marie Prikler
2022-06-14 18:21 ` bug#55078: " Liliana Marie Prikler
2022-05-10 14:47 ` [bug#55078] [PATCH]: Update webkitgtk & wpewebkit to 2.36.1 Raghav Gururajan via Guix-patches via
2022-05-11 4:13 ` Liliana Marie Prikler
2022-05-12 2:53 ` Raghav Gururajan via Guix-patches via
2022-06-04 7:04 ` Liliana Marie Prikler
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=9dc10afca2f5c7dbab84eecaf501944d73a02bb7.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=55078@debbugs.gnu.org \
--cc=all_but_last@163.com \
--cc=jackhill@jackhill.us \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.