Hi Jerome,
Thank you for your comment.
I realise now this was what I was supposed to do.
Let me describe what I did and your feedback can help me decide
whether I can continue with what I’ve done or should go back to the
backup I made before starting my experiments, using clonevdi (using
VBoxManage).
So…
What I did was:
- sudo gem update --system
- sudo gem update
- sudo gem install -v=2.3.5 rails --include-dependencies
In more detail, what happened, including some problems on the way:
-
virtualrails@jay ~ $ sudo gem update --system
[sudo] password for virtualrails:
Updating RubyGems
Updating rubygems-update
Successfully installed rubygems-update-1.3.7
Updating RubyGems to 1.3.7
Installing RubyGems 1.3.7
RubyGems 1.3.7 installed
=== 1.3.7 / 2010-05-13
NOTE:
http://rubygems.org is now the default source for downloading gems.
You may have sources set via ~/.gemrc, so you should replace
http://gems.rubyforge.org with http://rubygems.org
http://gems.rubyforge.org will continue to work for the forseeable
future.
New features:
-
gem commands
-
gem install and gem fetch now report alternate platforms when
a
matching one couldn’t be found.
-
gem contents --prefix is now the default as specified in –
help. Bug
#27211 by Mamoru T…
-
gem fetch can fetch of old versions again. Bug #27960 by Eric
Hankins.
-
gem query and friends output now lists platforms. Bug #27856 by
Greg
Hazel.
-
gem server now allows specification of multiple gem dirs for
documentation. Bug #27573 by Yuki S…
-
gem unpack can unpack gems again. Bug #27872 by Timothy Jones.
-
gem unpack now unpacks remote gems.
- –user-install is no longer the default. If you really liked it,
see
Gem::ConfigFile to learn how to set it by default. (This change
was made
in 1.3.6)
- RubyGems now has platform support for IronRuby. Patch #27951 by
Will G…
Bug fixes:
- Require rubygems/custom_require if --disable-gem was set. Bug
#27700 by
Roger P…
- RubyGems now protects against exceptions being raised by plugins.
- rubygems/builder now requires user_interaction. Ruby Bug #1040 by
Phillip
Toland.
- Gem::Dependency support #version_requirements= with a warning. Fix
for old
Rails versions. Bug #27868 by Wei Jen Lu.
- Gem::PackageTask depends on the package dir like the other rake
package
tasks so dependencies can be hooked up correctly.
RubyGems installed the following executables:
/opt/rubystack-2.0-0/ruby/bin/gem
virtualrails@jay ~ $ gem -v
1.3.7
OK: This seemed to upgrade successfully RubyGems from 1.3.5 to
Version 1.3.7
-
virtualrails@jay ~ $ sudo gem update
Updating installed gems
Updating RedCloth
Building native extensions. This could take a while…
Successfully installed RedCloth-4.2.3
Updating ZenTest
Successfully installed ZenTest-4.3.3
Updating after_commit
tcmalloc: large alloc 1349521408 bytes == (nil) @
tcmalloc: large alloc 2428973056 bytes == (nil) @
tcmalloc: large alloc 3574456320 bytes == (nil) @
tcmalloc: large alloc 4021641216 bytes == (nil) @
Successfully installed after_commit-1.0.7
Updating capistrano
Successfully installed capistrano-2.5.19
Updating cucumber
Building native extensions. This could take a while…
(:
(: (: (: (: (: (: (: (: (: (: (: (: (:
(:
(::) U P G R A D I N G (::)
Thank you for installing cucumber-0.8.3.
Please be sure to read
http://wiki.github.com/aslakhellesoy/cucumber/upgrading
for important information about this release. Happy cuking!
(: (: (: (: (: (: (: (: (: (: (: (: (: (:
(:
Successfully installed trollop-1.16.2
Successfully installed gherkin-2.0.2
Successfully installed json_pure-1.4.3
Successfully installed cucumber-0.8.3
Updating daemons
Successfully installed daemons-1.1.0
Updating delayed_job
Successfully installed delayed_job-2.0.3
Updating echoe
========================================================================
Thanks for installing Gemcutter! You can now run:
gem push merged into RubyGems 1.3.6
gem owner merged into RubyGems 1.3.6
gem webhook register urls to be pinged when gems are pushed
gem yank remove a specific version of a gem from RubyGems.org
========================================================================
Successfully installed gemcutter-0.5.0
Successfully installed echoe-4.3.1
Updating god
Building native extensions. This could take a while…
Successfully installed god-0.11.0
Updating highline
Successfully installed highline-1.5.2
Updating hoe
Successfully installed rubyforge-2.0.4
Successfully installed hoe-2.6.1
Updating memcache-client
Successfully installed memcache-client-1.8.5
Updating net-sftp
Successfully installed net-sftp-2.0.4
Updating net-ssh
Successfully installed net-ssh-2.0.23
Updating nokogiri
Building native extensions. This could take a while…
ERROR: Error installing nokogiri:
ERROR: Failed to build gem native extension.
/opt/rubystack-2.0-0/ruby/bin/ruby extconf.rb
checking for iconv.h… yes
checking for libxml/parser.h… no
libxml2 is missing. please visit
Installing Nokogiri - Nokogiri
for help with installing dependencies.
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers. Check the mkmf.log file for more
details. You may need configuration options.
Provided configuration options:
–with-opt-dir
–without-opt-dir
–with-opt-include
–without-opt-include=${opt-dir}/include
–with-opt-lib
–without-opt-lib=${opt-dir}/lib
–with-make-prog
–without-make-prog
–srcdir=.
–curdir
–ruby=/opt/rubystack-2.0-0/ruby/bin/ruby
–with-zlib-dir
–without-zlib-dir
–with-zlib-include
–without-zlib-include=${zlib-dir}/include
–with-zlib-lib
–without-zlib-lib=${zlib-dir}/lib
–with-iconv-dir
–without-iconv-dir
–with-iconv-include
–without-iconv-include=${iconv-dir}/include
–with-iconv-lib
–without-iconv-lib=${iconv-dir}/lib
–with-xml2-dir
–without-xml2-dir
–with-xml2-include
–without-xml2-include=${xml2-dir}/include
–with-xml2-lib
–without-xml2-lib=${xml2-dir}/lib
–with-xslt-dir
–without-xslt-dir
–with-xslt-include
–without-xslt-include=${xslt-dir}/include
–with-xslt-lib
–without-xslt-lib=${xslt-dir}/lib
Gem files will remain installed in /opt/rubystack-2.0-0/ruby/lib/ruby/
gems/1.8/gems/nokogiri-1.4.2 for inspection.
Results logged to /opt/rubystack-2.0-0/ruby/lib/ruby/gems/1.8/gems/
nokogiri-1.4.2/ext/nokogiri/gem_make.out
Updating passenger
ERROR: While executing gem … (Zlib::DataError)
invalid stored block lengths
Here, nokogiri didn’t upgrade… so tried the following:
- sudo apt-get install libxslt-dev libxml2-dev
sudo gem install nokogiri
Err… don’t find the trace for it but then it started complaining Zlib
and didn’t install nokogiri
- Anyway, I don’t know whether nokogiri should be of a problem…
I decided to go ahead and try to install rails 2.3.5 since as I
suspected,
sudo gem update install rails 2.3.8.
Now, wanting to give the trace here I retyped step 3
and it caused some problems…
What I’m going to do now I think is go back to my backup anyway… I’m
leaving the beginning of my message here, thinking maybe the
information about nokogiri is relevant for your information…
Anyway, since it seems I’m going to go back to my backup-version - I’m
re-asking my question:
Should I just follow your instructions and update to rails 2.3.5?
Should I refrain from doing sudo gem update --system and sudo gem
update?
Should rails 2.3.8 or any other updates cause me any trouble?
Do you recommend me to stick with rails 2.3.5 rather than 2.3.8?
Thanks!!
Sorry for the confusion in my message… my terminal seems to have
crashed from retyping step 3… as I’m really a beginner I wasn’t aware
of the fact I was doing something obviously wrong here… [blush]
Also, talking about being a newbie reminded me of another question I
have, not related to VirtualRails but to being a Linux beginner and
that is the following:
Where should I put my files and directories? and, more spcifically,
where should I put my RoR development libraries? should I create a
directory under /home/virtualrails/ or is there a different place I
should be aiming and looking into?
Many thanks,
Appreciate the answers here…
Best,
tino
