Closed Bug 217531 Opened 22 years ago Closed 21 years ago

mozilla .xpi files' install.js has filesize too big

Categories

(SeaMonkey :: Installer, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: phil.pishioneri, Assigned: ajschult784)

References

Details

(Keywords: regression)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Both the network installer and sea tar archive of 1.5b are failing to install for me on Red Hat Linux 7.3 (haven't tried the other). During installation I get a pop-up window with Error[-621]: An Installer module browser.xpi (.xpi) failed to install and the installation fails. In the install.log, I see this: Mozilla Navigator (version 1.5.0.2003082705) ----------------- ** initInstall: 0 ** communicatorFolder: /usr/local/mozilla/active/ ** Insufficient disk space: /usr/local/mozilla/active/ ** required : 163875 K ** available: 63203 K Install **FAILED** with error -235 -- 08/27/2003 22:42:11 Should the browser portion be requiring 162MB of disk space? Reproducible: Always Steps to Reproduce:
worksforme. did you grab the 1.5b binary build from .mozilla.org? I think the installer gets its info on size from config.ini (in the installer directory). What does your config.ini look like for the Navigator component (Install Size=xxxx)? Mine says "25765"
Severity: blocker → normal
Yes, I used the 1.5b binary builds from ftp.mozilla.org: both the installer and sea-tar failed. The config.ini stanzas for Navigator had "Install Size=25765". I just tried the 1.5a installer (had skipped that release), and it has the same problem. I re-installed 1.4 via its installer, and it installed without any problem.
I've found where the required size of 163875 comes from: it's hardcoded in the installation code. The file install.js which is packaged in browser.xpi has this line: var srDest = 163875; and that variable is used in that file's function verifyDiskSpace as the amount (in Kbytes) of free space required. The variable in the 1.4 version of install.js is set to 22987. So there's a discrepancy between the value in config.ini (apparently not actually used by the code) and the one in install.js (which seems abnormally high). If you have about 180 megabytes free in your installation filesystem, you probably don't see this error.
I generated a new browser.xpi with a modified install.js (changed srDest to 30000), and was able to install 1.5b. Total space used in the filesytem by the installation was about 44000 Kbytes, so the value in install.js appears incorrect.
ok, I see that. It looks like it's a problem with all the xpi files (not just browser).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
Summary: 1.5b installer fails on browser.xpi → mozilla .xpi files' install.js has filesize too big
->build
Assignee: ssu → mozbugs-build
Severity: normal → critical
Component: Installer → Build Config
http://lxr.mozilla.org/mozilla/source/xpinstall/packager/unix/makeall.pl#108 108 sub MakeXpiFile 109 { 110 my($componentName) = @_; 111 112 # Make .js file 113 MakeJsFile($componentName); 114 115 # Make .xpi file 116 if(system("perl makexpi.pl $componentName $inStagePath $inDistPath") != 0) 117 { 118 exit(1); 119 } 120 } the JS file is made first and then it's stripped (in makexpi.pl), so the size calculated for the install.js is the size with the libs unstripped.
-> installer
Assignee: mozbugs-build → ssu
Component: Build Config → Installer
Attached patch patchSplinter Review
This moves the call to makejs.pl inside of makexpi.pl (after the libs have been stripped) and fixes the bug for me.
Attachment #131400 - Flags: review?(ssu)
-> me
Assignee: ssu → ajschult
QA Contact: bugzilla → gbush
Any news on this patch?
*** Bug 231116 has been marked as a duplicate of this bug. ***
Attachment #131400 - Flags: review?(ssu0262) → review?(bsmedberg)
*** Bug 231567 has been marked as a duplicate of this bug. ***
*** Bug 218156 has been marked as a duplicate of this bug. ***
No-one has mentioned how to work around this if you're stuck (as I was): xpi files are zip files, so they can be unpacked with info-zip, winzip, jar, etc. and the "install.js" file edited to modify the "srDest" line as described in earlier comments, then pack up back into a zip file with the original name and the installer will work. I had to do browser.xpi and mail.xpi.
(In reply to comment #15) > No-one has mentioned how to work around this if you're stuck (as I was):... As I did: Temporarily free some space on the partition where you are going to installing mozilla by moving stuff somewhere else and back again when the install of mozilla finished. I know not always an option but you asked for work-arounds ;-) AFAIR you need to have 160/180MB of free space when not changing the xpi files.
Flags: blocking1.7a?
Priority: -- → P2
Attachment #131400 - Flags: superreview?(leaf)
Attachment #131400 - Flags: review?(bsmedberg)
Attachment #131400 - Flags: review+
Comment on attachment 131400 [details] [diff] [review] patch sr=leaf (nice one, samir!)
Attachment #131400 - Flags: superreview?(leaf) → superreview+
checked in
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Flags: blocking1.7a?
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: