public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: AFRL/RIG USLM <AFRL.RIG.USLM@us.af.mil>
Subject: Re: Version 2.6.0
Date: Wed, 21 Nov 2018 17:15:00 -0000	[thread overview]
Message-ID: <3e251e32-361b-7ac8-d401-a52f934e170d@SystematicSw.ab.ca> (raw)
In-Reply-To: <CY1P111MB01671EACD67AF7C519AAF4E495DA0@CY1P111MB0167.NAMP111.PROD.OUTLOOK.COM>

On 2018-11-21 09:45, AFRL/RIG USLM wrote:
> We are in need of the installation package for Cygwin version 2.6.0 only.
> This is the only version we are authorized to use.
> How do we go about getting this

Cygwin is a rolling package release system: setup program, base library, support
library, and program packages are continually updated and released.

Older versions are unsupported by the volunteer package maintainers, who apply
fixes only to the latest releases of packages to create updated versions.
So outdated older package versions will have unpatched security issues which
then become the responsibility of anyone choosing to run old releases.

Cygwin 2.6 is only the version of the base package: you really need a list of
all installed packages and their versions.

You can find older packages at:

http://www.crouchingtigerhiddenfruitbat.org/Cygwin/timemachine.html

Good luck running any old releases under Windows 10.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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

      parent reply	other threads:[~2018-11-21 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21 16:45 AFRL/RIG USLM
2018-11-21 17:05 ` Andrey Repin
2018-11-21 17:15 ` 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=3e251e32-361b-7ac8-d401-a52f934e170d@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=AFRL.RIG.USLM@us.af.mil \
    --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).