Closed
Bug 417889
Opened 17 years ago
Closed 17 years ago
symbol server key in bootstrap.cfg needs to be platform-specific
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rhelmer, Assigned: rhelmer)
References
Details
Attachments
(1 file)
|
1.69 KB,
patch
|
nthomas
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Attachment #303679 -
Flags: review?(nrthomas)
Comment 1•17 years ago
|
||
Comment on attachment 303679 [details] [diff] [review]
[checked in] platform-specific symbol key location
This is a permanent fix for bug 415913 ? It looks like
mozilla/toolkit/crashreporter/tools/upload_symbols.sh
should handle the spaces for Windows, but watch out for bustage.
Attachment #303679 -
Flags: review?(nrthomas) → review+
Updated•17 years ago
|
Priority: -- → P3
| Assignee | ||
Comment 2•17 years ago
|
||
Comment on attachment 303679 [details] [diff] [review]
[checked in] platform-specific symbol key location
Checking in fx-moz19-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/fx-moz19-bootstrap.cfg,v <-- fx-moz19-bootstrap.cfg
new revision: 1.14; previous revision: 1.13
done
Checking in fx-moz19-staging-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/fx-moz19-staging-bootstrap.cfg,v <-- fx-moz19-staging-bootstrap.cfg
new revision: 1.11; previous revision: 1.10
done
Attachment #303679 -
Attachment description: platform-specific symbol key location → [checked in] platform-specific symbol key location
| Assignee | ||
Comment 3•17 years ago
|
||
(In reply to comment #1)
> (From update of attachment 303679 [details] [diff] [review])
> This is a permanent fix for bug 415913 ? It looks like
> mozilla/toolkit/crashreporter/tools/upload_symbols.sh
> should handle the spaces for Windows, but watch out for bustage.
I'll make sure that the staging run goes ok. Thanks!
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•