From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 724 invoked by alias); 27 Oct 2017 13:48:05 -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 676 invoked by uid 89); 27 Oct 2017 13:48:04 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=Hx-languages-length:1509, our, Hx-spam-relays-external:ESMTPA X-HELO: out4-smtp.messagingengine.com Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 27 Oct 2017 13:48:02 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 973CD20C61; Fri, 27 Oct 2017 09:48:00 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Fri, 27 Oct 2017 09:48:00 -0400 X-ME-Sender: Received: from [192.168.1.102] (host86-179-113-201.range86-179.btcentralplus.com [86.179.113.201]) by mail.messagingengine.com (Postfix) with ESMTPA id 28B2F7F9A9; Fri, 27 Oct 2017 09:48:00 -0400 (EDT) Subject: Re: cygwin x86 setup issue:Can't connect to (null):80 From: Jon Turney To: The Cygwin Mailing List References: Cc: Fergus Message-ID: <76436e6c-e84d-927f-e5e9-f1cb9b262e60@dronecode.org.uk> Date: Fri, 27 Oct 2017 13:48:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2017-10/txt/msg00350.txt.bz2 On 26/10/2017 21:40, Jon Turney wrote: > On 26/10/2017 16:52, Fergus wrote: >>>> .. we are using our internal cygwin mirror >>>> .. when we setup x86-setup.exe .. it show download incomplete .. >>>> I thought perhaps setup couldn't handle a nonstandard port .. >> >> Not quite certain what is going on but something is, possibly related >> to the latest recent up-versioning of the setup-x86 executable to >> 2.882? > > Since the OPs first mail about their problem (2017-10-15) pre-dates the > release of setup 2.882 (2017-10-24), this seems unlikely unless OP is in > possession of a time-machine. > >> Forever I have updated Cygwin using a Command Prompt window and the >> typed command >> setup-x86.exe -L D:\cyg -R D:\consoleX -gqnm >> where the key switches are to update to the Cygwin provision located >> at D:\consoleX from a local mirror located at D:\cyg. >> (Previously I will have updated x86\setup.ini and x86\setup.ini.sig >> and augmented x86\release\ so that everything is in place that is >> needed.) > > I'm not sure what this means. > > There should be no way for you to generate a valid setup.ini.sig (absent > possession the Cygwin signing key, or using --no-verify, or using > --pubkey to provide an additional key), assuming the setup validates > that signature in --local-package-dir mode, which I think it should be. Oh, I get it. You're just saying you update the (partial?) mirror in 'D:\cyg'. Sorry for the misunderstanding. -- 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