This is the mail archive of the
mailing list for the Cygwin project.
Re: cygwin x86 setup issue:Can't connect to (null):80
- From: Jon Turney <jon dot turney at dronecode dot org dot uk>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Cc: Fergus <fergus at bonhard dot uklinux dot net>
- Date: Fri, 27 Oct 2017 14:47:59 +0100
- Subject: Re: cygwin x86 setup issue:Can't connect to (null):80
- Authentication-results: sourceware.org; auth=none
- References: <CAKqBF1iYuJhuV20DE1VUmRH=pKFK_eijfAMWvX--X2CrV7YiUA@mail.gmail.com> <firstname.lastname@example.org>
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
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
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
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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple