all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tomás Ortín Fernández via Guix-patches via <guix-patches@gnu.org>
To: 44882@debbugs.gnu.org
Subject: [bug#44882] Dependencies issues
Date: Sat, 28 Nov 2020 09:53:20 +0100	[thread overview]
Message-ID: <ff11ad2f-aa74-64db-d7ba-820e4b8fdd81@mailbox.org> (raw)
In-Reply-To: <55bea941-e029-69b7-0603-5548567659ef@mailbox.org>

Hello,

I have realized this patch isn't correct. I hadn't tested it on a clean environment before.
Solargraph requires Rubocop 0.52 (!). In fact, the current version of Solargraph doesn't currently work, either: there are version issues with Rubocop and with ruby-thor.

I need a more-or-less current Solargraph and Rubocop, that's why I have been updating some packages, but I realize now I wasn't doing it properly and that I'm getting tangled into a web of dependencies issues.

How should I proceed? Clearly Rubocop should be updated, but I don't know how to keep Solargraph working and how to figure out which packages will need to be updated or checked in case they need an older version of Rubocop.

I'm quite new to all of this, so sorry if I'm not doing things how I'm supposed to!

Tomás




  reply	other threads:[~2020-11-28  8:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 10:02 [bug#44882] [PATCH] gnu: ruby-solargraph: Update to 0.39.17 and add two dependencies Tomás Ortín Fernández via Guix-patches via
2020-11-28  8:53 ` Tomás Ortín Fernández via Guix-patches via [this message]
2020-12-04 19:56   ` [bug#44882] Dependencies issues Leo Famulari
2020-12-28  1:17   ` Björn Höfling
2020-12-04 19:44 ` [bug#44882] [PATCH] gnu: ruby-solargraph: Update to 0.39.17 and add two dependencies Leo Famulari
2021-02-25 22:47 ` Björn Höfling
2021-02-25 22:47 ` 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=ff11ad2f-aa74-64db-d7ba-820e4b8fdd81@mailbox.org \
    --to=guix-patches@gnu.org \
    --cc=44882@debbugs.gnu.org \
    --cc=tomasortin@mailbox.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.