Closed Bug 148618 Opened 22 years ago Closed 22 years ago

The installation package is corrupt

Categories

(SeaMonkey :: Installer, defect)

x86
Windows 98
defect
Not set
blocker

Tracking

(Not tracked)

CLOSED WORKSFORME

People

(Reporter: bugzilla, Assigned: dveditz)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0+) Gecko/20020601
BuildID:    20020602

Something is wrong with the full installtion package wor win32 on the latest
builds site. It's just around 7 Mb instead of usual 10, and when I download and
run it, it crashes.


Reproducible: Always
Steps to Reproduce:
1. Download the exe file (see URL above)
2. Run the downloaded file
3. See the usual "Program has performed an illegal operation" window.

Actual Results:  Installer crashes

Expected Results:  Installer should work

It worked fine on May, 31st, but remains broken June, 1st and 2nd.
True, we had this already on Friday.

pi
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 148400 has been marked as a duplicate of this bug. ***
Tried the same file in WinXP. After downloading, I get a window saying, "This is
not a valid win32 application".
same problem with linux talkback tarball, talkback enabled package is even
smaller than the one without
Sorry, the size thing I said is not correct *d'oh*
it seems that mozilla-i686-pc-linux-gnu-installer.tar.gz is also corrupted (2 June).

i have also experienced this bug across various nightly builds for
mozilla-i686-pc-linux-gnu-installer.tar.gz.  i worked around by downloading the
-sea package instead.
Likewise, the non-installer linux .tar.gz files have been corrupt for roughly
two days (I downloaded it once ~18 hours ago and again about 5 hours ago and
gzip hated both of them ("unexpected EOF" error).  This isn't quite what this
bug covers, but I suspect they are related somehow.
Is just got
ftp://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-win32-installer-sea.exe
from the server, it installed just fine.

pi
Yep, now it works fine. Should we close the bug, or would it make sense to
investigate further and figure out what happened on Jun 1st and 2nd?
The sources compile under Linux. Let's bring this to an end.

pi
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
v
Status: RESOLVED → VERIFIED
Let's consider it a temporary glitch in compilation/upload system.
Closing.
Status: VERIFIED → CLOSED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.