Make update specific changes necessary for channel-prefs.js to be removed on macOS
Categories
(Toolkit :: Application Update, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox125 | --- | fixed |
People
(Reporter: bytesized, Assigned: bytesized)
References
Details
(Whiteboard: [fidedi-ope])
Attachments
(8 files, 1 obsolete file)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
There are a number of update-specific things that need to be changed in order to get rid of channel-prefs.js
on macOS, as we are doing in Bug 1799332. I plan to write the necessary code here and mark the patches as being dependent on the patches for that bug to make it easy to land all the code at the same time.
This is likely not comprehensive, but here are the changes that I currently know of that need to be made:
- I believe that this test ought to be removed.
- I think that we want this to not be present on macOS. I'm not entirely sure what the best way to do that is. Maybe remove it and add it back in if we aren't on macOS?
- Currently, when we build MAR files, we have special handling for
channel-prefs.js
such that that file will be added to the installation only if it doesn't already exist. This mechanism should be removed on macOS and, I suspect, changed to handle the new mechanism added in D184711.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Pushed by rsteuber@mozilla.com:
https://hg.mozilla.org/projects/pine/rev/1b5ef137cebb
Make update-specific changes for removing channel-prefs on macOS r=nalexander,spohl
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Pushed by rsteuber@mozilla.com:
https://hg.mozilla.org/projects/pine/rev/7cd7ae05dbc9
Make update-specific changes for removing channel-prefs on macOS r=nalexander,spohl
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Pushed by rsteuber@mozilla.com:
https://hg.mozilla.org/projects/pine/rev/7673f4d7ec84
Make update-specific changes for removing channel-prefs on macOS r=nalexander,spohl
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 5•2 years ago
|
||
Assignee | ||
Comment 6•2 years ago
|
||
Comment 10•2 years ago
|
||
Comment 11•2 years ago
|
||
Assignee | ||
Comment 12•2 years ago
|
||
I'm having trouble making progress on the failed: 39
error that I'm getting, as mentioned on Slack. You asked me to needinfo to remind you about it.
Assignee | ||
Comment 13•2 years ago
|
||
Assignee | ||
Comment 14•2 years ago
|
||
Since this file is no longer used on macOS, the tests do not need to copy it into place.
Depends on D198895
Updated•2 years ago
|
Assignee | ||
Comment 15•2 years ago
|
||
Given that (a) it is no longer possible to easily inspect the Update Settings file and (b) it is intentionally possible to swap out Update Settings frameworks, I anticipate that in the future we may want a way to determine what channels the updater will accept. Thus, I think it is a good idea to add an easy way to make the updater output this information.
Depends on D196626
Assignee | ||
Comment 16•2 years ago
|
||
Depends on D198897
Assignee | ||
Comment 17•2 years ago
|
||
Those files are now in a different location and one of them (UpdateSettings) will already exist rather than needing to be created.
A few other changes are also made here:
- Currently, when we need to make changes to a gTestFiles entry, we access it by index, which is both unreadable (how is anyone supposed to know what gTestFiles[13] refers to?) and a maintenance nightmare (adding an item to the list in the wrong position potentially screws up all the indicies and now a bunch of the tests are making changes to the wrong gTestFiles entry). To improve this, I added
getTestFileByName
so that, for example,gTestFiles[gTestFiles.length - 1]
can be replaced withgetTestFileByName(FILE_CHANNEL_PREFS)
. - Two extra (optional) properties added to gTestFiles entries:
existingFile
andremoveOriginalFile
.existingFile == true
indicates that the file exists already and doesn't need to be created.removeOriginalFile
is only relevant ifexistingFile == true
, and it causes the file to be removed rather than retained. IfexistingFile && !removeOriginalFile
,compareContents
will be automatically set to the current file contents if it (andcompareFile
) is unset, as willcomparePerms
to ensure that the update process doesn't change the file. setUpdateSettingsUseWrongChannel
was added to make it easier to set the wrong update channel either via the INI file (on non-Mac) or via the Framework (on Mac).
Depends on D198898
Assignee | ||
Comment 18•2 years ago
|
||
Depends on D198899
Assignee | ||
Comment 19•2 years ago
|
||
Depends on D198900
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Updated•1 years ago
|
Comment 20•1 years ago
|
||
Comment 21•1 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/62ab286ed401
https://hg.mozilla.org/mozilla-central/rev/d711a830a93e
https://hg.mozilla.org/mozilla-central/rev/f81e80cf062f
https://hg.mozilla.org/mozilla-central/rev/ff5f23856542
https://hg.mozilla.org/mozilla-central/rev/2f4044201b9a
https://hg.mozilla.org/mozilla-central/rev/672c3f18cb8b
https://hg.mozilla.org/mozilla-central/rev/5c6748ef5865
https://hg.mozilla.org/mozilla-central/rev/c676fc5d89bc
Updated•1 year ago
|
Description
•