X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:reply-to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=sAwwHzUD82tr97BX
	B/bqGgFY3j+HnaQtqV7pgjbz6qVAYqM/GWWVOI/sd8eD8mPMlPUKK6CzaxJEfYfL
	gFM53Jf8Ee52fjH8Flpx1R7YHiUch9LMDRg/FXNAGXiaaXtBFi7DkPorti8A1B4Y
	w53ldLx4UYMOAdN65Smy8WP6XWs=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:reply-to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=igt3i5M3anH2XGWoZUGiia
	MpkoM=; b=yh6L79TljbCd5ktJST1gapR1jA9LhSCfVMTgrG0HOXwHAOPX3iCprF
	Lmyb6PSZYdJwi1ytKBBefWaTW1M/pTgG8iPgr1npHp+hkaRx/AEoNFMoChEi31ep
	eBHx/0IPVzskOyjWsgYuW1QzZ/9p2ar22vLnZzydVr6iEIHrobGvs=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=rice, Vince, Rice, vince
X-HELO:	mail-io0-f174.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:reply-to:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=kkTYMsWlUG8+gPoo5mRCgQH3chTDd63sKi4t0kUheVE=; b=qr/pxD3sTRgSgfFQY+BFBgjfTX5MZXBAPcRICNAfYYUg1/efnCjqyKoQWOTtvpvTtL GTpc+4z+EqZ945N2TWmxOQghr1aX1nvnigNVhiuy0C9T5z00/+WOED1k3a0cFnfDxzE/ u5WYZXTSVZ903FFwL4y2jsqqErxt/GJp7gSUqbSi21ZT04tqEcOVrkRiVbdWDL5zomxo dqkR+kmQrYXbEWT/JwUoaaXWKyUJw4Wix5y+5xF3NDEtQ2NyAsGLbX0YpsXcjjnqwyVB 1okls/AiX6J7BRZ35ezhIIk94JmvePb+Z3t5LjzABzB/F0fUHwezCYMinuCXKZ/stAUV 5nTA==
X-Gm-Message-State:	AKGB3mI/sbFURAwKKG3xqTwhQq68q0CyE7xEt1iyiGQqo+BkiTU1jd4E vbsLUICcr1yHKCOR7yFbSs3MeQ==
X-Google-Smtp-Source:	ACJfBouDRsL4doJKRewupcJ4PJE5x+6ZkANXIfs27I61huTA3TiveMduiwgJmv2xkfJc+wJK5I3yuw==
X-Received:	by 10.107.36.71 with SMTP id k68mr1410352iok.49.1513138144118; Tue, 12 Dec 2017 20:09:04 -0800 (PST)
Subject:	Re: setup 2.883 release candidate - please test
To:	cygwin AT cygwin DOT com
References:	<0c853d67-305e-97fd-c144-9151c3ba2085 AT cornell DOT edu> <5a307086 DOT 70159d0a DOT 91426 DOT 1547 AT mx DOT google DOT com> <D097F9F9-288E-4353-83B8-E2C370B0428B AT solidrocksystems DOT com>
Reply-To:	cygwin AT cygwin DOT com
From:	cyg Simple <cygsimple AT gmail DOT com>
Message-ID:	<fed3713a-1005-2bf0-febf-b0e7c4ee4d4b@gmail.com>
Date:	Tue, 12 Dec 2017 23:09:03 -0500
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version:	1.0
In-Reply-To:	<D097F9F9-288E-4353-83B8-E2C370B0428B@solidrocksystems.com>
X-IsSubscribed:	yes

On 12/12/2017 10:06 PM, Vince Rice wrote:
>> On Dec 12, 2017, at 6:12 PM, Steven Penny wrote:
>>
>> 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.
> 
> Where is that stated as a requirement? I don't see it anywhere, and I don't agree that it should be one. Ken is correct on this, IMO.

Both are correct views of operation.  Steve could provide patches to
allow a toggle for which logic to use with the default being what occurs
now.

-- 
cyg Simple

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

- Raw text -