all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ben Woodcroft <woodibe@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [PATCH] Upgrade ruby to 2.3.1 (including symlink patch)
Date: Thu, 28 Apr 2016 21:56:55 +1000	[thread overview]
Message-ID: <5721FA87.3090803@gmail.com> (raw)
In-Reply-To: <87fuu6xn7t.fsf@elephly.net>



On 28/04/16 16:27, Ricardo Wurmus wrote:
> Ben Woodcroft <woodibe@gmail.com> writes:
>
>> On 28/04/16 15:19, Ricardo Wurmus wrote:
>>> Rob Syme <rob.syme@gmail.com> writes:
>>>
>>>> * gnu/packages/patches/ruby-symlinkfix.patch: New patch to fix issue #1448.
>>>> * gnu/packages/ruby.scm (ruby): Update to 2.3.1 including symlink patch.
>>> Thank you!  The patch also needs to be registered in dist_patch_DATA in
>>> “gnu/local.mk”.  I can do this later when applying the patch in the
>>> office, unless there are other objections to this patch.
>> Do you mind holding off for a bit (no more than ~10 hours)? I wouldn't
>> mind having a play with this myself.
> No problem.  I can also apply this tomorrow if your tests find no
> problems.  Thanks!

Ruby-hashery now fails a unit test, but since that is a higher level 
package and ruby-ansi works I think it might be good to apply the patch 
here anyway. Would you mind please?

Thanks both,
ben

  reply	other threads:[~2016-04-28 11:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28  4:06 [PATCH] Upgrade ruby to 2.3.1 (including symlink patch) Rob Syme
2016-04-28  5:19 ` Ricardo Wurmus
2016-04-28  5:26   ` Ben Woodcroft
2016-04-28  6:06     ` Rob Syme
2016-04-28  6:27     ` Ricardo Wurmus
2016-04-28 11:56       ` Ben Woodcroft [this message]
2016-04-29 23:52         ` Ben Woodcroft
2016-04-30  6:32           ` Ricardo Wurmus
2016-04-30  6:35             ` Rob Syme

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=5721FA87.3090803@gmail.com \
    --to=woodibe@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.