Closed Bug 670034 Opened 13 years ago Closed 13 years ago

Make sure Thunderbird tinderboxes have the latest version of NSIS

Categories

(Mozilla Messaging Graveyard :: Release Engineering, defect)

x86
Windows 7
defect
Not set
major

Tracking

(thunderbird6+ fixed, thunderbird7+ fixed)

VERIFIED FIXED
Thunderbird 8
Tracking Status
thunderbird6 + fixed
thunderbird7 + fixed

People

(Reporter: rain1, Assigned: jhopkins)

Details

We currently use NSIS 2.33 on our tinderboxes [1], even though we should be using 2.46. This is probably because of an outdated mozilla-build. We need to update mozilla-build on our tinderboxes ASAP, because this is leading to a broken user experience right now (a dialog box asking if Thunderbird installed correctly, seemingly caused by a somewhat broken manifest embedded by earlier versions of NSIS.)

[1] http://tinderbox.mozilla.org/showlog.cgi?log=ThunderbirdTrunk/1310067063.1310074845.26398.gz&fulltext=1 -- search for makensisu
To update mozilla-build I guess we'll need to reinstall mozmill, etc. (Or wait for bug 656736 to land.)
This should really be fixed for 6.0 - w/o this fixed, people install TB, and Windows tells you TB may not have been installed correctly doesn't really inspire confidence.
Assignee: nobody → jhopkins
Component: Build Config → Release Engineering
Product: Thunderbird → Mozilla Messaging
QA Contact: build-config → release
Version: unspecified → other
@jhopkins - we'll need this done before we do the first beta of 6.
jhopkins set up builds on http://build.mozillamessaging.com/buildbot/try/buildslaves/momo-vm-win2k3-03, but they failed with strange errors. Out of disk space or corrupt filesystem, perhaps?
The push that jhopkins did (build 118) was based on top of some other older pushes to try, which ended up being on top of a changeset from February this year. I certainly wouldn't expect that to build...

Build 119 looks like a failure in what Joshua pushed.
Oh, heh, never mind.
Here's what I did yesterday:

Installed NSIS 2.46 Unicode on one try server build vm.

D:\tmp> nsis-2.46-Unicode-setup.exe /S /D=d:\mozilla-build\nsis-2.46u

Also checked in a PATH env change to our buildbotcustom repo:

 https://hg.mozilla.org/users/gozer_mozillamessaging.com/buildbotcustom-thunderbird-try/

I'm not sure how my try build push got confused... I must've missed some mercurial step.
Fixed try builds are up at https://ftp.mozilla.org/pub/mozilla.org/thunderbird/try-builds/john.hopkins@mozillamessaging.com-10fe6a8d56a5/try-win32/

These builds have the correct manifest, so they work without issues. Looks like the NSIS upgrade worked.
All our win32 builders now have the updated NSIS.

Note to self: Unzip http://momo-thumper.sj.mozillamessaging.com/mirror/mozillamessaging.com/nsis-2.46u.zip in /d/
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 8
I tested with the latest aurora and comm-central builds and verified that they have the correct manifests.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.