CVEs and Timing Between Artix Release and Official Release That is not In Arch 08 May 2024, 10:42:23 Lets count timing:Firefox has a bug a bug/expoitSome know because its officially roported (unless its non-disclosure 9months)Time taken to check the bug and fix the hole that is hiding among other bug reportsTime to check your fixTime to release the software:Building it in ArchSyncing/Separate building it in Artixpropagation to mirrorsDownload and installHow long it was?to the above we have to add:Time the one man job of librewolf to release new version (sometimes it happens a week after the official release)Fixed Librewolf is officially released.Times goes by...Time to Artix devs coming back from weekend partying/holiday etc and remember they have to not only sync to Arch.... Artix has outdated Librewolf.As far as I remembered even in old times Ubuntu had "the same day policy" for Firefox.So how does it look in Artix? Just curios. Not trolling.
Re: CVEs and Timing Between Artix Release and Official Release That is not In Arch Reply #1 – 08 May 2024, 15:15:57 Something is very wrong with this post.I stop here before I go into a massive rant and ban you.
Re: CVEs and Timing Between Artix Release and Official Release That is not In Arch Reply #2 – 08 May 2024, 15:54:20 It is true that librewolf (a galaxy package; done purely when the maintainer has time) is behind a version. You can simply look at the diff and see that it's an extremely minor change at best. No need for the CVE FUD.
Re: CVEs and Timing Between Artix Release and Official Release That is not In Arch Reply #3 – 09 May 2024, 19:04:31 Quote from: artrixie – on 08 May 2024, 10:42:23... Artix has outdated Librewolf.If you have ever donated to Artix, please apply for a refund and it'll be issued promptly.