This project is archived and is in readonly mode.
wants me to update right after a successful update.
-
pixeltarian
eek. hit enter by accident.
here's is the turn of events:
http://pastie.org/842523I don't get it. I do a 'gem install -v=2.3.5 rails' successfully, but then it tells me to do a 'gem install -v=2.3.5 rails' again. what gives?
-
Roland Moriz
Have you installed rack version 1.1.0?
Try to uninstall it (gem uninstall rack, select 1.1.0)aslo reported by: http://blog.e-thang.net/?p=76
-
Roland Moriz
another thread regarding this: http://www.ruby-forum.com/topic/201603
-
Ryan Bigg
This is a bug in config/boot.rb. I think that it rescues too broadly when it tries to do a gem 'rails'. Patch welcomed.
-
Ryan Bigg
- State changed from new to open
I think this is solved in Rails as it is Bundler that is responsible for loading the gems and is more "responsible" when it comes to outputting useful error messages. Anyone else agree?
-
Rohit Arondekar
- State changed from open to invalid
I can't recreate this and as Ryan has said, Bundler is now responsible for loading gems. Closing this ticket, if anybody is still encountering this issue please just make a comment and I'll reopen it.