"Unresolved specs" warning with Ruby 2.0.0-p247 and rubygems 2.0.3

[mattbrictson]

I just installed Ruby 2.0.0-p247, followed by gem install rubygems-bundler. In p247 it seems that my Gemfile is no longer being honored. In addition, I get warnings about "Unresolved specs".

For example when using p247:

$ rbenv shell 2.0.0-p247 
$ guard
WARN: Unresolved specs during Gem::Specification.reset:
      lumberjack (>= 1.0.2)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
15:07:59 - INFO - Guard here! It looks like your project has a Gemfile, yet you are running
> [#] `guard` outside of Bundler. If this is your intent, feel free to ignore this
> [#] message. Otherwise, consider using `bundle exec guard` to ensure your
> [#] dependencies are loaded correctly.
> [#] (You can run `guard` with --no-bundler-warning to get rid of this message.)
15:07:59 - INFO - Guard uses TerminalNotifier to send notifications.
15:07:59 - INFO - Guard uses TerminalTitle to send notifications.
15:07:59 - INFO - Guard::RSpec is running

But Ruby 2.0.0-p195 is fine:

$ rbenv shell 2.0.0-p195 
$ guard
15:07:50 - INFO - Guard uses TerminalNotifier to send notifications.
15:07:50 - INFO - Guard uses TerminalTitle to send notifications.
15:07:50 - INFO - Guard::RSpec is running

I've run bundle install in both environments, and bundle exec guard works fine with no warnings.

Am I doing something wrong, or is this a problem with rubygems-bundler + 2.0.0-p247?

For the record, here are my ruby and gem versions:

$ rbenv shell 2.0.0-p195 
$ ruby -v
ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-darwin12.3.0]
$ gem -v
2.0.2

$ rbenv shell 2.0.0-p247 
$ ruby -v
ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.4.0]
$ gem -v
2.0.3

[mpapis]

please run and gist:

which ruby
gem env
gem which bundler-unload
gem which rubygems-bundler/noexec
gem list -d bundler-unload
gem list -d rubygems-bundler

[mattbrictson]

Here you go: https://gist.github.com/mbrictson/5882055

[mpapis]

this looks good, now:

gem list -d bundler
gem list -d guard
rbenv which guard
head -n 1 $( rbenv which guard )
NOEXEC_DEBUG=1 guard

[mattbrictson]

Done: https://gist.github.com/mbrictson/5882055#file-gistfile2-txt

I also added the output of gem list -d lumberjack for good measure.

[mpapis]

Which version of guard is in Gemfile, can I see it?
And can you please compare with ruby-2.0.0-p195:

head -n 1 $( rbenv which guard )
#!/usr/bin/env ruby

[mattbrictson]

Gist updated. Interestingly, in 2.0.0-p195 the #! line is:

#!/usr/bin/env ruby_noexec_wrapper

Whereas 2.0.0-p247 it is:

#!/usr/bin/env ruby

[mpapis]

try again after gem regenerate_binstubs

[mpapis]

if regenerate helps then most likely this issue is covered with the following issues and will be solved automatically with them:

• Extract hooking up into executables as a separate gem #44 - Extract hooking up into executables as a separate gem (required for Use gemspec.extensions to invoke regenerate_binstubs after installation #43)
• Use gemspec.extensions to invoke regenerate_binstubs after installation #43 - Use gemspec.extensions to invoke regenerate_binstubs after installation (will ensure proper shebang)
• Fail when version of target gem is not satisfied #37 - Fail when version of target gem is not satisfied (will properly fail instead of using wrong versions)

if not ... I will have more questions

[mattbrictson]

gem regenerate_binstubs fixed it. Thanks!