Closed
Bug 828507
Opened 11 years ago
Closed 11 years ago
Firefox 19b1 Beta updates fail to apply
Categories
(Toolkit :: Application Update, defect)
Tracking
()
People
(Reporter: sbadau, Assigned: akeybl)
References
Details
Attachments
(2 files)
Updating to any beta on the "releasetest" and "betatest" channels is failing. Tried to update Firefox 17 beta 6 and Firefox 18 beta 7 to Firefox 19 beta 1. Steps to reproduce: 1. Install an older beta version (e.g. Firefox 17 beta 6 and Firefox 18 beta 7) 2. Change the channel update to "releasetest" or "betatest" 3. Open Firefox 4. Go to Tools menu-> About:Firefox Expected result: The update is downloaded and the Apply updates button can be clicked. Actual results: The update is downloaded but instead of the Apply Update button the following message is displayed: Update failed. Download the latest version.
Reporter | ||
Comment 1•11 years ago
|
||
The update fails only on Windows. Works fine on Ubuntu and Mac.
Comment 2•11 years ago
|
||
Can you set app.update.log to true and paste the entries in the error console that start with AUS?
Comment 3•11 years ago
|
||
Brian, any ideas regarding this?
Here's more detail on the user experience:
1. Set update channel to betatest by editing channel-prefs.js
2. Start Firefox 18.0b6 with a new profile
3. Click the Help menu > About Firefox
> Firefox checks for and finds a partial update to 19.0b1
> Firefox downloads the partial update and attempts to apply it
> Firefox fails to apply it and automatically begins downloading a complete update
> Firefox attempts to apply the complete update
> Firefox fails to apply the complete update and displays "Update fails. Download the latest version" in the About dialog
Comment 6•11 years ago
|
||
Comment on attachment 699915 [details]
Betatest update log
What are the values for ACCEPTED_MAR_CHANNEL_IDS in your update-settings.ini file located in your installation directory?
Comment 7•11 years ago
|
||
Looks like MAR channel is not accepted. Have there been changes to this lately that landed on beta? #define MAR_CHANNEL_MISMATCH_ERROR 22 that's the info info confvars.sh for ACCEPTED_MAR_CHANNEL_IDS is not matching what the MAR offered is which is built from the value of MAR_CHANNEL_ID.
Reporter | ||
Comment 8•11 years ago
|
||
(In reply to Robert Strong [:rstrong] (do not email) from comment #2) > Can you set app.update.log to true and paste the entries in the error > console that start with AUS? You can find those entries in my attachment.
(In reply to Robert Strong [:rstrong] (do not email) from comment #6) > What are the values for ACCEPTED_MAR_CHANNEL_IDS in your update-settings.ini ACCEPTED_MAR_CHANNEL_IDS=firefox-mozilla-beta,firefox-mozilla-release
Comment 10•11 years ago
|
||
Meh... looks like release drivers went ahead with using aurora's confvars.sh eben though bug 818333 was backed out per bug 818333 comment 19 due to the channel not being set except when building the nightly now. http://mxr.mozilla.org/mozilla-beta/source/browser/confvars.sh
Comment 11•11 years ago
|
||
Alex, see the comment #10 above
Comment 12•11 years ago
|
||
I'm escalating this to blocker given we can't release until this is fixed.
Severity: normal → blocker
status-firefox19:
--- → affected
tracking-firefox19:
--- → ?
QA Contact: anthony.s.hughes
Summary: Beta update fails → Firefox 19b1 Beta updates fail to apply
Version: unspecified → 19 Branch
Comment 13•11 years ago
|
||
release was not affected http://mxr.mozilla.org/mozilla-release/source/browser/confvars.sh#43
Assignee | ||
Comment 14•11 years ago
|
||
(In reply to Robert Strong [:rstrong] (do not email) from comment #10) > Meh... looks like release drivers went ahead with using aurora's confvars.sh > eben though bug 818333 was backed out per bug 818333 comment 19 due to the > channel not being set except when building the nightly now. > http://mxr.mozilla.org/mozilla-beta/source/browser/confvars.sh We'd already changed our documentation, and didn't see that bug 818333 was re-opened/unassigned (or get email to that end). This will need to be resolved on both Beta and Aurora, and will sadly require a beta re-spin.
Comment 15•11 years ago
|
||
Damn, thought you were reading bugmail. Perhaps changes to the merge document that rely on bugs should also be tracked in bugzilla and made a dependency of the bug that makes the change to avoid this in the future.
Comment 16•11 years ago
|
||
Ya seen the same as Comment 10 by inspecting the .mar file.
Assignee | ||
Comment 17•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/490cf7177128 https://hg.mozilla.org/releases/mozilla-beta/rev/a35a73b033a8 We're going to re-spin FF19.0b1 now.
status-firefox20:
--- → fixed
Comment 18•11 years ago
|
||
Marking this resolved fixed based on comment 17.
Reporter | ||
Comment 19•11 years ago
|
||
Mozilla/5.0 (Windows NT 6.2; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0 Build ID: 20130108132750 On the "betatest" channel the updates are properly done - the updates were done from Firefox 17 beta 6 and Firefox 18 beta 7 - on Windows XP, Windows 7, Windows 8, Ubuntu 12.10 and Mac OS X 10.7. But Firefox 19b1 Beta updates still fail to apply on the "releasetest" channel (Firefox behaves as described in Comment 5). Is this expected in any way?
Reporter | ||
Comment 20•11 years ago
|
||
Reopening this bug based on Comment 19.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 21•11 years ago
|
||
(In reply to Simona B [QA] from comment #19) > Firefox 19b1 Beta updates still fail to apply on the "releasetest" This was because Firefox 19.0b1#2 builds were pushed to releasetest before spun 19.0b1#3. These updates have now been purged via bug 829038. Calling this resolved fixed and will verify via automation.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Depends on: 829038
Resolution: --- → FIXED
Comment 22•11 years ago
|
||
(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #21) > Calling this resolved fixed and will verify via automation. Sorry, I forgot to update this bug. Updates have been working correctly for a while now.
Status: RESOLVED → VERIFIED
Keywords: verifyme
You need to log in
before you can comment on or make changes to this bug.
Description
•