![]() We were polling for that product in start_uptake_monitoring, and getting errors which blocked the 'Updates available on releasetest' email. The partial from 24.8.1esr was added at build3, and bouncer submission only happens on build1, so there was no Firefox-31.2.0esr-Partial-24.8.1esr set up. # rm previous version updates (they are not overwritten) rail was confused with one of the emails and pushed the esr snippets earlier than needed.Rm -rf staging/Firefox-31.2.0esr-build3.bak Rsync -a pushed/Firefox-31.2.0esr-build1-test/Firefox/31.0* staging/Firefox-31.2.0esr-build1-test-fixed-whatsnew/Firefox/įind staging/Firefox-31.2.0esr-build1-test-fixed-whatsnew -type f -exec sed -i -e '/^openURL/d' -e 's,^actions=showURL,actions=silent,' \ ĭiff -ru staging/Firefox-31.2.0esr-build3.bak staging/Firefox-31.2.0esr-build3 | less Mkdir -p staging/Firefox-31.2.0esr-build1-test-fixed-whatsnew/Firefox The patcher config has whatsnew turned on for all versions, so we need to post-process the snippets for < 31.0. Bash: scripts/scripts/l10n/release_repacks.sh: No such file or directoryīug 1018694 requests whatsnew pages to be shown for ESR24 users, so they get the Australis tour when updating to an Australis build.
0 Comments
Leave a Reply. |