My app doesn’t like 2.3.3 mainly due to a known bug in Rails that will
be fixed in 2.3.4
I had 2.3.2 frozen until I downloaded and tested 2.3.3
Now I want to freeze 2.3.2 back into my app but rake rails:freeze:gems
insists on unpacking 2.3.3 and an edge freeze for the 2.3.2 version
fails
C:\Development\Aptana\cloud_community>rake rails:freeze:gems
(in C:/Development/Aptana/cloud_community)
Freezing to the gems for Rails 2.3.3
rm -rf vendor/rails
mkdir -p vendor/rails
cd vendor/rails
Unpacked gem:
‘C:/Development/Aptana/cloud_community/vendor/rails/activesupport-
2.3.3’
mv activesupport-2.3.3 activesupport
Unpacked gem:
‘C:/Development/Aptana/cloud_community/vendor/rails/activerecord-2
.3.3’
mv activerecord-2.3.3 activerecord
Unpacked gem:
‘C:/Development/Aptana/cloud_community/vendor/rails/actionpack-2.3
.3’
mv actionpack-2.3.3 actionpack
Unpacked gem:
‘C:/Development/Aptana/cloud_community/vendor/rails/actionmailer-2
.3.3’
mv actionmailer-2.3.3 actionmailer
Unpacked gem:
‘C:/Development/Aptana/cloud_community/vendor/rails/activeresource
-2.3.3’
mv activeresource-2.3.3 activeresource
Unpacked gem:
‘C:/Development/Aptana/cloud_community/vendor/rails/rails-2.3.3’
cd -
C:\Development\Aptana\cloud_community>rake rails:unfreeze
(in C:/Development/Aptana/cloud_community)
rm -rf vendor/rails
C:\Development\Aptana\cloud_community>rake rails:unfreeze
(in C:/Development/Aptana/cloud_community)
rm -rf vendor/rails
C:\Development\Aptana\cloud_community>rake rails:freeze:edge
RELEASE=2.3.2
(in C:/Development/Aptana/cloud_community)
cd vendor
Downloading Rails from
http://dev.rubyonrails.org/archives/rails_2.3.2.zip
Unpacking Rails
rm -rf rails
C:/Development/InstantRails/ruby/bin/rake: No such file or directory -
unzip rai
ls.zip
rm -f rails.zip
rm -f rails/Rakefile
rm -f rails/cleanlogs.sh
rm -f rails/pushgems.rb
rm -f rails/release.rb
touch rails/REVISION_328ba3b333777bbc1269cbe0e9f590c845006c9d
rake aborted!
No such file or directory -
rails/REVISION_328ba3b333777bbc1269cbe0e9f590c845006
c9d
(See full trace by running task with --trace)
Any ideas how to proceed from here will be greatly appreciated.
Wap A. wrote:
follow this site instruction and do that way
http://arjunghosh.wordpress.com/2008/04/18/how-to-freeze-rails-application/
Thanks for the reply.
I think I’m missing something. I can’t see how that is telling me to do
anything different to the way’s I’m trying.
I don’t understand why the freeze:edge is failing.
On Thu, Aug 20, 2009 at 3:24 AM, James W. <
[email protected]> wrote:
I don’t understand why the freeze:edge is failing.
What platform are you on and what you’re typing at the command prompt?
Also,
what are the exact error message(s) you’re receiving?
-Conrad
Conrad T. wrote:
On Thu, Aug 20, 2009 at 3:24 AM, James W. <
[email protected]> wrote:
I don’t understand why the freeze:edge is failing.
What platform are you on and what you’re typing at the command prompt?
Also,
what are the exact error message(s) you’re receiving?
-Conrad
Hi Conrad,
As per my OP this is a copy of the command line I use
C:\Development\Aptana\cloud_community>rake rails:freeze:edge
RELEASE=2.3.2
(in C:/Development/Aptana/cloud_community)
cd vendor
Downloading Rails from
http://dev.rubyonrails.org/archives/rails_2.3.2.zip
Unpacking Rails
rm -rf rails
C:/Development/InstantRails/ruby/bin/rake: No such file or directory -
unzip rai
ls.zip
rm -f rails.zip
rm -f rails/Rakefile
rm -f rails/cleanlogs.sh
rm -f rails/pushgems.rb
rm -f rails/release.rb
touch rails/REVISION_328ba3b333777bbc1269cbe0e9f590c845006c9d
rake aborted!
No such file or directory -
rails/REVISION_328ba3b333777bbc1269cbe0e9f590c845006
c9d
(See full trace by running task with --trace)
I’m using windows XP SP3.
I was able to get a copy of the vendors folder from my git repository so
I have gotten round the problem by overwriting my local copy eith this
but it’s bothering me that I no longer seem to be able to freeze rails
properly.
I checked the permissions on the rails installation folders and there
were some read only folders in there which I set to fuill access
recursively just in case it was a permissions thing but this made no
difference
2009/8/20 James W. [email protected]:
 Also,
Downloading Rails from
rm -f rails/release.rb
I have gotten round the problem by overwriting my local copy eith this
but it’s bothering me that I no longer seem to be able to freeze rails
properly.
I checked the permissions on the rails installation folders and there
were some read only folders in there which I set to fuill access
recursively just in case it was a permissions thing but this made no
difference
I am not sure but here is a suggestion. First lock your application to
2.3.2 by putting this at the beginning of environment.rb (watch out in
case there is already a line setting this up)
RAILS_GEM_VERSION = ‘2.3.2’ unless defined? RAILS_GEM_VERSION
Check the app still runs.
Now if you do
rake rails:freeze:gems
I hope it will freeze 2.3.2 in.
Colin
Colin L. wrote:
I am not sure but here is a suggestion. First lock your application to
2.3.2 by putting this at the beginning of environment.rb (watch out in
case there is already a line setting this up)
RAILS_GEM_VERSION = ‘2.3.2’ unless defined? RAILS_GEM_VERSION
Check the app still runs.
Now if you do
rake rails:freeze:gems
I hope it will freeze 2.3.2 in.
Colin
Thanks Colin.
The environment.rb is set to 2.3.2 as you suggested. I kinda expected
that a freeze gems would take this into account but sadly that is not
the case.
Tnis is till plaguing me. Does anyone have any ideas at all?
2009/8/21 James W. [email protected]:
Check the app still runs.
Now if you do
rake rails:freeze:gems
I hope it will freeze 2.3.2 in.
Colin
Thanks Colin.
The environment.rb is set to 2.3.2 as you suggested. I kinda expected
that a freeze gems would take this into account but sadly that is not
the case.
If you have the line in environment.rb then it should use 2.3.2
without having to freeze it in. Delete any rails directory in /
vendor in your application and try the app. If it is not using 2.3.2
there is something odd going on. Are you sure there is not a typo in
the version line in environment.rb?
Colin
Colin L. wrote:
If you have the line in environment.rb then it should use 2.3.2
without having to freeze it in. Delete any rails directory in /
vendor in your application and try the app. If it is not using 2.3.2
there is something odd going on. Are you sure there is not a typo in
the version line in environment.rb?
Colin
It does use 2.3.2 locally but I need to freeze this in for deployment.
Maybe I could uninstall 2.3.3 somehow then it would revert back to using
2.3.2 on a gems freeze?
I dunno, I’m clutching at straws here.
Really appreciate the ideas.
2009/8/22 James W. [email protected]:
It does use 2.3.2 locally but I need to freeze this in for deployment.
Maybe I could uninstall 2.3.3 somehow then it would revert back to using
2.3.2 on a gems freeze?
I dunno, I’m clutching at straws here.
Try this
rake VERSION=2.3.2 rails:freeze:gems
Colin
Colin L. wrote:
2009/8/22 James W. [email protected]:
It does use 2.3.2 locally but I need to freeze this in for deployment.
Maybe I could uninstall 2.3.3 somehow then it would revert back to using
2.3.2 on a gems freeze?
I dunno, I’m clutching at straws here.
Try this
rake VERSION=2.3.2 rails:freeze:gems
Colin
AWwesome 
Worked like a dream.
How on earth did you find that out? and thank you very much