From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13442 invoked by alias); 13 Dec 2017 00:12:59 -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 13428 invoked by uid 89); 13 Dec 2017 00:12:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=UD:altervista.org, H*UA:github.com, H*M:google X-HELO: mail-oi0-f46.google.com Received: from mail-oi0-f46.google.com (HELO mail-oi0-f46.google.com) (209.85.218.46) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 13 Dec 2017 00:12:57 +0000 Received: by mail-oi0-f46.google.com with SMTP id w131so475439oiw.0 for ; Tue, 12 Dec 2017 16:12:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:subject:to:references :user-agent; bh=9GhG7gkR8dLAu+EOBzMdxasoc163zQtBnoURnMdbcoM=; b=gv/hQII2vv1gmpx61TkUz4GTZjZsBSTzdOL4XJWVZ0o3BnB7LAurdWLeFMEMcK327A H2o6SmhiBha6NYylQ4nB7idjv88PLvmHaGl6ebs0kYFb+Zxm4xKs38jB3CsBNeJbBs1t zhd/Glj7I9m17ZQLzliMrF14uWUw2qPBFRXDJmYUS0WYGUFREZUjJxd1gLJMiSr0m2Hf YiB+IrauVSpjoByviB+eB+JM0r5f4pHxUvPQefcRvNFn8iLkt1mIeRK5jAMNN1reqxIC 5TsM2J4EStvpsr7eoFnOk2+rgETgxNcmfNUP7p8CvH+sAU1gBmLDY4v8ApMayE7CG/Uu l04A== X-Gm-Message-State: AKGB3mIyrxZbReit5r/J69MPJlpLp6Wn2vN2Ls+WE6L1z/7u/rPtE+q3 F5pKP4jdJifv6BIhjGaRYoMaUQ== X-Google-Smtp-Source: ACJfBosD/ixFOvmZD4MRvmfknDuNIQ/2Y07DjvpGdnyK6gbXi9oiMmztphsWeC3WlT2JHQnlMHtWOg== X-Received: by 10.202.49.212 with SMTP id x203mr482141oix.33.1513123975063; Tue, 12 Dec 2017 16:12:55 -0800 (PST) Received: from giq ([2605:6000:9fc0:56:782b:4ab4:f364:a67]) by smtp.gmail.com with ESMTPSA id z45sm222311otz.77.2017.12.12.16.12.53 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Dec 2017 16:12:54 -0800 (PST) Message-ID: <5a307086.70159d0a.91426.1547@mx.google.com> Date: Wed, 13 Dec 2017 04:09:00 -0000 From: Steven Penny X-Google-Original-From: Steven Penny 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) X-SW-Source: 2017-12/txt/msg00118.txt.bz2 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