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:from:subject:to:cc:references:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=APthvDNaKcmsvzXn
	1HCvxcz1R8hsyuApQEICEdIrQSWsjU8DY4gDprPpgsYky3lxcXNr8lfgSTiI4TK3
	T4ukbpZCp1vkqRyQwSYpm4SjZ0g99LgkJBw4Oxd9fcqFiJrC1i6AM+pc/rVfaUPK
	7ac2sdxiKw0ntJcLoxkZ2aEEYmI=
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:from:subject:to:cc:references:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=9tVG7n7ldO0wSt1sl68Bnj
	8QI3I=; b=EVTENUQVMhtX7hM/JuEGOnGHJAhAc34AOwW82r5VIKJPpXlcqS9N3/
	kmh4XXwSWv8jE+kr+YjDUn9gF6AdwOM+Si2CWcegNwe/YAy97EBnLQblnASksra9
	0iMEUxKI5j+9J57Ml8FHPWm3OHISahhNeLcSQXTjGs0DGybzjTyOo=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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=-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
X-ME-Sender:	<xms:TUjyWcTLVwWPK0JZb0AUiy2igaCokYk2f5uuHxIl6s1wTIFtcRtgWg>
From:	Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Subject:	Re: cygwin x86 setup issue:Can't connect to (null):80
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
Cc:	Fergus <fergus AT bonhard DOT uklinux DOT net>
References:	<CAKqBF1iYuJhuV20DE1VUmRH=pKFK_eijfAMWvX--X2CrV7YiUA AT mail DOT gmail DOT com>
Message-ID:	<b1aeac45-6ff1-c3d5-4333-9e887efe4433@dronecode.org.uk>
Date:	Thu, 26 Oct 2017 21:40:43 +0100
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:	<CAKqBF1iYuJhuV20DE1VUmRH=pKFK_eijfAMWvX--X2CrV7YiUA@mail.gmail.com>

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

- Raw text -