зеркало из https://github.com/mozilla/gecko-dev.git
6ab6ebcdf4
The fix in Bug 1577634 only worked for the beta channel as it didn't consider the RC case. There's several situations: * beta without comments --> beta with comments: handled by bug 1577634, but with fallout * beta with comments --> beta with comments: `channel-prefs.js` is identical so we never need to apply any transforms * beta with comments --> rc with comments: the channel changes in `channel-prefs.js` (by design) so we apply transforms * rc with comments --> beta with comments: the channel changes in `channel-prefs.js` (by design) so we apply transforms By moving the channel fixing transforms forward the file will become identical before we need to try the comment transform. The code breaks early in this case. The release/esr case is simpler: * release without comments --> release with comments: handled by comment transform, channel transforms only used for beta tests * release with comments --> release with comments: `channel-prefs.js` already identical, no transforms applied Differential Revision: https://phabricator.services.mozilla.com/D49224 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
common | ||
mar_certs | ||
updates | ||
README.txt | ||
compare-directories.py | ||
final-verification.sh | ||
get-update-xml.sh | ||
replace-updater-certs.py | ||
test-mar-url.sh |
README.txt
Mozilla Build Verification Scripts --- -- Contents -- updates -> AUS and update verification l10n -> l10n vs. en-US verification common -> useful utility scripts -- Update verification -- verify.sh does a low-level check of all advertised MAR files. Expects to have a file named all-locales, but does not (yet) handle platform exceptions, so these should be removed from the locales file. prints errors on both STDOUT and STDIN, the intention is to run the script with STDOUT redirected to an output log. If there is not output on the console and an exit code of 0 then all tests pass; otherwise one or more tests failed. Does the following: 1) download update.xml from AUS for a particular release 2) download the partial and full mar advertised 3) check that the partial and full match the advertised size and sha1sum 4) downloads the latest release, and an older release 5) applies MAR to the older release, and compares the two releases. Step 5 is repeated for both the complete and partial MAR. Expects to have an updates.cfg file, describing all releases to try updating from. - Valid Platforms for AUS - Linux_x86-gcc3 Darwin_Universal-gcc3 Linux_x86-gcc3 WINNT_x86-msvc Darwin_ppc-gcc3