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:subject:to:references
	:content-type; q=dns; s=default; b=eRJC6tUEnwzIrtTvphRUiRdDujxxA
	EagSmVx5SLvlJ6ud7dErm08ewezv+U9mPNZ2CD9Sayyey40E1UUvCh0Qq+CXpq+L
	lyLKunW+O0AF4H4iHKKzZkU5eR64o8rjrYhYFQNKhnEyNFdrmox7toBT28Xnf6jq
	5MlViW0H7uJnu8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5a307086.70159d0a.91426.1547@mx.google.com>
Date: Tue, 12 Dec 2017 16:12:54 -0800 (PST)
From: Steven Penny <svnpenn@gmail.com>
Subject: Re: setup 2.883 release candidate - please test
To: cygwin@cygwin.com
References: <0c853d67-305e-97fd-c144-9151c3ba2085@cornell.edu>
Content-Type: text/plain; charset=utf8; format=flowed
User-Agent: Tryst/2.0.1 (github.com/svnpenn/tryst)

On Tue, 12 Dec 2017 08:04:09, Ken Brown wrote:
> How can setup possibly automate this?  It doesn't know where the corrupt 
> local tarball came from.  For example, suppose you sometimes build 
> packages yourself for testing or debugging.  You keep them in your local 
> repository, and you also upload them to a private repository on the 
> internet so that you can easily install them on a different computer. 
> You make a change and rebuild the package, but you forget to replace all 
> copies of it.  setup can't know which version is the correct one.  And 
> it certainly shouldn't be deleting your files because it thinks they're 
> corrupt.

No, this is not right. If you are building packages yourself, then you should
have a custom setup.ini to match, example:

http://matzeri.altervista.org/x86_64

so that in any case, setup.ini has the final say of what a correct archive is,
via the SHA512. If a file in the local repo doesnt match either because:

- file size 0
- file size less than proper size because of interrupted download
- SHA mismatch because of custom build

said file should be removed and redownloaded by setup.exe. if you are building
custom archives, then you should also be making custom setup.ini.


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