Closed Bug 312038 Opened 20 years ago Closed 20 years ago

Get Updates produces rollback

Categories

(Toolkit :: Application Update, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: peng.thinkblue, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051003 Firefox/1.4.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051003 Firefox/1.4.1 When running any nightly branch build after 20051003 you get an "update" to 2005100307. Also, when the update is complete Software Updates pops up a window that says "The partial Update could not be applied. Firefox will try again by downloading a complete update. Reproducible: Always Steps to Reproduce: 1. Start with any night branch build after 20051003. (Also works with 1.5 Beta 2 when channel-prefs.js is changed from "nightly" to "beta" version.) 2. Select Help | Get Update 3. Allow Firefox to restart after update is downloaded Actual Results: The build is identified as version 2005100307 with a message that the update was not successfully applied Expected Results: The installation should have a build number of at least 20051007, preferably the latest nightly branch build.
I tried to confirm this and could not. Starting from the 2005100307 win32 zip, I was able to traverse this sequence of builds, partial updates unless noted: 0307 -> 0407 -> 0415 (partial failed) -> 0418 -> 0506 (partial failed) -> 0517 -> 0604 There were glitches in the generated updates from 20051003 to 20051005 (bug 311099, there seems to be regenerated update files for most of those builds). You probably have a stale active-updates.xml and updates/0/ from when update was broken, and which aren't removed by an uninstall (bug 311423). I suggest removing the file and directory from the firefox install dir, then trying to update again.
Closing this unless anyone objects.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.