Closed Bug 458968 Opened 16 years ago Closed 16 years ago

Firefox Mac Beta 1 candidate build is branded "Minefield"

Categories

(Release Engineering :: General, defect, P1)

Product:
Release Engineering
Component:
General
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: marcia, Assigned: nthomas)

References

Details

I have downloaded the build from ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.1b1-candidates/build1/ on two separate Mac machines and it is branded with Minefield instead of Firefox.
Flags: blocking-firefox3.1?
Same happens to me. Adding Ben.
The build has
  ac_add_options --enable-official-branding
so there must be something more subtle going on. Looking.
FWIW, the linux builds have the correct Firefox branding.
Ok, it looks like the wrong file got uploaded to the ftp server. The correct buildID should be 20081007125523, while [1] is 20081007110205, branded Minefield and with version 3.1b1pre.

[1] http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/3.1b1-candidates/build1/mac/en-US/firefox-3.1b1.dmg
Component: Build Config → Release Engineering
Flags: blocking-firefox3.1?
Priority: -- → P1
Product: Firefox → mozilla.org
QA Contact: build.config → release
Version: Trunk → other
I've replaced the build at [1] with the correct dmg. 

The sha1 hashes are
 proper 3.1b1 build - b3e0d0f7c0f4ea7a4de48bd34cec71a9a4f67e03
 accidental nightly - bb5ff9c49cfe05761f507d0884cdbfd965c63a57

You can get a sha1sum on mac by using a terminal to go
  openssl dgst -sha1 <file>
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
QA, please verify.
Assignee: nobody → nthomas
verified fixed - I am testing now and the Build ID is: 20081007125523
Status: RESOLVED → VERIFIED
Thanks, apologies for the glitch.
Status: VERIFIED → RESOLVED
Closed: 16 years ago → 16 years ago
Status: RESOLVED → VERIFIED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.