From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 130427 invoked by alias); 26 Oct 2017 20:40:49 -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 130416 invoked by uid 89); 26 Oct 2017 20:40:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.6 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=possession, nonstandard, setup-x86.exe, UD:setup-x86.exe 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; Thu, 26 Oct 2017 20:40:47 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B074D20CDC; Thu, 26 Oct 2017 16:40:45 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Thu, 26 Oct 2017 16:40:45 -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 3E55A7FA79; Thu, 26 Oct 2017 16:40:45 -0400 (EDT) From: Jon Turney Subject: Re: cygwin x86 setup issue:Can't connect to (null):80 To: The Cygwin Mailing List Cc: Fergus References: Message-ID: Date: Thu, 26 Oct 2017 20:40: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/msg00344.txt.bz2 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. > This command now fails, but too early in the process for a logfile to > be commenced. Basically the locally-based installation procedure > hangs. Thanks for reporting this problem. I can't reproduce it. Perhaps running setup with --no-admin --verbose (so that logging is emitted to the terminal) might shed some light on things? > I changed the command to update conventionally from the internet and > everything worked properly: the update occurred without a glitch. -- 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