Can't install gem with mutant

[roman-dubrovsky]

Has a dependecies conflict with mutant-rspec library

Fetching gem metadata from http://rubygems.org/.......
Fetching gem metadata from http://rubygems.org/.
Resolving dependencies........
Bundler could not find compatible versions for gem "parser":
  In snapshot (Gemfile.lock):
    parser (= 2.5.3.0)

  In Gemfile:
    mutant-rspec was resolved to 0.8.24, which depends on
      mutant (~> 0.8.24) was resolved to 0.8.24, which depends on
        parser (~> 2.5.1)

    datarockets-style (~> 0.2.0) was resolved to 0.2.0, which depends on
      rubocop (~> 0.73.0) was resolved to 0.73.0, which depends on
        parser (>= 2.6)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

It can also be rubocop or mutant issue.

Mutant rspec: https://github.com/mbj/mutant/blob/master/docs/mutant-rspec.md

[TheBlackArroVV]

Looks like mutant want like versions of gem parser between 2.5.1 and 2.6.0 without including last one. And rubocop from 2.6.0, so i think the right way for fixing it is to open issue in mutant repository

Sincerely, yours cap

[nikitasakau]

Update about this problem:

Now we have a bit different versions but problem looks the same: rubocop upgrades parser, mutant can not get in time 🤷‍♂️.

Even a bit more difficult: mutant depends on unparser, and unparser can not get in time with parser upgrading. BUT unparser is a gem of mutant developer.

I've created issue - https://github.com/mbj/mutant/issues/992 in mutant rep and maintainer has already asked and self-assigned on it. So looks like he is going to fix it.

But what I noticed. Problems with parser is a pretty often meets. And looks like they need some time to upgrade it. I've seen when issue with almost the same problem created on September and fixed on January. Also he is linked my issue to https://github.com/mbj/unparser/issues/129. It was created on May and nothing finished.

Do we really need this gem? Even if we can install it, looks like we will get problems with parser in the future because they lock version. And we will not be able to upgrade rubocop for example. Or I'm wrong?

[roman-dubrovsky]

Do we really need this gem?

@nikitasakov did you mean rubocop or mutant?

[nikitasakau]

@roman-dubrovsky I mean mutant. Now rubocop does not allow to install mutant because of parser, but if we install it, mutant will not allow us update rubocop in the future because of parser again. Or I'm wrong?

[roman-dubrovsky]

hm, looks like this issue is still relevant.

and yes, I want that we'll try to use mutant (especially until all of us don't know how to write good tests). This library adds good test coverage and allows avoiding a lot of code smells

[nikitasakau]

My issue resolved and now it is possible to install mutant-rspec. Can we close this issue or we will able to close it after mutant installation only? @roman-dubrovsky

[roman-dubrovsky]

@nikitasakov 👍 can you check it locally and close the issue

[nikitasakau]

Checked, installed without any problems with current rubocop (0.80)

[mbj]

@nikitasakov, @roman-dubrovsky I just found this issue.

Just as a heads up: Mutant is now much better maintained (and still free to use for OSS projects). The 0.10.x series is closely tracking the reminder of the ecosystem. Plus unparser got major updates that will make it easier to closely track parser.

I recommend to update to mutant-0.10.x.

[roman-dubrovsky]

@mbj nice, thank you so much. I'll check it later.

[mbj]

@roman-dubrovsky Have you been using mutant on this repo, or another repo where mutant conflicted with this repo?

[roman-dubrovsky]

@mbj only in other repo for now

[mbj]

@roman-dubrovsky is that other repo public?