From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: v1.7
Date: Tue, 23 May 2017 22:30:00 -0000 [thread overview]
Message-ID: <773b21a1-ef31-a03b-e444-fb278c30681c@SystematicSw.ab.ca> (raw)
In-Reply-To: <64F4610BDC915A4681532CCAE7ACFDB9344A592A@NAWEPRLHXM01V.nadsuswe.nads.navy.mil>
On 2017-05-22 18:28, Yamamoto, Anne B CIV PMRF N63 wrote:
> We are currently using v1.7 but it is no longer DADMS supported.
> Would it be possible to get a vendor support statement email so that
> we may continue using this version?
If you upgrade to a current release, support for current packages is
available from the volunteers on this list; if you cannot upgrade, you
are on your own, unless you can find an organisation to do support for
Cygwin 1.7. Please note that current releases do not support unsupported
Windows releases including XP or earlier.
You can still get XP compatible or earlier Cygwin 1.7 packages in small
quantities by following instructions at
http://www.crouchingtigerhiddenfruitbat.org/Cygwin/timemachine.html
and looking around the 2015 timeframe.
If you have to continue to use Cygwin 1.7, you may want to download and
install the source, devel, and debuginfo packages corresponding to your
installed binary package releases, shown in /etc/setup/installed.db,
from the above site a few at a time.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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
prev parent reply other threads:[~2017-05-23 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 7:27 v1.7 Yamamoto, Anne B CIV PMRF N63
2017-05-23 11:50 ` v1.7 Adam Dinwoodie
2017-05-23 22:30 ` Brian Inglis [this message]
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=773b21a1-ef31-a03b-e444-fb278c30681c@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).