X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=G1ztavunUuSx1g9ahW7UzGI+X3UXTbIMNf5G+SzayoFGQx7EcEPAp JHWwqY9duv2ey36qHfUVyDE2mco8U+ovkWlDgsMFIdhhoYUj4BIXGWM7oWKaaTx3 awsoXs2qHCGnbndwP3LJHgxtBMSSU8ilbIxGOG4mNI4mXTlXHG4LME= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; s=default; bh=Ay8KC+tYlEOCa4zJjzzHQ0hy0qE=; b=NLrvxNuUQGat6lXqujSsZQ0qzXZU aVaQpkFbP/eM0WA6zJIgYRq3QAxfNPifYmcRAtuXG/ZfZmExNG/2Gdhg5BFFjSgQ umoN9RQKd0rZyYqnNDWgTbUX1PqnaeByrxFHlHlj4T3BzeO7gd//ZzUapWAsQ+tM LobPP5wYshzd2nI= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.4 required=5.0 tests=AWL,BAYES_50,FSL_HELO_BARE_IP_2,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: plane.gmane.org To: cygwin AT cygwin DOT com From: Achim Gratz Subject: Re: Updated: setup.exe (Release 2.872) Date: Tue, 13 Oct 2015 07:13:29 +0000 (UTC) Lines: 27 Message-ID: References: <000501d10580$62e56a90$28b03fb0$@bonhard.uklinux.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Fergus bonhard.uklinux.net> writes: > I always install / update Cygwin from a x86/release/ directory located on my > hard drive, and kept up to date. So you use a local mirror? > 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? Yes, if the directory you install from looks like a local mirror then setup.ini should be found in the correct place and the signature should check OK to ensure the file and everything you install later on, through the SHA-512 checksums, hasn't been tampered with. You can skip the signature check with '-X / --no-verify', but unless you modify setup.ini I suggest to just download the .sig file as well. You might want to add '-m / --mirror-mode' as well to ensure that setup doesn't switch into ad-hoc install mode inadvertently. If you want to use the ad-hoc install method w/o setup.ini (which requires that setup searches the disk for package files, which is quite inefficient for a full install), then rename the directory so it doesn't look like a local mirror or start setup from a deeper level in the directory tree. Regards, Achim. -- 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