similar to: freeze_gems and freeze_edge not working in 14.2

WinXP/ruby1.8.4/rails1.0. did a "rake freeze_gems" and got: ------ Freezing to the gems for Rails 1.0.0 rm -rf vendor/rails mkdir -p vendor/rails The filename, directory name, or volume label syntax is incorrect. The filename, directory name, or volume label syntax is incorrect. The filename, directory name, or volume label syntax is incorrect. The filename, directory name, or volume

I''m having a lot of problems with typo and rails 1.1 and I am looking for a way to revert back to 1.0 just for specific projects with problems. Is there a way to run, rake freeze_gems, and specify rails 1.0? Thanks -- Joe Clarke

Hi, I am currently experimenting on rake freeze_gems and there is something I do not understand. When I freeze_gems my app, it puts Rails in the /vendor/ directory, which works. But what about all other gems I have installed (for example Unicode, sqlite support, mysql support and so on)? The aim of freezing is to be independant of the versions of the ISP, but it seems that the server still

I installed TortoiseSVN, created a local repository at c:/instantrails/SVNRepository. I have an app that I want to put into SVN and also do a freeze_edge for, but I''m not sure how. I ran command ''rake freeze_edge'' and got the error: ERROR: Must have subversion (svn) available in the PATH to lock this application to Edge Rails rake aborted! Any advice or links to a

How do i use "rake freeze_edge" over a proxy? "rake freeze_edge -p http://...." doesnt work THanks Chris -- Posted via http://www.ruby-forum.com/.

I got these messages running ''rake freeze_edge'' in the application directory rake aborted! Don''t know how to build task ''freeze_edge'' What gives ? TIA -- Posted via http://www.ruby-forum.com/.

Hi I''m trying to deploy an app bundled with Rails 1.1 as I''m on a shared host, but it seems to be crashing out the dispatch.fcgi processes. I ran rake freeze_gems to get rails in my vendor directory (on a windows box) I added it to the svn and deployed, but got this error ./../config/environment.rb:47: uninitialized constant ActionMailer (NameError) from

(from http://pastebin.ca/44831) from a rails 1.0 app i did rake freeze_edge and rake rails:update. that went fine. when i go to the front page of my rails app I get wrong number of arguments (2 for 3) /var/www/somehost.net/site/public/../config/../vendor/rails/railties/lib/dispatcher.rb:63:in `failsafe_response''

Heya, I got the following problem on an app using memcahed. Using the latest stable release from gem install rails and lighttpd all is fine. If I do a rake freeze_edge as I want to take advantage of the latest fun, I get the following error-message at startup time. rails@lists.rubyonrails.org $ ruby script/process/respawn ..... ...

I''m having problems trying to freeze local rails gem to my app with: rake freeze_gems On OSX 10.4.6 i get the following error: Illformed requirement [=#<Gem::Specification name=rails version=1.1.0>] This is the full output: Freezing to the gems for Rails 1.1.0 rm -rf vendor/rails mkdir -p vendor/rails cd vendor/rails Unpacked gem: ''activesupport-1.3.0'' mv

Hi all- I just decided to move from my 1.1.0 to 1.1.2. I had previously frozen to 1.1.0 and therefore had all of rails in SVN in my vendor directory. When I finally got rake freeze_gems to work, it blasted (rm -rf) my vendor/rails directory and put a new one in there. This also blasted all my .svn directories. Is there some convenient way to do a freeze upgrade and play well with SVN?

Hi, I''m trying to freeze rails on a windows box and get this message(test is an rails app): C:\rails\test>rake freeze_gems (in C:/rails/test) Freezing to the gems for Rails 1.0.0 rm -rf vendor/rails mkdir -p vendor/rails The filename, directory name, or volume label syntax is incorrect. The filename, directory name, or volume label syntax is incorrect. The filename, directory name,

I''m on OS X Tiger, and just upgraded my gems. I also ran ''rake rails:update''. After that, I ran "rake freeze_gems", I recieve the following: ===================== Freezing to the gems for Rails 1.1.0 rm -rf vendor/rails mkdir -p vendor/rails cd vendor/rails Unpacked gem: ''activesupport-1.3.0'' mv activesupport-1.3.0 activesupport Unpacked

I have rails 1.0 and I cannot install rails-1.1 system-wide. However, I can freeze_edge (but just once because of svn 1.1.4 on Debian). Under this scenario, how can I create brand new rails-1.1 apps? I know how to freeze_edge *existing* rails-1.0 apps but that process seems to be imperfect because the script/about command and /rails/info/properties URL do not work after freezing to 1.1.0

I''ve been developing new application on local machine in rails 1.1.1. Hosting provider (godaddy) is at rails 1.0.0 and not upgrading any time soon I''m told. I set "RAILS_GEM_VERSION = ''1.0.0''" in my environment.rb file to get past inital errors, but now I''m getting the following error:

Running Debian 3.1, ruby 1.8.2, postgresql 7.4.x, rails-1.0 gem and rails-1.1 (rake freeze_edge). After if ''rake freeze_edge && rake rails:update'' (to rails 1.1), my unit test fails with an error attempting to create sequence table that already exists (ie. addresses_id_seq table). But if I roll back with ''rake rails:unfreeze'' (to rails 1.0), my unit

Does a rails project automatically switch to using a "local" copy of the rails libs if it exists in the vendor directory, or do I need to tweak something else to pick it up? Thanks! -Theo

Hi, rails-0.14.2/lib/initializer.rb states: # This initialization routine does nothing unless <tt>:active_record</tt> # is one of the frameworks to load (Configuration#frameworks). If it is, # this sets the database configuration from Configuration#database_configuration # and then establishes the connection. def initialize_database # code end In

Please ignore. Sorry for the garbage on the list. I had accidently pasted this at the bottom of environment.rb ActiveRecord::Base.establish_connection ouch... jh On 10/27/05, James Hughes <hughes.james-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > Hi, > > rails-0.14.2/lib/initializer.rb states: > > # This initialization routine does nothing unless

I''m using Mac OS X, I installed Ruby/Rails/lighttpd/etc via the instructions from hivelogic. I think I''ve found a bug with EdgeRails, but I''m not sure how to submit it (and maybe I''m doing something wrong and someone can just point me in the right direction). Anyway I thought I''d report it just in case it is a bug. I''ve downloaded