Closed
Bug 842392
Opened 12 years ago
Closed 12 years ago
Firefox 10.0.12esr update to 17.0.2esr
Categories
(Release Engineering :: Release Requests, defect, P2)
Release Engineering
Release Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: u279076, Assigned: coop)
References
Details
During our automated testing for 10.0.*esr -> 17.0.3esr updates I discovered that only 10.0.12esr is not updating properly. 10.0esr through 10.0.11esr correctly receive updates to 17.0.3esr on esrtest channel. However, 10.0.12esr updates to 17.0.2esr on the same channel. I've spotchecked manually and this is indeed the case. Here is a sample update.xml file:
https://aus3.mozilla.org/update/3/Firefox/10.0.12/20130103094221/Linux_x86_64-gcc3/en-US/esrtest/Linux%203.7.9-1-ARCH%20%28GTK%202.24.15%29/default/default/update.xml
> <update type="minor"
> displayVersion="17.0.2esr"
> appVersion="17.0.2"
> platformVersion="17.0.2"
> buildID="20130107124423"
> detailsURL="https://www.mozilla.com/en-US/firefox/17.0.2/releasenotes/"
> actions="silent">
> <patch type="complete"
> URL="http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/17.0.2esr-candidates/build3/update/linux-x86_64/en-US/firefox-17.0.2esr.complete.mar"
> hashFunction="SHA512"
> hashValue="d0a36f19befb4a786241c7d600682dc5596f28925535d1cab6c6a0d3f2891632ed6c4c885a3bbf40a7f15f094a11780c95a6a5b6c344aa8ab7a9d9e9159dcdbf"
> size="23607901"/>
> </update>
FWIW, I don't think this is necessarily a blocker for release since 10.0.12 users will update 10.0.12esr > 17.0.2esr > 17.0.3esr. That said, if would be better if we can fix this before we release.
Assignee | ||
Comment 1•12 years ago
|
||
This should be fixed now. Please let me know if it is not.
Status: NEW → ASSIGNED
Priority: -- → P2
I re-ran our update automation for 17esr on releasetest. All ESR versions now update correctly to 17.0.3esr. Thank you, Chris.
Status: ASSIGNED → RESOLVED
Closed: 12 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
•