| 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. |
| | 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. |
| | 12 | |
| | 13 | 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 :-) |
| 25 | | == Problems with 91.0 failing to build == |
| 26 | | |
| 27 | | On a couple of systems (one fairly recent, one BLFS-10. with necessary updates) 91.0 failed to build - a python test on libgkrust.a reported |
| 28 | | {{{ |
| 29 | | TEST-UNEXPECTED-FAIL | check_networking | libgkrust.a | |
| 30 | | Identified 1 networking function(s) being imported in the rust static library (getsockname) |
| 31 | | }}} |
| 32 | | |
| 33 | | This happened with both clang and gcc. |
| 34 | | |
| 35 | | There is now a patch in BLFS which fixes that problem. |
| 36 | | |
| 37 | | |
| 38 | | == Dependencies for 91.0esr series == |
| | 27 | == Dependencies for 91esr series == |
| 50 | | rustc needs to be >= 1.47 but you should use at least 1.52.0 to fix possible vulnerabilities. If using openssl-3, use 1.56.1 with the sedto pick up newer 'cargo' and 'cargo-sys' crates. |
| | 39 | rustc needs to be >= 1.47 but you should use at least 1.58.1. |
| | 40 | |
| | 41 | |
| | 42 | == Dependencies for 102esr series == |
| | 43 | |
| | 44 | cbindgen needs to be >= 0.23 |
| | 45 | |
| | 46 | icu needs to be >= 71.1 |
| | 47 | |
| | 48 | Firefox continues to test for node.js >= v10.23.1 which has not been maintained for a long time. If you have updated node.js to fix each reported vulnerability you should be (I think v16.14.2 was the last vulnerability fix). If not, update to the current version. |
| | 49 | |
| | 50 | libvpx should be v1.11.0. |
| | 51 | |
| | 52 | nspr needs to be >= 4.34 |
| | 53 | |
| | 54 | nss needs to be >= 3.79 |
| | 55 | |
| | 56 | rustc needs to be >= 1.59.0, tested with 1.60.0. |
| | 57 | |
| | 58 | The environment variable MACH_USE_SYSTEM_PYTHON has been deprecated since firefox-100.0, replace it by MACH_BUILD_PYTHON_NATIVE_PACKAGE_SOURCE=system. |
| | 59 | |
| | 60 | See below re 'sandboxing' for how to disable wasi-sysroot, or where to look if you wish to use it. |
| | 61 | |
| | 62 | New Themes (Tools -> Add-Ons and Themes) can make it easier to see which tab is active. |
| 63 | | cbindgen needs to be >= 0.23.0 |
| 64 | | |
| 65 | | icu should now be >= 71.1 |
| 66 | | |
| 67 | | The shipped libpng is now apparently automatically updated (reviewing |
| 68 | | changes would mean using mercurial). But upstream libpng has not been updated for some time. Similar automatic updates are now in place for libwebp, which presumably means the version should be 1.2.2. However, looking at the python configury files, it is possible that much earlier versions of these might work. For consistency, best to keep up to date. |
| 69 | | |
| 70 | | The shipped libvpx has been updated to v1.11.0, updating the system version to that is recommended. |
| 71 | | |
| 72 | | nss shipped version is 3.78.1 which is a security update. The same fixes are in nss-3.79. |
| 73 | | |
| 74 | | rustc now needs to be >= 1.59.0, tested with 1.60.0. |
| 75 | | |
| 76 | | other minimum versions unchanged |
