Closed Bug 629048 Opened 10 years ago Closed 10 years ago

Ensure comm-central apps work by |Rename *-*.mac64.dmg to *-*.mac.dmg|

Categories

(SeaMonkey :: Release Engineering, defect, P2)

defect

Tracking

(blocking-seamonkey2.1 -)

RESOLVED FIXED
Tracking Status
blocking-seamonkey2.1 --- -

People

(Reporter: Callek, Assigned: Callek)

References

Details

+++ This bug was initially created as a clone of Bug #600931 +++

Since the new i386/x86_64 universal is our only Mac deliverable now, I think it makes more sense to name it "mac" than "mac64" (mac64 kind of implies 64-only, which isn't the case).
blocking-seamonkey2.1: --- → ?
I think this needs different bugs for all affected build masters, as the changes are there, really.

For SeaMonkey, we need to port the one small misc.py patch to our stance in there, update builbotcustom to current default branch tip and reconfigure. That should be all.
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/ says we already upload *.mac.* binaries, so things mostly work, I guess. What we need to check for SeaMonkey should just be getting those buildbotcustom fixes in.
locale builds are missing on FTP, I guess the repack stuff needs the buildbot fixes to run correctly.
Yeah, buildbotcustom and tools should be updated. Additionally you may want to add pltform=platform here: http://hg.mozilla.org/build/buildbotcustom/file/c1ba98a2f159/misc.py#l1520 (for l10n dep builds).
Depends on: 629856
This should be done by Bug 629856
Is this ready to be resolved, if so could you cancel the blocking request?
Ok, this is not blocking (since its easy to manually fix)

That said the reason we are failing to do l10n side of this, is that the MOZ_PKG_PLATFORM magic done in buildbot checks 'platform', which our factory sets differently (in release builds) than expected:

http://mxr.mozilla.org/build/source/buildbot-configs/seamonkey/release_master.py#336

Specifically we specify %os%-release

Which causes MOZ_PKG_PLATFORM to be overridden.
blocking-seamonkey2.1: ? → -
Actually that last comment is covered by Bug 631864
Blocks: 631864
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.