all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 44880@debbugs.gnu.org
Subject: [bug#44880] [PATCH] gnu: ruby-rubocop: Update to 1.4.2.
Date: Fri, 4 Dec 2020 14:58:33 -0500	[thread overview]
Message-ID: <X8qU6bHRX4m1k1NB@jasmine.lan> (raw)
In-Reply-To: <3298b708-515f-5ef2-3198-6395749da8d6@mailbox.org>

On Fri, Nov 27, 2020 at 08:05:06PM +0100, Tomás Ortín Fernández via Guix-patches via wrote:
> I'm finding it very difficult to package the updated rubocop from git, so here is a patch with rubocop 1.4.2 packaged from the gem. It was packaged from git because the gem doesn't include tests, but I can't figure out how to make the tests work. I have already asked for help at help-guix, and I'm sending this patch in the meanwhile because the current rubocop version is too outdated to be useful at all. As soon as I have the tests figured out, I will send a patch enabling the tests.
> 
> * gnu/packages/ruby.scm (ruby-rubocop): Update to 1.4.2, fetch from gem, disable tests

Thanks! Did you check if the packages that depend on ruby-rubocop still
work after this upgrade? You can get the list of such packages with
`guix refresh --list-dependent ruby-rubocop` and then try building each
one.




  reply	other threads:[~2020-12-04 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26  9:21 [bug#44880] [PATCH] gnu: ruby-rubocop: Update to 1.4.2 Tomás Ortín Fernández via Guix-patches via
2020-11-27 14:56 ` [bug#44880] Mistake Tomás Ortín Fernández via Guix-patches via
2020-11-27 19:05 ` [bug#44880] [PATCH] gnu: ruby-rubocop: Update to 1.4.2 Tomás Ortín Fernández via Guix-patches via
2020-12-04 19:58   ` Leo Famulari [this message]
2021-02-25 22:50 ` Björn Höfling

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=X8qU6bHRX4m1k1NB@jasmine.lan \
    --to=leo@famulari.name \
    --cc=44880@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 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.