X-Spam-Check-By: sourceware.org
Message-ID: <43D6ED0D.71274F0@dessent.net>
Date: Tue, 24 Jan 2006 19:14:21 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin Setup: Fatal Error: Uncaught Exception
References: <43D467F0 DOT 4020706 AT tlinx DOT org> <43D46B88 DOT FD612AE AT dessent DOT net> <20060123112502 DOT GB2188 AT efn DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0601231023040 DOT 18707 AT access1 DOT cims DOT nyu DOT edu> <43D52923 DOT C90D9967 AT dessent DOT net> <Pine DOT GSO DOT 4 DOT 63 DOT 0601231435340 DOT 27934 AT access1 DOT cims DOT nyu DOT edu> <20060125024444 DOT GB4272 AT efn DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Yitzchak Scott-Thoennes wrote:

> Just to reemphasize, these are *not* corrupt tarballs.  They are
> tarballs exactly as downloaded, extracted, and installed.  It's just
> that later the versions on the cygwin mirror became different while
> keeping the same version/filename.  I verified in a couple of the
> cases that the newer version actually had executables rebuilt, with
> slightly different file sizes and timestamps.
> 
> I don't think I have any of them around any more, but if you were to
> pick a current tarball in your local package directory and un-bzip2 it
> and re-bzip2 it with a different compression level, you should see
> the problem.

Well it's corrupt from the standpoint of setup.exe, which only knows
that it has encountered a file with the specified name but incorrect
size and/or MD5 based on the information in the setup.ini file.  Short
of AI there is no way for it to distinguish this case from the case of
something that is actually corrupt.

If people are uploading new packages (or otherwise modifying them once
"in flight") without bumping the version, then that needs to stop.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/