X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW
X-Spam-Check-By: sourceware.org
Received-SPF: pass (google.com: domain of dave.korn.cygwin@gmail.com designates 10.180.99.100 as permitted sender) client-ip=10.180.99.100;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of dave.korn.cygwin@gmail.com designates 10.180.99.100 as permitted sender) smtp.mail=dave.korn.cygwin@gmail.com; dkim=pass header.i=dave.korn.cygwin@gmail.com
Message-ID: <4F482FE5.8080602@gmail.com>
Date: Sat, 25 Feb 2012 00:48:37 +0000
From: Dave Korn <dave.korn.cygwin@gmail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Automating setup - --no-verify doesn't seem to work
References: <ji8vgp$qs7$1@dough.gmane.org>
In-Reply-To: <ji8vgp$qs7$1@dough.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On 24/02/2012 19:56, Andrew DeFaria wrote:
> I'm trying to automate the setup of cygwin and I'm running setup.exe
> with many additional options. All in all it's working fairly nicely but
> the --no-verify doesn't seem to work. The help says that --no-verify is
> "Don't verify setup.ini signatures" yet when I run it I see a lot of
> "Checking MD5 for <package>". Isn't there an option to turn off this MD5
> checking?

  No, those are actually two separate things.  The --no-verify option means
that setup.exe will accept any setup.ini file with any values for the md5sums
for packages, not just the official version; it doesn't stop the md5sums from
being checked, just means that a custom mirror can supply its own versions of
packages with their own md5sums, but they always get checked no matter what.

    cheers,
      DaveK

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