Post B0nj75c1kCIVbefH9s by wolf480pl@mstdn.io
 (DIR) More posts by wolf480pl@mstdn.io
 (DIR) Post #B0nZdPgTecDvaCWLVg by wolf480pl@mstdn.io
       2025-12-01T08:13:09Z
       
       0 likes, 0 repeats
       
       @notthebeenoob question: isn't the whole point of NixOS that you can have multiple versions o dependencies like php? And unless it's exposed to a public network, I don't see why EOL should matter...@darix
       
 (DIR) Post #B0nZsNvSTRbmTOfPhQ by darix@mastodon.social
       2025-12-01T08:15:50Z
       
       0 likes, 0 repeats
       
       @wolf480pl @notthebee i had this discussion a while ago (musescore needed some older Qt6 version) ... it is not as straight forward as it seems to establish a parallel older version of a package. which sounded weird to me tbh.TBH depending on which changes are needed it might really be easier to just backport the  support for newer php and move forward.
       
 (DIR) Post #B0ncdbLMbWZrbfQUJE by wolf480pl@mstdn.io
       2025-12-01T08:46:48Z
       
       0 likes, 0 repeats
       
       @notthebee @darix The idea of downstream backporting is you start doing it when upstream stops doing it.You look at security fixes for 9.x and backport those....is how I imagine it works.And I imagine it takes a lot of blood, sweat and tears.
       
 (DIR) Post #B0ndIdwBrfdTWaDouG by darix@mastodon.social
       2025-12-01T08:54:12Z
       
       0 likes, 0 repeats
       
       @wolf480pl @notthebee pretty much this. 1. check if the security bug affects 8.12. check if the code saw major changes between 8.1 and 8.x3. backport 8.x patch to 8.1
       
 (DIR) Post #B0ne6rFedbtZIQGowC by wolf480pl@mstdn.io
       2025-12-01T09:03:18Z
       
       0 likes, 0 repeats
       
       @darixoh, latest is 8.5 not 8.x? They make breaking changes on minors? wtf...@notthebee
       
 (DIR) Post #B0nexihd9WPS89Yw0O by wolf480pl@mstdn.io
       2025-12-01T09:12:51Z
       
       0 likes, 0 repeats
       
       @notthebeeDebian totally does the latter.Some distros have a policy against such downstream backporting, or downstream patching I'm general, so I thought @darix was implying this could be done even more downstream (in your personal packages) but idk seems like a lot of work to me...
       
 (DIR) Post #B0nfI9E0FmXWBARfEG by wolf480pl@mstdn.io
       2025-12-01T09:16:32Z
       
       0 likes, 0 repeats
       
       @notthebeewell ok it's not "developing your own fixes", but it is porting fixes from a version supported by upstream to a version unsupported by upstream@darix
       
 (DIR) Post #B0nj75c1kCIVbefH9s by wolf480pl@mstdn.io
       2025-12-01T09:59:22Z
       
       0 likes, 0 repeats
       
       @notthebeeYeah, it's obviously a question of resources. I wonder why @darix thinks it'd be easy in this case...
       
 (DIR) Post #B0nxt3TmNPKAFVZZjM by darix@mastodon.social
       2025-12-01T12:44:54Z
       
       0 likes, 0 repeats
       
       @wolf480pl @notthebee because all other distros do it. And it was my job for the last 20.5 years.