Closed Bug 384287 Opened 15 years ago Closed 15 years ago

SeaMonkey 1.1.2 installer uses wrong XPI URL

Categories

(SeaMonkey :: Installer, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: morrispeckham, Assigned: kairo)

References

()

Details

User-Agent:       Opera/9.21 (Windows NT 5.0; U; en)
Build Identifier: 1.1.2.2007050918

Running the SeaMonkey installer, seamonkey-1.1.2.en-US.win32.stub-installer.exe, the downloader stays at 0% and shows the message "Too many network errors trying to download xpcom.xpi."

My proxy log shows that it is making 22 attempts to get http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/1.1.2/2007-05-09-18-seamonkey1.1-release/windows-xpi/xpcom.xpi but this URL gives a 404 error.

I think the correct URL might be http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/1.1.2/windows-xpi/xpcom.xpi

Reproducible: Always

Steps to Reproduce:
1. Download Windows "Net installer" seamonkey-1.1.2.en-US.win32.stub-installer.exe
2. Run
Actual Results:  
Nothing downloaded, install fails

Expected Results:  
Selected components downloaded, install runs
Indeed:
Identifier0=Site0
;*** LOCALIZE ME BABY ***
Description0=Default
;*** LOCALIZE ME BABY ***
Domain0=http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/1.1.2/2007-05-09-18-seamonkey1.1-release/windows-xpi
[...]
; This key is used as a fail over key.  This url will be used when the
; url in the Site Selector fails.
url=http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/1.1.2/2007-05-09-18-seamonkey1.1-release/windows-xpi
Status: UNCONFIRMED → NEW
Ever confirmed: true
Ouch, perhaps my tinderbox patches have been knocked off again :(

I'll look into this.
Status: NEW → ASSIGNED
Assignee: nobody → kairo
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
FIXED. Sorry it took so long. I'll try to get correct URLs into stub installer the next time.

I'm so glad that we get rid of this for SeaMonkey 2...
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.