From: Keith Thompson <Keith.S.Thompson@gmail.com>
To: cygwin@cygwin.com
Cc: Keith Thompson <Keith.S.Thompson@gmail.com>
Subject: setup-x86_64.exe 2.884 vs. setup.ini 2.891
Date: Sun, 29 Apr 2018 20:38:00 -0000 [thread overview]
Message-ID: <CAAHpriMDMcwX+GCTtnvJEDee2gYvTsgfkk-Wh5x5pd1eynEvUQ@mail.gmail.com> (raw)
I'm using a freshly downloaded copy of https://cygwin.com/setup-x86_64.exe,
which reports itself to be "Setup.exe version 2.884 (64 bit)".
I use http://mirrors.kernel.org
Every time I run the setup program, it reports:
Cygwin Setup
The current ini file is from a newer version of setup-x86_64.exe. If you
have any trouble installing, please download a fresh version from
http://www.cygwin.com/setup-x86_64.exe.
I've confirmed that the ini file at
http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.ini
contains:
release: cygwin
arch: x86_64
setup-timestamp: 1524946592
setup-version: 2.891
I was able to find https://cygwin.com/setup/setup-2.891.x86_64.exe via
a Google search, which works around the problem, but the underlying
problem is still there: the default setup program is inconsistent
with the setup.ini files on the mirrors.
I've been having this problem for several weeks (I don't know exactly
when it started). I've checked several other mirror sites, and the
setup.ini for all the ones I've checked also specify version 2.891.
If I ignore the warning messages, the discrepancy doesn't seem to
cause any problems.
I'm using Windows 10.
--
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 reply other threads:[~2018-04-29 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 20:38 Keith Thompson [this message]
2018-04-29 21:22 ` Steven Penny
2018-05-02 6:48 ` Keith Thompson
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=CAAHpriMDMcwX+GCTtnvJEDee2gYvTsgfkk-Wh5x5pd1eynEvUQ@mail.gmail.com \
--to=keith.s.thompson@gmail.com \
--cc=cygwin@cygwin.com \
/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).