Closed Bug 284702 Opened 20 years ago Closed 18 years ago

Installation of af-ZA language pack failes because of install.rdf is not correct

Categories

(Mozilla Localizations :: Other, defect)

x86
Windows XP
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: twanno, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

When installing the af-ZA (Afrikaans) language pack from
ftp.mozilla.org/pub//mozilla.org/firefox/releases/1.0.1/win32/xpi/, you get the
following error:
The install-<three random characters>.rdf is not wellformed.

Reproducible: Always

Steps to Reproduce:
1.try installing the af-ZA language pack
2.notice the installation error
3.

Actual Results:  
installation fails

Expected Results:  
installation should work.

I noticed that when I removed the first blank line in the install.rdf file
(before the <?xml version="1.0"?> line), the installation worked.
This was with a downloaded copy, installed from the hard drive.

BTW the unmodified downloaded copy did also not install because of the error
Summary: Installation of af-ZA language pack failes because of install.xpi is not correct → Installation of af-ZA language pack failes because of install.rdf is not correct
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 (No
IDN) Firefox/1.4

Confirmed. The supplied fix (removing initial blank line in install.rdf) also
seems to fix this (although I had to bump the maxVersion for it to finish the
install).

Whoever maintains this file (or anyone with privilidges) should just remove the
blank line and repackage this.
This is now not the latest af-ZA build.  This whitespace before XML header was fixed in the Translate Toolkit so we shouldn't see this problem again.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.