DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:cc:subject:date:message-id
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=PwiW/PE9QqjyUJjbXd22UvbHQ6MbkQdLSeymrtMvSjRdxzh+AGQ1P
	Y5SYbqaLS4dySJ1cIoN1a8naRm2SQvBKPkg5fY8nXccUK1ALAc8ni6j6XozeR4Vs
	dASE9sMJONDENY56ojKvTRUzuEBsFwqsvCLrPk5f09GwIsy8FdA9iQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Fergus" <fergus@bonhard.uklinux.net>
To: <cygwin@cygwin.com>
Cc: <fergus@bonhard.uklinux.net>
Subject: Re: Updated: setup.exe (Release 2.872)
Date: Tue, 13 Oct 2015 07:28:33 +0100
Message-ID: <000501d10580$62e56a90$28b03fb0$@bonhard.uklinux.net>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I always install / update Cygwin from a x86/release/ directory located on my
hard drive, and kept up to date.
The new setup-x86.exe requires setup.ini.sig located in x86/ as well as
setup.ini.
Easy to manage, but is this additional requirement intentional?
Fergus


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