Closed Bug 536413 Opened 13 years ago Closed 13 years ago

[WinCE] Not able to update directly to Firefox 3.6 B5 from previous betas

Categories

(Release Engineering :: General, defect)

ARM
Windows CE
defect
Not set
normal

Tracking

(status1.9.2 final-fixed)

RESOLVED FIXED
Tracking Status
status1.9.2 --- final-fixed

People

(Reporter: marcia, Assigned: nthomas)

References

Details

(Whiteboard: [nv][server-side])

Seen while performing update testing on the Firefox 3.6 Beta 5. This is using the 2009-12-04 OS drop.

STR:

Machine 1:

1. Fresh Factory Reset with Machine 1 - Beta 2 installed by default.
2. Check for updates -> I receive an update offer for B3 instead of B5

Machine 2:

1. Fresh Factory Reset. Rename the Firefox directory (in this OS drop there is no way to uninstall Firefox). Even though the directory has been renamed, when I run the cab file it still recognizes that Firefox is installed on the machine so it is more a pave over install.
2. Install the Beta 3 from the releases directory.
3. Check for updates - I am offered the update to B4 instead of B5.
The snippets were generated incorrectly in bug 532755 (attachment 418216 [details])
Blocks: 532755
Component: General → Release Engineering
Product: Firefox → mozilla.org
QA Contact: general → release
Version: 3.6 Branch → other
Can we fix this at 3.6rc1 or do we need to do it before then ?
Flags: blocking1.9.2?
(In reply to comment #1)
> The snippets were generated incorrectly ...

In particular the following lines were missing:
        past-update   3.6b2 3.6b3 betatest releasetest beta
        past-update   3.6b3 3.6b4 betatest releasetest beta

The update path from b2 -> b3 -> b4 -> b5, tortuous though it is, does exist so lets fix it up when we build 3.6rc1.
Blocks: 535567
No longer blocks: 532755
Is there a direct update path from b2 -> b5 or will there be from b2 -> rc? I believe that we expect devices to ship with b2, that right, dolske?
Flags: blocking1.9.2? → blocking1.9.2+
Whiteboard: [nv] → [nv][server-side]
I'm not sure of their shipping schedule; my impression was they haven't shipped yet, so the first devices should have an OS build with a newer Firefox. I think the last OS build we got had beta 4, as I was able to update it to Beta 5 earlier today with no problem.
Summary: [WinCE] Not able to update to Firefox 3.6 B5 from previous betas → [WinCE] Not able to update directly to Firefox 3.6 B5 from previous betas
Fixed by the better patcher config in bug 535567 (attachment 420483 [details] [diff] [review]).
Assignee: nobody → nrthomas
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.