On 7/15/24 4:37 PM, Felix Miata wrote:
Not so. It's normal for old ESR and new ESR to coexist for about 3 releases: https://ftp.mozilla.org/pub/firefox/releases/128.0esr/linux-x86_64/en-US/fir... 83M 08-Jul-2024 13:44 https://ftp.mozilla.org/pub/firefox/releases/115.13.0esr/linux-x86_64/en-US/... 77M 08-Jul-2024 13:57
Thanks Felix, my bad, Though herein lies that subtle issue that catches people off-guard. The original thread was wondering why mozilla still had 115.11.0 for TW instead of the then-current 115.12.0 (build failure was the reason) So when I saw 115.13.0 in the repo, I logically expected the next update to update 115.11.0 to 115.13.0. I updated and clicked to start firefox and BAM, my profile was irreversibly converted to 128.0.0 format due to the update pulling 128.0.0 instead of 115.13.0 as expected. By naming both 128 and 115 "firefox-esr" at the same time you cause 128 to be pulled in instead of 115 due to how the version-preference work. That's not new, that's just how it works. There is virtually no way for a normal user to prevent having a profile converted unless they find both 115 and 128 in the repo (by physically scrolling though it) and then explicitly passing a version to install and then lock firefox-esr before performing an update. That's a bit of a bridge too far. In my case, I would have much rather continued with 115 through EOL in October to ensure that 128 is fully baked before I move to it. However with the irreversible profile changes, that path is now foreclosed. (unless I pull an old profile over -- most people do not have that option) This was after I did look at the mozilla/Tumbleweed/x86_64 repo and saw 115.13.0, but didn't catch that there was also a 128.0esr. Thankfully 128 hasn't given me any issues yet -- so this wasn't as painful as it could have been. Usually it doesn't matter and a simple "Oops I pulled a version I didn't want, just downgrade" is all it takes. But in cases like this where irreversible changes are made to the user's profile without notice -- there should be some better way to prevent this. Just thinking out loud. -- David C. Rankin, J.D.,P.E.