[Rails] Re: After updating to Rails 2.3.2 whole enviroment broke. Help!!

2009-04-13 Thread Olaf S.
It only copied the folder vendor/rails/railties and says that my Gem folder isn't writeable, so all the other folders are missing. But when I try to reproduce this behavior everything seems to work, even though I still get some error messages: Do you have any idea what that could mean? My Gem

[Rails] Re: After updating to Rails 2.3.2 whole enviroment broke. Help!!

2009-04-11 Thread Matt Jones
There's still something weird going on - you shouldn't have to run the freeze task as root... What exactly is "incomplete" when you run it as a regular user? --Matt Jones On Apr 10, 4:34 pm, "Olaf S." wrote: > Thank you very much for your help. It was a very stupid mistake and is > solved now:

[Rails] Re: After updating to Rails 2.3.2 whole enviroment broke. Help!!

2009-04-10 Thread Olaf S.
Thank you very much for your help. It was a very stupid mistake and is solved now: After upgrading to rails I removed the /vendor/rails folder, because I freezed rails. Then I've run $ rake rails:freeze:gems to freeze the new version (2.3.2). I forgot that I had to do this as root, so the fr

[Rails] Re: After updating to Rails 2.3.2 whole enviroment broke. Help!!

2009-04-10 Thread Bharat
I am assuming that you don't have a statement like; RAILS_GEM_VERSION = '2.2.2' unless defined? RAILS_GEM_VERSION Since you were doing fine until you installed the gem in question. If you have not updated it for Rails 2.3.2 then do so and try again. If that does not work then my advice would