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
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Setup 2.510.2.2 failure
Date: Tue, 13 Sep 2005 11:09:52 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <OF3A1953E2.C7EC0D07-ON8825707A.006E33DF-8825707A.0070EE76@mck.us.ray.com>
Message-ID: <SERRANOCrJRxKZMqA4d00000344@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Arthur I Schwarz
>Sent: 12 September 2005 21:34

> And for:

  Basically vast swathes of X.  I've seen this too.  I haven't understood
the problem yet, but like I said the best workaround is to rename aside or
delete the files; you may end up unnecessarily re-downloading some, but
that's not the end of the world, and the md5 checksum will guarantee that no
package that is _actually_ corrupt gets installed.  (The problem is that a
check for package validity based on comparing the actual filesize on disk of
the .tar.bz2 with the supposed size listed in setup.ini flags a discrepancy;
this should be dealt with by setup rather than throwing an exception, but in
any case it appears to be a false positive and so should really be properly
fixed before we implement anything to auto-delete/rename seemingly-corrupt
packages).



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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/