Closed
Bug 789529
Opened 12 years ago
Closed 12 years ago
Updater tests can't find channel-prefs.js
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
FIXED
Firefox 20
People
(Reporter: jimm, Assigned: jimm)
References
Details
(Whiteboard: completed-elm)
Attachments
(2 files, 1 obsolete file)
904 bytes,
patch
|
glandium
:
review+
|
Details | Diff | Splinter Review |
1.50 KB,
patch
|
Details | Diff | Splinter Review |
channel-prefs.js ends up in:
dist/bin/browser/defaults/pref/channel-prefs.js
which isn't found by update tests.
Moving it to 'preferences' solves the problem. But based on the comments in bug 756325 maybe that's not the right fix.
cc'ing a few people.
Assignee | ||
Comment 1•12 years ago
|
||
The code in the app makefile was updated to:
ifndef LIBXUL_SDK
# channel-prefs.js is handled separate from other prefs due to bug 756325
libs:: $(srcdir)/profile/channel-prefs.js
$(NSINSTALL) -D $(FINAL_TARGET)/defaults/pref
$(PYTHON) $(topsrcdir)/config/Preprocessor.py $(PREF_PPFLAGS) $(ACDEFINES) $^ > $(FINAL_TARGET)/defaults/pref/channel-prefs.js
endif
FINAL_TARGET points to the browser sub dir.
Assignee | ||
Comment 2•12 years ago
|
||
Moving this file back down to dist/bin also solves the problem. It also lets both browser share the same channel-pref file, so maybe that's the right fix?
Comment 3•12 years ago
|
||
This is filed as Win7 but isn't this a Win8 bug?
The channel-prefs.js needs to end up in the defaults/pref directory that is read by the app per bug 756325.
Nick, I'm still tempted to get rid of channel-prefs.js entirely and go with allowing QA to provide an override other than the channel-prefs.js file. If you ever need to change the channel that would still be possible when updating.
Comment 4•12 years ago
|
||
(In reply to Jim Mathies [:jimm] from comment #2)
> Moving this file back down to dist/bin also solves the problem. It also lets
> both browser share the same channel-pref file, so maybe that's the right fix?
I think that is the better way to go for now. If nothing else, they are the same install and there shouldn't be the possibility of having two different channels based due to two channel-prefs.js files.
Assignee | ||
Comment 5•12 years ago
|
||
(In reply to Robert Strong [:rstrong] (do not email) from comment #3)
> This is filed as Win7 but isn't this a Win8 bug?
This is fall out from the metro-build bug, so once that land on mc this will show up there.
> I think that is the better way to go for now. If nothing else, they are the
> same install and there shouldn't be the possibility of having two different
> channels based due to two channel-prefs.js files.
Ok, I'll land that change on elm to be sure it addresses the update test failures. Will post a patch here as well for Glandium.
Assignee | ||
Comment 6•12 years ago
|
||
This just reverts a single change in the "Move browser application in a subdirectory (PoC)" patch in bug 755724.
Assignee | ||
Comment 7•12 years ago
|
||
revert packager changes as well.
Assignee | ||
Comment 8•12 years ago
|
||
Attachment #659341 -
Attachment is obsolete: true
Assignee | ||
Updated•12 years ago
|
Whiteboard: completed-elm
Assignee | ||
Updated•12 years ago
|
No longer blocks: metro-build
Assignee | ||
Updated•12 years ago
|
Blocks: new-packager
Comment 9•12 years ago
|
||
Comment on attachment 659304 [details] [diff] [review]
patch
This is needed on m-c, as bug 787180 landed there a while ago. This is effectively a noop until FINAL_TARGET != DIST/bin.
Attachment #659304 -
Flags: review+
Updated•12 years ago
|
Assignee: nobody → jmathies
Comment 10•12 years ago
|
||
Comment 11•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 20
You need to log in
before you can comment on or make changes to this bug.
Description
•