forked from clio/ten_years_rails
-
Notifications
You must be signed in to change notification settings - Fork 39
Closed
Description
When running bundle_report outdated
on a Rails 2.3 LTS project the following errorr is returned:
You have already activated activesupport 5.2.4.4, but your Gemfile requires activesupport 2.3.18.31
The complete output is:
WARN: Unresolved specs during Gem::Specification.reset:
i18n (< 2, >= 0.7)
minitest (~> 5.1)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
/usr/local/bundle/gems/next_rails-1.0.2/exe/bundle_report:8:in `require': cannot load such file -- next_rails (LoadError)
from /usr/local/bundle/gems/next_rails-1.0.2/exe/bundle_report:8:in `block in <top (required)>'
/usr/local/bundle/gems/bundler-1.12.5/lib/bundler/runtime.rb:35:in `block in setup': You have already activated activesupport 5.2.4.4, but your Gemfile requires activesupport 2.3.18.31. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)
from /usr/local/bundle/gems/bundler-1.12.5/lib/bundler/runtime.rb:20:in `map'
from /usr/local/bundle/gems/bundler-1.12.5/lib/bundler/runtime.rb:20:in `setup'
from /usr/local/bundle/gems/bundler-1.12.5/lib/bundler.rb:95:in `setup'
from /usr/local/bundle/gems/bundler-1.12.5/lib/bundler/setup.rb:9:in `<top (required)>'
from /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:133:in `require'
from /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:133:in `rescue in require'
from /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:40:in `require'
from /usr/local/bundle/gems/next_rails-1.0.2/exe/bundle_report:57:in `<top (required)>'
from /usr/local/bundle/bin/bundle_report:22:in `load'
from /usr/local/bundle/bin/bundle_report:22:in `<main>'
I think if next_rails avoided actionview
as a strict dependency by removing spec.add_runtime_dependency "actionview"
from the gemspec it might help. Actionview is in fact optional from what I've seen in the code so I believe this wouldn't be an issue.
There is also #4 which is somewhat related.
Metadata
Metadata
Assignees
Labels
No labels