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
Date:	Thu, 21 Jul 2005 11:13:26 +1000 (EST)
From:	Luke Kendall <luke DOT kendall AT cisra DOT canon DOT com DOT au>
Subject:	MD5 checksum question
To:	cygwin AT cygwin DOT com
MIME-Version:	1.0
Message-Id:	<20050721011326.9EB2A83CB3@pessard.research.canon.com.au>

Does it matter that the top-level setup.ini (that duplicates the MD5
checksums of each package's md5.sum file), does *not* do the same thing
for the setup.hint file in each package directory?  I assume the
duplication is to allow the detection of the race condition (mentioned
below).

I only noticed while updating my md5cygchk mirror-checker, to detect the
case where all package md5.sum files are correct but the top-level
setup.ini file is out of sync with the packages below.

(This happens if you rsync a mirror site while the site is being
updated.  It leads to the setup.exe error: 
"Download Incomplete.  Try again?")

I'm assuming the lack of a setup.hint line in each package's entry in
setup.ini doesn't matter.

Regards,

luke


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

- Raw text -