#Download seamonkey 2.49.1 404 update

Used zipcopy.sh as documented in 2.0b1 notes to move the Windows zips into the directory we want them in for release. 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).

#Download seamonkey 2.49.1 404 update

Update Verification broke due to path issues in verify.sh.patcher paths using nightly when all of the candidates are using candidates/.

L10n verification is mostly useless, since we have lots of expected changed strings.

_l10n_verify and updates started automatically, triggered by the fake-signing.

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.

All references to steps were done directly on my system using modified(to use S3) scripts from the old server.

when the build finished, I triggered the osx repacks.įrom 2.46 onwards, was decomissioned.

fixed the gecko-versions.json to use 51 gecko and retriggered but failed due to the changes table missing a few Csets (I think they were purged).

OSX64 build was busted due to the buildsymbols using a non-universal build format(even if it was built with a universal mozconfig).

Win32 and Linux* builds and repacks were ok.

Updated buildbot-configs for l10n and configsīin/buildbot sendchange -username=ewong -master=localhost:9010 -branch=releases/comm-esr52 -c 'SeaMonkey 2.49.1build1' 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) except for sv-SE which used (d9a857496db2). Venkman is no longer included in the release.

THUNDERBIRD_52_VERBRANCH dom-inspector SEA2_37_RELBRANCH SEAMONKEY_2_49_ESR_RELBRANCH releases/mozilla-esr52 ec540cbe2082