Closed
Bug 654306
Opened 14 years ago
Closed 14 years ago
[Mac] Major Update Billboard not offered from 3.7a5 thru 4.0b6 Universal builds
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: marcia, Assigned: nthomas)
References
Details
Attachments
(1 file)
67.77 KB,
image/png
|
Details |
Seen while testing Major Update Billboard.
STR:
1. Download ftp://ftp.mozilla.org/pub/firefox/releases/devpreview/1.9.3a5/mac/en-US/
2. Change channel to betatest or releasetest (both tested)
3. Help:Check for Updates
4. I am offered update to Mozilla Developer Preview 4.0 B10
Tested with a clean profile.
Reporter | ||
Comment 1•14 years ago
|
||
Assignee | ||
Comment 2•14 years ago
|
||
Confirmed, investigating.
Assignee: nobody → nrthomas
Status: NEW → ASSIGNED
Priority: -- → P2
Assignee | ||
Comment 3•14 years ago
|
||
So we have used the buildIDs from the mono-arch mac64 builds that we were done for a5 through to b6. Specifcally, the problem arises from bug 628690, in particular:
http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=mozilla/tools/patcher-configs&command=DIFF_FRAMESET&file=moz20-branch-patcher2.cfg&rev1=1.16&rev2=1.17&root=/cvsroot
That config was copied to the one we used for this MU work.
Summary: [Mac] Major Update Billboard not offered from 3.7a5 → [Mac] Major Update Billboard not offered from 3.7a5 thru 4.0b6 Universal builds
Reporter | ||
Comment 4•14 years ago
|
||
I can confirm that if I download a Mac64 build that I do get offered the correct update (although sans the billboard, which is another issue)
Assignee | ||
Comment 6•14 years ago
|
||
This is fixed now. My working notes are at https://wiki.mozilla.org/Releases/Firefox_5.0b1/BuildNotes#Mac_BuildID_issues.
I'll fix the config files on bug 651982.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 7•14 years ago
|
||
I tested downloading Mac32 builds and I do now get the update offer.
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•