This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Automating setup - --no-verify doesn't seem to work
- From: Dave Korn <dave dot korn dot cygwin at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 25 Feb 2012 00:48:37 +0000
- Subject: Re: Automating setup - --no-verify doesn't seem to work
- 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
- References: <ji8vgp$qs7$1@dough.gmane.org>
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