similar to: rails 1.1: fix to ''rake rails:freeze:gems''

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''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, 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

Hi All, Not sure if this is a bug or expected behavior. I''ve pasted my log below, but basically the first time that I run rake rails:freeze:gems, I get action* all unpacked into app/vendor/ rails.....the 2nd time I run it? I only get vendor/railties/* Something I''ve done wrong? Thanks, Dale ---- log ----- ~/cygwin/test$ rake rails:freeze:gems (in C:/Documents and

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,

Hi all. I keep having the following error when I invoke the rake db:migrate command for Rails 1.1 (Ruby 1.8.2 -- Windows 2000) ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate == Realtorex: migrating ======================================================= -- create() rake aborted! undefined method `create'' for

Hi all, I''m wondering if "rake freeze_gems" will freeze SwitchTower as well. If it doesn''t, I could try to modify the rake task at [1] to freeze extra gems such as switchtower into vendor/ (the rake task at [1] freezes gems into lib/ which I disagree with). Is there anyone else actually using a "frozen" SwitchTower? If so, what did you do to freeze it with a

Running rake rails:freeze:gems I got the following error: [root@WiNN-Mesh web_interface]# /usr/local/bin/rake rails:freeze:gems --trace (in /usr/sbin/web_interface) ** Invoke rails:freeze:gems (first_time) ** Execute rails:freeze:gems Freezing to the gems for Rails 1.2.5 rm -rf vendor/rails mkdir -p vendor/rails cd vendor/rails rake aborted! uninitialized constant Gem::GemRunner

My understanding is that the "rails:freeze:gems" task copies the Rails source into the application''s vendor directory. Which is why I find the following error surprising and confusing, because the task should not involve writing to system files or directories: % rake rails:freeze:gems (in /Users/tallen/apps/pnc) Freezing to the gems for Rails 2.3.5 rm -rf vendor/rails mkdir -p

I am developing with rails at three platform mac, windows, linux. until Rails 2.1, we can describe gem dependencies in environment.rb. ( this one ~ http://ryandaigle.com/articles/2008/4/1/what-s-new-in-edge-rails-gem-dependencies ) so I write environment.rb like below for using will_paginate ... config.gem ''capistrano'' config.gem

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

Freezing to 1.2.6 appears to be broken right now for two reasons. My environment is using rails 1.2.6 and rubygems 0.9.5 Attempting to freeze to 1.2.6 with this will result in this output & error: % rake rails:freeze:edge TAG=rel_1-2-6 ... ** Invoke rails:freeze:edge (first_time) ** Execute rails:freeze:edge A vendor/rails/railties . . . A vendor/rails/activesupport/MIT-LICENSE

Hello all, I just did a first time ruby enterprise edition, installed some gems, and now I''m trying to do a '' sudo ./rake gems:install'' and getting a: rake aborted! No Rakefile found error. Firstly, what directory should I be doing this from? -- View this message in context:

Freezing to the gems for Rails 1.2.6 rake aborted! uninitialized constant Gem::GemRunner tracing gives: no such file to load -- /Users/nathany/Sites/boat/oat/config/../vendor/ rails/railties/lib/initializer /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `gem_original_require'' ... which seems like it may be trying to load the frozen gems before they are there? It

I''m use Ruby 1.9 via rvm and Rails 2.3.3. I''m on OS X 10.5 and I have the mysql 2.8.1 gem installed. When I run rake on my rails app, I get the error "wrong argument type Mysql (expected Struct)". I can run the app fine with script/server and script/console fine. Is anyone else having this problem or know what might cause this problem? Here''s the stack

Anyone know what''s going on here? Every time I rune rake freeze_gems it complains that I don''t have rails installed. freeze_edge won''t work either. catalog1# rake freeze_gems (in /usr/local/cart/ast/rails) rm -rf vendor/rails mkdir -p vendor/rails Unpacked gem: ''actionpack-1.9.1'' Unpacked gem: ''activerecord-1.12.2'' Unpacked gem:

This is interesting. The default rspec rake tasks generated by Hoe give you an rspec.rake file that looks like: > begin > require ''spec'' > rescue LoadError > require ''rubygems'' > require ''spec'' > end > So far so good. When you invoke rake to do something, say check_manifest > rake check_manifest > You

Hi there, Running doc:rails and doc:rerails on a fresh rails directory after running ''rake freeze_gems'' fail with the following error: > Don''t know how to build task ''vendor/rails/activesupport/README'' Should it work? That file doesn''t seem to exist. If that''s not the sequence for generating the api documentation, what

Hi, I''m sure I''m doing something stupid, but I can''t figure this one out. I want the edge rails docs (I''m using svn:externals for vendor/rails to get edge rails). Running ruby 1.8.4, and edge rails. Tried on linux and OS X. ''rake doc:app'' and ''rake doc:plugins'' works fine, but when I run ''rake

Hello all, I''m kinda going through a rocky upgrade to rails 1.1 and I can''t find much on google about this. When I run my tests I get this: $ rake (in /home/www/art2) /usr/bin/ruby -Ilib:test "/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake/rake_test_loader.rb" "test/functional/panoramas_controller_test.rb"