End of whinlatter stable support
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.
Best regards,
Signature · 2 lines
Yoann Congal Smile ECS
Quoted 11 lines · Yoann Congal via lists.openembedded.org
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?
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,
2026. 04. 03. 11:14 keltezéssel, Martin Jansa via lists.openembedded.org írta:
Quoted 13 lines
Quoted 10 lines · Yoann Congal via lists.openembedded.org
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.
Quoted 6 lines
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.
Quoted 16 lines
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: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-