all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Vong <alexvong1995@gmail.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: 33846@debbugs.gnu.org, alexvong1995@gmail.com
Subject: [bug#33846] [PATCH] gnu: ruby: Remove versions 1.8, 2.1 and 2.2.
Date: Wed, 26 Dec 2018 01:59:38 +0800	[thread overview]
Message-ID: <87va3hpjw5.fsf@gmail.com> (raw)
In-Reply-To: <20181224082249.sz7llwmjval5kba2@thebird.nl> (Pjotr Prins's message of "Mon, 24 Dec 2018 09:22:49 +0100")

[-- Attachment #1: Type: text/plain, Size: 932 bytes --]

Pjotr Prins <pjotr.public12@thebird.nl> writes:

> On Sun, Dec 23, 2018 at 05:39:09PM +0800, Alex Vong wrote:
>> Hello,
>> 
>> This patch removes all ruby versions which have reached EOL since they
>> no longer receive official security updates.
>> 
>> However, please do complain if you need to use one of these
>> versions. IMO, it is better to have a central place for them to receive
>> (unofficial) security updates (e.g. Debian will support ruby 2.1 until
>> 2020), than to roll your own security updates (which is error-prone and
>> duplicate effort).
>> 
>
> Thanks Alex,
>
> No objection. Note that we now have the channel mechanism to suport
> older versions of software we don't need to maintain older versions
> inside GNU Guix if there are no down stream dependencies.
>
OK. I have found that there is a guix-chromium channel. So I think I
understand what you mean now.

> Pj.

Thanks,
Alex

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2018-12-25 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87lg4il99m.fsf@gmail.com>
2018-12-23  9:39 ` [bug#33846] [PATCH] gnu: ruby: Remove versions 1.8, 2.1 and 2.2 Alex Vong
2018-12-24  8:22   ` Pjotr Prins
2018-12-25 17:59     ` Alex Vong [this message]
2019-01-02  8:00       ` bug#33846: " Alex Vong

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=87va3hpjw5.fsf@gmail.com \
    --to=alexvong1995@gmail.com \
    --cc=33846@debbugs.gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.