From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21289 invoked by alias); 13 Dec 2017 13:28:07 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 21280 invoked by uid 89); 13 Dec 2017 13:28:07 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.2 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=ground X-HELO: limerock04.mail.cornell.edu Received: from limerock04.mail.cornell.edu (HELO limerock04.mail.cornell.edu) (128.84.13.244) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 13 Dec 2017 13:28:05 +0000 X-CornellRouted: This message has been Routed already. Received: from authusersmtp.mail.cornell.edu (granite4.serverfarm.cornell.edu [10.16.197.9]) by limerock04.mail.cornell.edu (8.14.4/8.14.4_cu) with ESMTP id vBDDS3jN023648 for ; Wed, 13 Dec 2017 08:28:03 -0500 Received: from [192.168.0.15] (mta-68-175-129-7.twcny.rr.com [68.175.129.7] (may be forged)) (authenticated bits=0) by authusersmtp.mail.cornell.edu (8.14.4/8.12.10) with ESMTP id vBDDS2F2009946 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Wed, 13 Dec 2017 08:28:03 -0500 To: cygwin From: Ken Brown Subject: setup's response to a "corrupt local copy" Message-ID: Date: Wed, 13 Dec 2017 14:36:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Cornell-Gauge: Gauge=XXXXX X-PMX-CORNELL-AUTH-RESULTS: dkim-out=none; X-IsSubscribed: yes X-SW-Source: 2017-12/txt/msg00124.txt.bz2 This is a followup to the discussion started here: https://cygwin.com/ml/cygwin/2017-12/msg00088.html When setup is preparing to download files and it finds a corrupt copy in the local cache, it issues a fatal error message telling the user to remove the corrupt file and retry. Steven said that setup should silently delete the corrupt file, while I argued in favor of the current behavior, on the grounds that setup shouldn't be deleting user files if it doesn't know where they came from. There is a middle ground: setup could query the user. Additionally, as suggested by cyg Simple, there could be an option that directs setup to silently remove corrupt files. Ken -- 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