Closed Bug 457344 Opened 17 years ago Closed 17 years ago

Win98 users doesn't seem to get an offer to update from 2.0.0.16 to 2.0.0.17

Categories

(AUS Graveyard :: General, defect)

x86
Windows 98
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: Matti, Assigned: reed)

References

Details

Attachments

(2 files, 1 obsolete file)

I can not reproduce this myself but someone should look at this if possible. I saw 2 different people on heise.de claiming that they don't get an offer to update from Firefox 2.0.0.16 to 2.0.0.17 under Windoes98 It seems that they also manually tried it but they got the info "no updates available". Is it possible that the update block that should block an update to 3.X under windows98SE also blocks minor updates ?
Assignee: nobody → morgamic
Severity: normal → critical
Component: Release Engineering → General
Depends on: 418129
Product: mozilla.org → AUS
QA Contact: release → general
Version: other → 2.0
Er, not fixed here, yet. Should we just be patient or should the bug be reopened? Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16
Behavior from bug 418129 is only supposed to work with major updates. Is this update a major update?
(In reply to comment #3) > Behavior from bug 418129 is only supposed to work with major updates. Is this > update a major update? AUS and patcher are both broken. Patcher seems to only set the updateType if the update is major, and AUS never sets a default for updateType, so without an updateType for minor updates, this block of code never becomes true, and therefore, platform checking is applied for both major and minor updates: 476 // If it's not a major update, we're not blocking platforms. 477 if ($updateType == 'minor' || empty($unsupportedPlatforms[$product])) { 478 return true; 479 } Quick fix is to make AUS set a default of updateType being minor if it's not set, but really patcher should be setting updateType for all snippets, not just major update ones. I'm working on a patch. Should be posted shortly.
The update class has a default of minor, but it is overridden if patcher offers one.
Attached patch patch - v1Splinter Review
Set updateType to 'minor' by default when initializing a new patch class. Test included. Nothing tested, as I don't have a local AUS instance to use for testing.
Assignee: morgamic → reed
Status: NEW → ASSIGNED
Attachment #340756 - Flags: review?(morgamic)
Attachment #340756 - Flags: review?(morgamic) → review+
Attachment #340757 - Attachment is obsolete: true
Attachment #340758 - Flags: review?(reed)
Attachment #340757 - Flags: review?(reed)
RCS file: /cvsroot/mozilla/webtools/aus/tests/data/3/Synthetic/1.0/platform/8000000004/locale/channel/complete.txt,v done Checking in tests/data/3/Synthetic/1.0/platform/8000000004/locale/channel/complete.txt; /cvsroot/mozilla/webtools/aus/tests/data/3/Synthetic/1.0/platform/8000000004/locale/channel/complete.txt,v <-- complete.txt initial revision: 1.1 done RCS file: /cvsroot/mozilla/webtools/aus/tests/data/3/Synthetic/1.0/platform/8000000004/locale/channel/partial.txt,v done Checking in tests/data/3/Synthetic/1.0/platform/8000000004/locale/channel/partial.txt; /cvsroot/mozilla/webtools/aus/tests/data/3/Synthetic/1.0/platform/8000000004/locale/channel/partial.txt,v <-- partial.txt initial revision: 1.1 done Checking in xml/inc/patch.class.php; /cvsroot/mozilla/webtools/aus/xml/inc/patch.class.php,v <-- patch.class.php new revision: 1.23; previous revision: 1.22 done
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Attachment #340758 - Flags: review?(reed) → review+
Checking in tests/Verify.py; /cvsroot/mozilla/webtools/aus/tests/Verify.py,v <-- Verify.py new revision: 1.7; previous revision: 1.6 done Checking in tests/Verify.txt; /cvsroot/mozilla/webtools/aus/tests/Verify.txt,v <-- Verify.txt new revision: 1.12; previous revision: 1.11 done
Attachment #340758 - Attachment description: Revised tests to cover all ignored OS's with minor update types → Revised tests to cover all ignored OSes with minor update types
https://aus2-staging.mozilla.org has been updated with the new patch. Once QA has looked over it and confirmed that the problem is fixed, we'll get the production AUS2 instance updated. Any help testing would be appreciated!
(In reply to comment #11) > https://aus2-staging.mozilla.org has been updated with the new patch. Once QA > has looked over it and confirmed that the problem is fixed, we'll get the > production AUS2 instance updated. Any help testing would be appreciated! Starting now the Tests - Tomcat
(In reply to comment #12) > Starting now the Tests - Tomcat Tests are done now and tests for Windows (NT and Windows 98) and also Ubuntu 6.06.01 PASS. I'm not really able to test Mac 10.3 I also confirmed working updates on aus2-staging for Windows XP and Mac 10.5 Results are added to https://wiki.mozilla.org/QA/Firefox3/TestPlan/MajorUpdate/Results:20016_fx3.0.1#Retest_for_Bug_457344_-_Tomcat
Bug 457489 filed to get AUS2 production updated.
> I can not reproduce this myself but someone should look at this if possible. > I saw 2 different people on heise.de claiming that they don't get an offer to > update from Firefox 2.0.0.16 to 2.0.0.17 under Windoes98 > It seems that they also manually tried it but they got the info "no updates > available". > > Is it possible that the update block that should block an update to 3.X under > windows98SE also blocks minor updates ? I was able to reproduce this with my dad's old laptop/notebook with Firefox v2.0.0.16 and Windows 98 SE. I had to download and install v2.0.0.17 with its installer.
verified fixed using my windows 98 VM. Update to 2.0.0.17 works like expected now.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: