Unresolved specs during Gem::Specification.reset:

Question

When launching Guard, I\'m getting this output:

$ guard
WARN: Unresolved specs during Gem::Specification.reset:
             


        

Answer 1

I was getting this message while running Rspec within a Guard plugin gem, using bundle exec rspec. It turned out to be a missing line in the gemspec file:

$:.push File.expand_path("../lib", __FILE__)

This line is normally at the top of the file (in many of the gems I have recently been working in) and I had commented it out to see why.

Answer 2

add

'bundle exec'

before your command.

I use ruby 2.4 and got the same problem when deploying jekyll on windows, it fixed.

Answer 3

I was seeing this issue by just running RSpec on its own. From what I understand, this means that you have more than one version of the listed gems installed on your system, and RSpec is unsure which one to use. After uninstalling older version of the gems, the warnings went away.

You can try:

gem cleanup lumberjack

Or:

gem list lumberjack

gem uninstall lumberjack

If you're using Bundler, you can try bundle exec guard (or in my case bundle exec rspec).

Answer 4

This worked for me:

bundle clean --force

then

bundle install

to reinstall gems.

Answer 5

Using the following command solved it for me:

bundle clean --force

See guard-and-unresolved-specs for more info

Answer 6

Use Bundler. Call bundle exec guard, not guard.