Closed Bug 216164 Opened 22 years ago Closed 22 years ago

Once again corrupted XPCOM.XPI in mozilla-win32-installer-sea.exe on 14th August 2003

Categories

(Core :: XPCOM, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: andrew, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030813 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030813 Install package at mozilla-win32-installer-sea.exe on 14th August 2003 has a corrupted XPCOM.XPI Reproducible: Always Steps to Reproduce: 1. download and install http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-win32-installer-sea.exe 2. 3. Actual Results: corrupted XPCOM.XPI
Why is a corrupted Build an installer problem ? Wait for the next build and try it again ?
Assignee: ssu → general
Component: Installer → Browser-General
QA Contact: bugzilla → general
exe-file tells about corrupt XPCOM.XPI, zip-file can´t be unzipped mozilla-win32-installer-sea.exe 14-Aug-2003 10:37 11.8M mozilla-win32-talkback.zip 14-Aug-2003 10:36 10.5M
Status: UNCONFIRMED → NEW
Ever confirmed: true
Herman: If you confirm it, move it to the correct component ! There are reason to leave it in b-g but that isn't the case for this bug. One corrupt build is no reason to report a bug (wait for the next one).
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5b) Gecko/20030815 BuildID 2003081515 is WORKSFORME, though without talkback. resolving 'WONTFIX', as Aug 14th builds won´t get rebuild Also corrupt, still on the server: MozillaFirebird-win32.zip 14-Aug-2003 09:40 6.8M Maybe corruption has come from Bug 214700 move string into mozilla/xpcom & obsolete out of mozilla/xpcom
Status: NEW → RESOLVED
Closed: 22 years ago
Component: Browser-General → XPCOM
Resolution: --- → WONTFIX
no, a corrupt .zip is not from a patch, it a problem with the file-move to the FTP server or another problem with the .zip process during the buildtime.
You need to log in before you can comment on or make changes to this bug.