unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: 39120@debbugs.gnu.org
Subject: [bug#39120] [PATCH 01/12] gnu: ruby-listen: Update to 3.2.0.
Date: Mon, 13 Jan 2020 22:53:25 +0000	[thread overview]
Message-ID: <20200113225336.15160-1-mail@cbaines.net> (raw)
In-Reply-To: <87h80zcd53.fsf@cbaines.net>

This avoids some test failures when updating Ruby to 2.6.

* gnu/packages/ruby.scm (ruby-listen): Update to 3.2.0.
---
 gnu/packages/ruby.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/ruby.scm b/gnu/packages/ruby.scm
index ad675dc488..b8a5c8b5d3 100644
--- a/gnu/packages/ruby.scm
+++ b/gnu/packages/ruby.scm
@@ -4548,7 +4548,7 @@ a native C extension.")
 (define-public ruby-listen
   (package
     (name "ruby-listen")
-    (version "3.1.5")
+    (version "3.2.0")
     (source
      (origin
        ;; The gem does not include a Rakefile, so fetch from the Git
@@ -4560,7 +4560,7 @@ a native C extension.")
        (file-name (git-file-name name version))
        (sha256
         (base32
-         "1hqmkfa9f2xb5jlvqbafdxjd5ax75jm8gqj5nh3k22xq0kacsvgg"))))
+         "1hkp1g6hk5clsmbd001gkc12ma6s459x820piajyasv61m87if24"))))
     (build-system ruby-build-system)
     (arguments
      `(#:test-target "spec"
-- 
2.24.1

  reply	other threads:[~2020-01-13 22:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 20:30 [bug#39120] [00/12] Update Ruby to 2.6 Christopher Baines
2020-01-13 22:53 ` Christopher Baines [this message]
2020-01-13 22:53   ` [bug#39120] [PATCH 02/12] gnu: ruby-aruba: Update to 0.14.14 Christopher Baines
2020-01-13 22:53   ` [bug#39120] [PATCH 03/12] gnu: ruby-childprocess-0.6: Remove version 0.6.3 Christopher Baines
2020-01-13 22:53   ` [bug#39120] [PATCH 04/12] gnu: ruby-childprocess: Update to 3.0.0 Christopher Baines
2020-01-13 22:53   ` [bug#39120] [PATCH 05/12] gnu: ruby-yard: Update to 0.9.20 Christopher Baines
2020-01-13 22:53   ` [bug#39120] [PATCH 06/12] gnu: ruby-hoe: Update to 3.21.0 Christopher Baines
2020-01-13 22:53   ` [bug#39120] [PATCH 07/12] gnu: ruby-power-assert: Update to 1.1.5 Christopher Baines
2020-01-13 22:53   ` [bug#39120] [PATCH 08/12] gnu: ruby-json-pure: Update to 2.2.0 Christopher Baines
2020-01-13 22:53   ` [bug#39120] [PATCH 09/12] gnu: ruby-tzinfo: Skip safe tests Christopher Baines
2020-01-13 22:53   ` [bug#39120] [PATCH 10/12] gnu: ruby-2.4: Update to 2.4.9 Christopher Baines
2020-01-13 22:53   ` [bug#39120] [PATCH 11/12] gnu: ruby: Update to 2.6.5 Christopher Baines
2020-01-13 22:53   ` [bug#39120] [PATCH 12/12] gnu: Add ruby-2.5 Christopher Baines
2020-01-13 22:59 ` [bug#39120] [00/12] Update Ruby to 2.6 Marius Bakke
2020-01-14  7:31   ` Christopher Baines
2020-01-14 23:53     ` Christopher Baines
2020-05-09  7:39       ` bug#39120: " Christopher Baines

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200113225336.15160-1-mail@cbaines.net \
    --to=mail@cbaines.net \
    --cc=39120@debbugs.gnu.org \
    /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 public inbox

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

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).