Bug 41577: Disable profile migration
Merge Info
Related Issues
Backport Timeline
-
Immediate - patchsets for critical bug fixes or other major blocker (e.g. fixes for a 0-day exploit) OR patchsets with trivial changes which do not need testing (e.g. fixes for typos or fixes easily verified in a local developer build) -
Next Minor Stable Release - patchset that needs to be verified in nightly before backport -
Eventually - patchset that needs to be verified in alpha before backport -
No Backport - patchset for the next major stable
Upstream Merging
-
Merge to base-browser- typically for!fixupsto patches in thebase-browserbranch, though sometimes new patches as well- NOTE: I should probably create a separate MR, because the changed file contains Tor Browser's stuff.
Issue Tracking
-
Link resolved issues with appropriate Release Prep issue for changelog generation
Change Description
We disable the profile migration on macOS with an override.ini.
We could disable directly in the browser with MOZ_PROFILE_MIGRATOR=0.
I believe we do that only on macOS because we ship a default profile in other platforms, but if everything goes as I expect, we won't anymore on base browser.
Edited by Pier Angelo Vendrame