From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Fergus <fergus@bonhard.uklinux.net>
Subject: Re: cygwin x86 setup issue:Can't connect to (null):80
Date: Thu, 26 Oct 2017 20:40:00 -0000 [thread overview]
Message-ID: <b1aeac45-6ff1-c3d5-4333-9e887efe4433@dronecode.org.uk> (raw)
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
next prev parent reply other threads:[~2017-10-26 20:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 15:52 Fergus
2017-10-26 20:40 ` Jon Turney [this message]
2017-10-27 13:48 ` Jon Turney
-- strict thread matches above, loose matches on Subject: below --
2017-10-27 14:31 Fergus
2017-10-15 1:39 Lynn Lin
2017-10-24 13:23 ` Jon Turney
2017-10-25 19:52 ` Lynn Lin
2017-10-25 21:35 ` Brian Inglis
2017-10-26 14:35 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b1aeac45-6ff1-c3d5-4333-9e887efe4433@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=fergus@bonhard.uklinux.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).