Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 25 Jul 2005 21:21:40 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Download Incomplete.  Try again?
Message-ID: <20050726012140.GA20576@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <20050726005246 DOT 6F0C28355D AT pessard DOT research DOT canon DOT com DOT au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050726005246.6F0C28355D@pessard.research.canon.com.au>
User-Agent: Mutt/1.5.8i

On Tue, Jul 26, 2005 at 10:52:46AM +1000, Luke Kendall wrote:
>I'm currently trying to find out why a recent copy of a cygwin mirror
>causes the "Download Incomplete.  Try again?" error in setup.exe.  The
>md5 checksums on each file within the download is good (we check them
>against the md5.sum file in each package directory).  But still we get
>the above error.
>
>Is there a way to test if a downloaded cygwin will cause the "Download
>Incomplete.  Try again?" error, except by running setup.exe?
>
>By looking through the mailing list archives, I got the impression that
>this happened when the setup.ini file got out of sync with the
>collection of packages - but Christopher explained that setup.ini only
>gets updated occasionally.

No, I said it was updated "at regular intervals", not "on a continuous
basis".

>And I can confirm that: many of the package versions in setup.ini don't
>match the versions of the packages present, even in stable and
>installable cygwin mirrors.

Actually, yes they do.

>Is that because setup.ini gets updated manually?

It doesn't get updated manually.

cgf

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