public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: yoann.congal@smile.fr, martin.jansa@gmail.com
Cc: Yocto ML <yocto@lists.yoctoproject.org>,
	OE-core ML <openembedded-core@lists.openembedded.org>,
	bitbake ML <bitbake-devel@lists.openembedded.org>
Subject: Re: [OE-core] [bitbake-devel] End of whinlatter stable support
Date: Tue, 7 Apr 2026 15:53:51 +0200	[thread overview]
Message-ID: <7e6015d3-bb8c-4267-a7b1-2d79091f108d@gmail.com> (raw)
In-Reply-To: <CA+chaQdp8E_HMyo6Qx6C+PuRrLbrqgbFdQF_WdbZS1ONncxb3w@mail.gmail.com>

2026. 04. 03. 11:14 keltezéssel, Martin Jansa via lists.openembedded.org írta:
> On Fri, Apr 3, 2026 at 10:46 AM Yoann Congal via
> lists.openembedded.org <yoann.congal=smile.fr@lists.openembedded.org>
> wrote:
>> Hello everyone,
>>
>> As you may have noticed, the end-of-life date of whinlatter (2.16 for
>> bitbake) is near.
>> The last release of whinlatter will be the 5.3.4 and will be built in
>> the week of the 20th of april 2026 for a release the week of the 6th of may.
>>
>> If you have patches that you want to see merged in this last version,
>> please send them before the 10th (next week) so we get enough time for
>> review and testing.
> I would like to see my glibc-2.43 compatibility changes I've sent last
> week merged.
>
> I've tested it on 26.04 in docker, if it doesn't show any issue on
> other hosts used by AB, then what's the harm of merging them to
> whinlatter and scarthgap?

That series is indeed needed for whinlatter in my testing on
Fedora 44 (post-beta, practically final), plus the other series
I just sent that fixes binutils-native and gcc-cross.

Unfurtunately, pseudo would need another fix to work on
Fedora 44 as is, see my mail at
https://lists.openembedded.org/g/openembedded-core/message/234730

For now, I can't build neither whinlatter, nor current master
on Fedora 44 due to the pseudo issue.

> Even after whinlatter gets EOL someone might use latest ubuntu release
> on host and then try to compare his wrynose build (where 26.04 works
> fine) with whinlatter build (which fails immediately without these
> changes). I often use EOL OE releases when trying to "bisect" what
> changed in upstream layers e.g. between scarthgap and wrynose.
>
> Cheers,
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#234574): https://lists.openembedded.org/g/openembedded-core/message/234574
> Mute This Topic: https://lists.openembedded.org/mt/118647081/3617728
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [zboszor@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>



      reply	other threads:[~2026-04-07 13:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03  8:46 End of whinlatter stable support yoann.congal
2026-04-03  9:14 ` [bitbake-devel] " Martin Jansa
2026-04-07 13:53   ` Böszörményi Zoltán [this message]

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=7e6015d3-bb8c-4267-a7b1-2d79091f108d@gmail.com \
    --to=zboszor@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yoann.congal@smile.fr \
    --cc=yocto@lists.yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox