From: Thomas Schweikle <tschweikle@bfs.de>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Ruby EOL in Cygwin 3.4.9?
Date: Thu, 12 Oct 2023 17:43:55 +0000 [thread overview]
Message-ID: <065b648b-6eb0-4303-888e-5f94bfd22fff@bfs.de> (raw)
In-Reply-To: <PH7PR22MB31209C697AD372E36AD384ABAFCCA@PH7PR22MB3120.namprd22.prod.outlook.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 577 bytes --]
Am Mi., 11.Okt..2023 um 18:37:29 schrieb Hendrickson, Eric D via Cygwin:
> Hello all,
>
> As a ~25 year user and sometime contributor to Cygwin, I support Cygwin here at my place of work. Does anyone know why we are deploying Ruby 2.6 which EOL about 18 months ago?
>
> https://www.ruby-lang.org/en/downloads/branches/
>
> I'm concerned about proliferation of EOL versions of Ruby in case some security risk / 0Day is identified.
Did you set version 2.6* to install? It is still there and may be
installed. Version 3.2.2 is available too.
--
Thomas
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2521 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 321 bytes --]
prev parent reply other threads:[~2023-10-12 17:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 16:37 Hendrickson, Eric D
2023-10-11 22:03 ` Eliot Moss
2023-10-11 22:36 ` Hendrickson, Eric D
2023-10-12 1:11 ` Eliot Moss
2023-10-12 2:55 ` Eric D Hendrickson
2023-10-12 3:59 ` gs-cygwin.com
2023-10-12 4:15 ` Eric D Hendrickson
2023-10-12 4:46 ` gs-cygwin.com
2023-10-12 15:18 ` Eric Hendrickson
2023-10-12 16:53 ` Brian Inglis
2023-10-12 18:21 ` Adam Dinwoodie
2023-10-12 21:46 ` Eric Hendrickson
2023-10-12 22:17 ` David Rothenberger
2023-10-13 9:15 ` Adam Dinwoodie
2023-10-11 22:47 ` Yasuhiro Kimura
2023-10-12 13:42 ` Brian Inglis
2023-10-12 17:43 ` Thomas Schweikle [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=065b648b-6eb0-4303-888e-5f94bfd22fff@bfs.de \
--to=tschweikle@bfs.de \
--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).