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

old problem: unable to bundle #2

Open
polka opened this issue Feb 5, 2012 · 1 comment
Open

old problem: unable to bundle #2

polka opened this issue Feb 5, 2012 · 1 comment

Comments

@polka
Copy link

polka commented Feb 5, 2012

in a rails3.1.3 app the installation rails g dresscode:install finishes fine. but if i do a bundle in $dresscode/bundle it will cancel with >>

Bundler could not find compatible versions for gem "rails":
In Gemfile:
dresscode (>= 0) ruby depends on
rails (~> 3.1.0) ruby

dresscode (>= 0) ruby depends on
  rails (3.2.1)

my Gemfile
source "http://rubygems.org"

gem 'dc_contactform', :path => 'dc_addons/dc_contactform'

group :test do
gem 'rspec-rails'
gem 'factory_girl'
gem 'capybara'
gem 'spork'
gem 'shoulda-matchers'

gem 'guard-rspec'
gem 'guard-spork'

gem 'database_cleaner'

gem 'selenium-webdriver'

gem 'capybara-webkit'

end

gemspec
<<EOF

can u reconstruct my issue ??

its essential to bundle to fire up tests directly out of the gem. i think its unacceptable to run acceptance tests ((lol) or others) from a seperate app.

if i use a rails 3.2.x app i got the error>> undefined method mass_assignment_sanitizer= which should be able to neutralize if you comment it out in development.rb. but in my case there is nothing to comment out.

any ideas????

@polka
Copy link
Author

polka commented Feb 13, 2012

fixed if you dont specify the version number of rails.
inexplicable why the min version greather than wont work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant