On Friday, 8 November 2024, 15:49:11 CET, Alexander Kanavin wrote: _______________________________________________________ Christian Eggers Software Engineer ARRI Arnold & Richter Cine Technik GmbH & Co. Betriebs KG Arriweg 17, 83071 Stephanskirchen www.arri.com
+49 8036 3009-3118 [email protected] Arnold & Richter Cine Technik GmbH & Co. Betriebs KG Sitz: München - Registergericht: Amtsgericht München - Handelsregisternummer: HRA 57918 Persönlich haftender Gesellschafter: Arnold & Richter Cine Technik GmbH Sitz: München - Registergericht: Amtsgericht München - Handelsregisternummer: HRB 54477 Geschäftsführer: Stefan Mairiedl; Walter Trauninger > On Fri, 8 Nov 2024 at 15:39, Christian Eggers <[email protected]> wrote: > > > Hi Alex, > > > > On Friday, 8 November 2024, 11:46:03 CET, Alexander Kanavin wrote: > > > You can do anything you want in your private layers, but in public the > > > options are: > > > - backport the fixes > > > > I tried to backport them, but beside the mentioned merge request I > > need a number of other patches which feels like creating a zombie. > > Due to the complexity I cannot prove whether the result is valid. > > > > Yes. This is the problem with LTS releases 'bugfixes only' policy that > cannot be easily resolved. Do you *have* to use scarthgap, or can you > transition to styhead? Currently we are in the process of making a new release, so switching to a newer OE version is not possible. Switching "only" to a newer Glib release will let me sleep well tonight. > > Would this help other users of Scarthgap? I thought that the mixin > > layers are intended to bring new features to a stable layer. But > > in this case there is a serious bug (race condition in the memory > > management routines) of a major piece of software. Every multi > > threaded application based on Glib is potentially affected. On > > my system it's NetworkManager, but I also read about Firefox. > > > > LTS mixins isn't about new features. It's more about making it possible to > 'opt into' potentially disruptive version upgrades. If such an upgrade > would land in oe-core scarthgap, users would have no choice. With LTS > mixins they have a choice: take the upgrade, or not. If the issues don't > affect them and they don't need new features, not taking the update is a > valid choice. Thanks for the clarification. > > Anyway, you are welcome to prepare such an update for meta-lts-mixins. Cherry picking the commits from Styhead into our private repo was a no brainer, so anybody can do. I only thought about other people who may have the same (almost unfixable) problems with NetworkManager. Providing a mixin wouldn't really help them because probably nobody would look for it in such a case. > > Alex > regards, Christian
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#206888): https://lists.openembedded.org/g/openembedded-core/message/206888 Mute This Topic: https://lists.openembedded.org/mt/109461202/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
