Changes between Version 129 and Version 130 of firefox

Timestamp:

07/26/2022 08:07:38 PM (21 months ago)

Author:

ken@…

Comment:

--

firefox

@@ -11 +11 @@
 For 91.0esr, firefox seems to want to create a new profile when coming from 78esr, but using 'firefox -P' allows it to use the existing profile. If you have created redundant profiles, or wish to rename profiles, 'about:profiles' will open the profile manager to permit this.
 
-When upgrading from firefox-91esr to 102esr the profile is automatically upgraded. However, if you have multiple systems on the same machine which share /home (in my case, development and released systems), invoking firefox on another system after one system has been updated, even just starting the profile selector or running firefox --version, is enough to get the profile marked as trashed. Backups of ~/.mozilla are good :-)
+When upgrading from firefox-91esr to 102esr the profile is automatically upgraded. However, if you have multiple systems on the same machine (esr in /usr, latest in /opt) which share /home (in my case, development and released systems), invoking firefox on another system after one system has been updated, even just starting the profile selector or running firefox --version, is enough to get the profile marked as trashed. Backups of ~/.mozilla are good :-) Related issues with upgrading the latest to 103.0 iff I used my (extra) desktop file, except I got 102 instead of 103, with the esr items. Starting from a term and specifying that PATH to the required firefox using -P allowed my to sort tings out. 
  
 == Which version should I use ? ==
@@ -69 +69 @@
 Note that point releases of the current stable versions are not specifically monitored, if you use the current stable version you should check for updates and their release note and any security fixes.
 
-== Dependencies for 102.0 series (latest upstream stable) ==
+== Dependencies for 103.0 series (latest upstream stable) ==
 
-Same as for 102esr.
+cbindgen >= 0.24.3 and therefore the sed needed for 102 is not wanted.
+
+nss >= 3.80.0
+
+It looks as if 103 is updating the profile details.
 
 
@@ -80 +84 @@
 For the moment, g++ can be used if you pass --without-wasm-sandboxed-libraries.
 
-== Dependencies for 103.0beta ==
+== Dependencies for 104.0beta ==
 
-cbindgen >= 0.24.3 and therefore the sed needed in 102 is not needed.
-
-nss >= 3.80.0
+To Be Advised.
 
 The early betas for 92.0 and 93.0 needed static libstdc++.a to link logalloc-replay (that specifies -static-libstdc++). In later betas that was not compiled. While using a static system lib (outside of rust) is annoying, the expected lifetime of a firefox beta is short and this requirement can be remembered if a vulnerability in libstdc++ is ever disclosed. I assume this requirement will continue for early betas (those where EARLY_BETA_OR_EARLIER is defined in build/defines.sh).