From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Yoann Congal <yoann.congal@smile.fr>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [whinlatter][PATCH 0/4] gn: upgrade to latest revision
Date: Sat, 21 Mar 2026 15:02:53 +0100 [thread overview]
Message-ID: <8723b2eb-3931-4aaf-a406-e17fd62fa72e@gmail.com> (raw)
In-Reply-To: <DH8CJYGCGVWY.CKRVLGTIY6JG@smile.fr>
2026. 03. 21. 10:19 keltezéssel, Yoann Congal írta:
> On Sat Mar 21, 2026 at 8:36 AM CET, Zoltan Boszormenyi via lists.openembedded.org wrote:
>> The latest revision of gn is needed to build Chromium 145
>> for whinlatter. Nothing else.
>>
>> See https://github.com/OSSystems/meta-browser/pull/963
>>
>> Please merge these into whinlatter.
> Hello,
>
> Sorry but general upgrades like this are not acceptable for stable.
I can keep the gn_git.bbappend in the meta-browser PR.
But then it's not better when every layer shipped their version
before moving it to core.
> Is there a verifiable stability promise from gn upstream that would
> somehow make that acceptable? Note that I'm not familiar with it.
Chromium updates carry a lot of CVE fixes, too.
gn is just a build tool for it and other projects.
next prev parent reply other threads:[~2026-03-21 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 7:36 [whinlatter][PATCH 0/4] gn: upgrade to latest revision Zoltán Böszörményi
2026-03-21 7:36 ` [whinlatter][PATCH 1/4] " Zoltán Böszörményi
2026-03-21 7:36 ` [whinlatter][PATCH 2/4] " Zoltán Böszörményi
2026-03-21 7:36 ` [whinlatter][PATCH 3/4] " Zoltán Böszörményi
2026-03-21 7:36 ` [whinlatter][PATCH 4/4] " Zoltán Böszörményi
2026-03-21 9:19 ` [OE-core] [whinlatter][PATCH 0/4] " Yoann Congal
2026-03-21 14:02 ` Böszörményi Zoltán [this message]
2026-03-21 18:45 ` Yoann Congal
2026-03-22 7:11 ` Böszörményi Zoltán
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=8723b2eb-3931-4aaf-a406-e17fd62fa72e@gmail.com \
--to=zboszor@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yoann.congal@smile.fr \
/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