Closed
Bug 65269
Opened 24 years ago
Closed 24 years ago
MacOS Trunk builds do not have Talkback enabled.
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jay, Assigned: jj.enser)
Details
Attachments
(1 file)
Sometime between 12/08 and 12/09 Talkback stopped receiving blackboxes from
MacOS users. The datafiles we use to generate Trunk Topcrash and MTBF reports
do not have any MacOS data. We need to get Talkback activated in the Trunk
builds ASAP.
Assignee | ||
Comment 1•24 years ago
|
||
I'm on it.
I detected the problem during the holidays and reported it on 12/28. 2 variables
are used in the mac build scripts to handle fullcircle/talkback related issues.
build{talkback} and MOZ_FULLCIRCLE.
By default the former is defined while the latter is not, but it IS defined in
the local prefs on the release build mac. However, the build behaves as if
MOZ_FULLCIRCLE was not defined.
I will debug further the build process to try and understand why this happens.
Ref: ns/build/mac/build_scripts/NetscapeBuildList.pm, lines 817-835
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•24 years ago
|
||
I have a fix. the problem was caused by the syntax "$dist_dir:TalkBack" in the
build script, where $dist_dist value was already containing a trailing colon, so
there was one too many colon in the path.
to avoid multiple calls to ($dist_dir . "TalkBack"), I added a variable.
see (and review) coming patch.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 3•24 years ago
|
||
Assignee | ||
Comment 4•24 years ago
|
||
Oops I marked this one fixed a little too early. Reopening, and will mark fixed
again after the patch is reviewed and checked in.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 5•24 years ago
|
||
Good catch. sr=sfraser
Assignee | ||
Comment 6•24 years ago
|
||
fix checked in.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•