emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#41036: closed (ruby: Add 2.7.3.)


From: GNU bug Tracking System
Subject: bug#41036: closed (ruby: Add 2.7.3.)
Date: Wed, 24 Jun 2020 20:29:02 +0000

Your message dated Wed, 24 Jun 2020 21:28:51 +0100
with message-id <87eeq46we4.fsf@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@gnu.org.)


-- 
41036: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=41036
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: ruby: Add 2.7.3. Date: Sat, 02 May 2020 23:25:53 +0000
This patch adds Ruby 2.7.3, the latest release.



Attachment: 0001-gnu-Add-ruby-2.7.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: [bug#41036] [PATCH 0/2] New patches to update Ruby to 2.7 Date: Wed, 24 Jun 2020 21:28:51 +0100 User-agent: mu4e 1.4.10; emacs 26.3
Ryan Prior via Guix-patches via <guix-patches@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

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]