GNU bug report logs - #41036
ruby: Add 2.7.3.

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Christopher Baines <mail <at> cbaines.net>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#41036: closed (ruby: Add 2.7.3.)
Date: Wed, 24 Jun 2020 20:29:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 24 Jun 2020 21:28:51 +0100
with message-id <87eeq46we4.fsf <at> cbaines.net>
and subject line Re: [bug#41036] [PATCH 0/2] New patches to update Ruby to 2.7
has caused the debbugs.gnu.org bug report #41036,
regarding ruby: Add 2.7.3.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
41036: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=41036
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ryan Prior <rprior <at> protonmail.com>
To: "guix-patches <at> gnu.org" <guix-patches <at> gnu.org>
Subject: ruby: Add 2.7.3.
Date: Sat, 02 May 2020 23:25:53 +0000

[Message part 3 (text/plain, inline)]

This patch adds Ruby 2.7.3, the latest release.

[Message part 4 (text/html, inline)]

[0001-gnu-Add-ruby-2.7.patch (text/x-patch, attachment)]

[Message part 6 (message/rfc822, inline)]

From: Christopher Baines <mail <at> cbaines.net>
To: Ryan Prior <rprior <at> protonmail.com>
Cc: 41036-done <at> debbugs.gnu.org
Subject: Re: [bug#41036] [PATCH 0/2] New patches to update Ruby to 2.7
Date: Wed, 24 Jun 2020 21:28:51 +0100

[Message part 7 (text/plain, inline)]

Ryan Prior via Guix-patches via <guix-patches <at> gnu.org> writes:

> Here are the new patches you asked for, they should apply cleanly to master.
>
> Ryan Prior (2):
>   gnu: Renames ruby to ruby-2.6.
>   gnu: Ruby: Update to 2.7.
>
>  gnu/packages/ruby.scm | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)

Great, thanks.

I've tweaked the commit messages a bit, and now pushed these patches to
core-updates.

I think the way ruby-2.7 inherits from ruby-2.6 is a bit odd, but I like
that this change is small in terms of the diff. Anyway, how to lay out
the package definitions is a lesser issue compared to what's actually
defined.

Now comes the challenge of actually fixing all the packages this change
will have broken. If updates to packages that fix issues with Ruby 2.7
don't cause too many rebuilds or break anything on master, then pushing
those to master is good. The master branch can then be merged in to
core-updates to get those changes applied there as well. Otherwise, the
fixes should be applied to core-updates.

Thanks,

Chris

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.