DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=nOCbohP5D51zzRx2ZbrNFSceSVuvSfsGfoQ8XYgWF6h
	IoVbdz82Ldfpos3GDVSTN3lclNf0KVHRJktmt0KXY89rTGIHLeViWqzVPSmgImxz
	UjkRlivVHrmQL0s5BpsGevgaFemIWjaHwEOSmK8bD6YRiLFVIC83mXrXohobBwYU
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <53BBB398.4090009@gmail.com>
Date: Tue, 08 Jul 2014 11:02:16 +0200
From: Marco Atzeri <marco.atzeri@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Observations about Cygwin's md5 checksums
References: <53BA242D.1040101@cisra.canon.com.au> <53BA70CC.7010809@gmail.com> <53BB6183.9000007@cisra.canon.com.au>
In-Reply-To: <53BB6183.9000007@cisra.canon.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 08/07/2014 05:12, Luke Kendall wrote:
> On 07/07/14 20:05, Marco Atzeri wrote:
>> On 07/07/2014 06:38, Luke Kendall wrote:
>>
>> setup.ini is built using the setup.hint's of the several packages.
>> No further usage outside the www.cygwin.com server.
>
> Thanks for the explanation, Marco.  Can I check what you mean?
> I think you're saying that setup.hint has no function once setup.ini has
> been created.
> (You're not saying "setup.ini shouldn't be used for other purposes.")

I am saying that when we upload a new package we also upload the new
setup.hint.
On the main server (www.cygwin.com) setup.ini is updated using
this new data, by a program that runs every 10 or 20 minutes.
Sometimes we update only the setup.hint when a "require" issue need to
be solved.
No further usage is done of the setup.hint files on the main server.
Of course you can do what you want of them ;-) but the same
(and additional) information are inside setup.ini

>> during upload of new files the creation of md5.sum is out of sync
>> with the directory content. Md5.sum is updated 1 time per hour
>> If the mirror sync before the creation of the md5sum it has still the
>> old version.
>>
>
> Does that mean that if the md5.sum file were created at the same time
> that the package contents were updated, there would be no possible way
> for out-of-sync md5.sum files to be provided?  Do you think the current
> process could be improved?
>
> I have observed that the errors in the mirrors persist for weeks or more.

upgrade of setup.ini and update of md5sum are done by two different 
processes.
Please note that the server is covering also other softwares not
only cygwin (https://www.sourceware.org/)

> Anyway, by changing our checking process to use the information in
> setup.ini instead of the md5.sum files which can be wrong (for many
> weeks), we can bypass the incorrect md5.sum files.

I expect so, as md5 in setup.ini is also used by setup-xxx.exe
to check for incorrect download.


Regards
Marco

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