David Heinemeier Hansson: you can install Rails 2.2 through RubyGems. We now require RubyGems 1.3.1, so be sure to update that first
$ gem -v
$ gem update --system
ERROR: While executing gem ... (RuntimeError)
gem update --system is disabled on Debian. RubyGems can be updated \
using the official Debian repositories by aptitude or apt-get
$ wget http://rubyforge.org/frs/download.php/45905/rubygems-1.3.1.tgz
$ tar xzf rubygems-1.3.1.tgz
$ cd rubygems-1.3.1
$ sudo ruby setup.rb
$ gem -v
$ sudo gem install rails
Successfully installed rake-0.8.3
Successfully installed activesupport-2.2.2
Successfully installed activerecord-2.2.2
Successfully installed actionpack-2.2.2
Successfully installed actionmailer-2.2.2
Successfully installed activeresource-2.2.2
Successfully installed rails-2.2.2
7 gems installed
Installing ri documentation for rake-0.8.3...
Installing ri documentation for activesupport-2.2.2...
Installing ri documentation for activerecord-2.2.2...
Installing ri documentation for actionpack-2.2.2...
Installing ri documentation for actionmailer-2.2.2...
Installing ri documentation for activeresource-2.2.2...
Installing RDoc documentation for rake-0.8.3...
Installing RDoc documentation for activesupport-2.2.2...
Installing RDoc documentation for activerecord-2.2.2...
Installing RDoc documentation for actionpack-2.2.2...
Installing RDoc documentation for actionmailer-2.2.2...
Installing RDoc documentation for activeresource-2.2.2...
On Ubuntu this worked for me:
sudo gem install rubygems-update
Upgrading using apt-get install rubygems on 8.10 only brings you up to 1.2.0.
Using update_rubygems directly on a virgin 8.10 system doesn’t work for me, but does provide an alternate means to get access to a setup.rb that does do the trick.
$ sudo gem install update_rubygems
$ sudo update_rubygems
sudo: update_rubygems: command not found
$ sudo /var/lib/gems/1.8/gems/rubygems-update-1.3.1/bin/update_rubygems
Error: Cannot find RubyGems Update Path!
RubyGems has already been updated.
The rubygems-update gem may now be uninstalled.
E.g. gem uninstall rubygems-update
$ cd /var/lib/gems/1.8/gems/rubygems-update-*
$ sudo ruby setup.rb
$ gem -v
I can’t even begin to wrap my head around why Rubygems is included in any package management system. It’s well known that it doesn’t play nice with others (hence an official position statement by the Debian guys), so why include it at all? The same problem affects OS X, which includes Rubygems and a handful of gems.
So we can either install a duplicate copy in a different path, or update the old version behind the back of whichever package system you use. Both seem like pretty shitty solutions, to me. Sure it might initially be handy, but it’s pretty damn confusing the first time you upgrade.
Detail link sudo atp-get install ruby rubygems setup http_proxy env, if you gem update through proxy http_proxy=http://proxy serverIP:80/;export http_proxy you can vi .profile for current user $ sudo gem install update_rubygems $ cd...
Even you are using Ubuntu Intrepid Ibex 8.10, better to downgrade from Ruby 1.8.7 to 1.8.6, as usufull for more production servers for today.
I have written the article about smart downgrade by using repo from Ubuntu Hardy: [link]
Instalando e usando o Capistrano no Ubuntu Linux - Parte 1
Hoje resolvemos testar o Capistrano  como nova solução para fazer deploy automático das nossas aplicações web do Labase . Partindo de um Ubuntu 8.04 sem o Ruby  instalado, o procedimento é o seguinte: $ sudo apt-get install ruby irb rdoc...
I am current using Ubuntu 8.10. For me, if I ran the commands, rubygems would stay at 1.2 even though it looked like it “updated successfully” If you are trying to update ruby gems on Ubuntu, you may need to install it manually. Sam Ruby has a good...
Some time ago Rails 2.2 was released. Since than the framework requires rubygems 1.3.1 to run. Unfortunately Ubuntu 8.10 only has rubygems 1.2.0 in its repositories. A quick google search didn’t yield a good solution for this. Everyone is...
Another anecdote about my inability to handle Ubuntu for the delight of the knowledgeable readers: Since gem 1.3.1 is not out for Ubuntu, rails won’t start the server. Therefore I tried to manually update gem. And since gem 1.3.1 has a totally...
우분투를 가지고 노는 재미가 쏠쏠하다.. windows xp 는 쓰면서도 살짝 재미는 없었는데.. 우분투는 새로운 OS라 좀 재밌는 것 같다.. 아직도 windows 사용하니? (내가 쓴말이지만 와.. 이거 진짜 웃긴다.. ㅡㅡ;;) 하면서 살짝 자랑같이 말하고 싶기도 하지만.. ㅡㅡ;; 그럴려면 꽤 많은 시간이 필요할 듯 하다.. ㅡㅡ;; (이게 젤 삽질 안하는 리눅스라니.. 그나마 다행)...
On Debian some common gems like rails are packaged, these go in the standard debian gem home of /var/lib/gems and is the setup for gem 1.2.0.
When you do the /var/lib/gems/1.8/bin/update_rubygems to go to 1.3.1 the update will ignore the debian gem home and use a combination of /usr/lib/gem and $HOME/.gem as the GEM_PATHs so any gems installed via apt-get or updated by the debian system will not be seen by gem list thereafter. The GEM_PATH is realised by ruby code somewhere in the 1.3.1 ruby codebase. I have read posts where debian maintainers complain about this.
If you read default.rb (I am not at my ubuntu box as I write this) it seems that the rubygems guys know about the debian /var/lib/gem path but don’t adjust the GEM_PATH to include the debian path. We are, at the moment, pawns in a game between debian maintainers and rubygems devs. I am going to try a .bashrc solution that tries to append the debian path to the output of ‘gem env path’. On a dev box, I hate having to do sudo gem install to get gems for user space stuff.
I think that on a debian box it should be like this...
sudo gem install xxx puts the gem in /var/lib/gem/... (if the gem exists in $HOME/.gem/ then move it to /var/lib/gem)
gem install xxx puts the gem in $HOME/.gem/ (unless the gem already exists in /var/lib/gem)
Community Engine es un plugin de Ruby On Rails . En otras palabras, es una extensión de Redes Sociales para un Framework Web programado por completo en Ruby . Y Ruby, es un lenguaje de programación derivado de SmallTalk , con lo que quienes saben...
Answer by pierr for Any other ways to install heroku except gem install
Updating the gem to version 1.3.6 seem solve the problem. However, gem update --system does not work on Ubuntu platforms, and apt-get install rubygems1.8 always bring you to version 1.2.0 . Here is the trick to update your gems to latest one,1.3.6,...
nstalling from behind a proxy If you are installing from behind a proxy, be sure to add the following to the end of any gem install or gem update command: -p http: //your-proxy-server-name:your-proxy-server-port For example, if your proxy server...