#FIREFOX ESR 42 UPDATE#
> rushing to latest release, and let the worst bugs / update issues be weeded > AFAIK there are no security issues with 78.15. If not, it'd be a pretty strange coincidence.
#FIREFOX ESR 42 UPGRADE#
Now that I recall, it actually happened with the last ESR major version upgrade too, so it's possible that it's an upstream FF Sync problem, where they drop compatibility for older ESR.
And I don't just mean extensions: history and sometimes bookmarks too.Īlso, some websites stop working properly with older browser versions. I have the same issue with FF 78.15 ESR on Debian (didn't have the time to upgrade to new stable release): it didn't sync properly, now it doesn't sync at all. The problem for me was that syncing and/or extensions stopped working properly and I need / heavily use a container extension which needs to be synced and fully working, so I had to upgrade to 91 non-ESR (which works properly). I only have a few ~unstable packages, none related to Firefox. > Out of curiosity, what were those compatibility issues? Related to mixing (In reply to Joonas Niilola from comment #13) I'm quite happy by not rushing to latest release, and let the worst bugs / update issues be weeded out first. > versions, I think it'd make much more sense to choose the _NEW_ versionĪFAIK there are no security issues with 78.15. > isn't enough manpower / resources to maintain both the old and new ESR > This is absolutely bad for security and honestly makes no sense: if there Out of curiosity, what were those compatibility issues? Related to mixing ~unstable with stable? Yeah we should have this documented, or preferably upstream detect a profile downgrade and start from "scratch" backing up the >ESR profile. This is absolutely bad for security and honestly makes no sense: if there isn't enough manpower / resources to maintain both the old and new ESR versions, I think it'd make much more sense to choose the _NEW_ version instead of the old one. I find myself in the same situation: had to migrate to non-ESR 'cause 78 ESR stopped syncing properly at a certain point, now I'm stuck on 91 non-ESR until its ESR counterpart is released on Gentoo. > What would your recommendation have been? Any other options? > (3) staying with an outdated and vulnerable Firefox 91.0.2 until Gentoo > (2) upgrading to later regular releases which would again mean no ESR, and > (1) downgrading to 78 ESR which would again break things for me, > were removed from the tree, I was left between the following bad choices: > Later, when versions 92 and later were released, and the 91.#.# versions > 91 ESR once that is released, so I masked versions 92 and later.
> and kept up with the regular releases up to version 91, hoping to stay with > Due to compatibility reasons I had to upgrade Firefox 78 ESR to Firefox 86
> Such policies are not good for users who wish to migrate from regular (In reply to Jaak Ristioja from comment #11) Now it's dead: last release is 78.15, released on together with 91.2 ESR. > I don't think there are currently plans on going 91ESR before 78ESR is (In reply to Joonas Niilola from comment #10)
0 kommentar(er)
