Used langpackmove.sh as documented in 2.0b1 notes to move the langpacks into the directory we want them in for release. Changed reference paths in verify.sh and the workdir that verify.sh and the command to call verify.sh finally unhorked the verifications (particularly macos圆4).
#Seamonkey 2.46 release update
Update Verification broke due to path issues in verify.sh.
Update failed due to patcher path issues, but with a bit of magic, Callek unhorked it and it went green.L10n verification is mostly useless, since we have lots of expected changed strings._l10n_verify and updates started automatically, triggered by the fake-signing.No longer needed to send info to metrics. We have no signing infrastructure for SeaMonkey right now, so I faked the signing step that is usually done after completion of builds and L10n repacks and before the update generation.On, modified ~/versions.sh for the current release run.ĭue to the change in our upload/download hosts, the whole update process on stage.mo have been updated. With the plethora of issues, please check the POST-MORTEM part(end of this doc.).Updated buildbot-configs for l10n and configsīin/buildbot sendchange -username=ewong -master=localhost:9010 -branch=releases/comm-release -c "SeaMonkey 2.46build1" doit.Made sure all build machines have clean release directories.L10n revisions according to opt-ins as taken from the sign-off tool (and pushed ship-it). Venkman is no longer included in the release. NB: There was a total of 9 different builds and instead of listing them out here, this is what the (current) final branch of SEA_COMM490_20160927_RELBRANCH looks like:
0 kommentar(er)
