Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gem Error: WARN: Unresolved specs during Gem::Specification.reset: #1173

Closed
nayefc opened this issue Feb 9, 2014 · 5 comments

Comments

Projects
None yet
2 participants
@nayefc
Copy link

commented Feb 9, 2014

Hello,

Everytime I run middleman s, I get:

WARN: Unresolved specs during Gem::Specification.reset:
      rack (>= 1.0, >= 1.4.5)
      thor (< 2.0, >= 0.15.2)
      activesupport (~> 3.2.6)
      rb-fsevent (>= 0.9.3)
      rb-inotify (>= 0.9)

I did try to run gem cleanup and run bundle install after that but it still does not work.

Any ideas?

@tdreyno

This comment has been minimized.

Copy link
Member

commented Feb 10, 2014

bundle exec middleman s?

@nayefc

This comment has been minimized.

Copy link
Author

commented Feb 10, 2014

bundle exec middleman s does't show the warnings. What's the difference? Is there anything that needs to be fixed? I'm not entirely sure why these warnings are showing up.

@tdreyno

This comment has been minimized.

Copy link
Member

commented Feb 11, 2014

All calls to middleman, other than init need to be run through Bundler (it's a ruby dependency management thing that works around really dumb stuff in the core Rubygems).

You can either call bundle exec middleman s every time. Or, run:

bundle install --binstubs

And then you can run:

./bin/middleman s

And if you add ./bin to your $PATH variable, you can directly run:

middleman s

And it will automatically be run through bundler.

See more: https://github.com/sstephenson/rbenv/wiki/Understanding-binstubs

@nayefc

This comment has been minimized.

Copy link
Author

commented Feb 12, 2014

Makes sense, thank you! Why did middleman s never throw such errors before until I upgraded it though?

@tdreyno

This comment has been minimized.

Copy link
Member

commented Feb 12, 2014

Those aren't errors, just warnings from inside Rubygems. At some point, it downloaded some gems which has some kind of warnings that need to be cleaned up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.