# Rails 3 on debian

**URL:** <https://www.ruby-forum.com/t/rails-3-on-debian/184264>\
**Category:** Rails\
**Created:** [February 27, 2010, 5:24pm UTC](https://www.ruby-forum.com/t/rails-3-on-debian/184264 "2010-02-27T17:24:11Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![kenfc](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/b782af/32.png) [@kenfc](https://www.ruby-forum.com/u/kenfc)\
**Post date:** [February 27, 2010, 5:24pm UTC](https://www.ruby-forum.com/t/rails-3-on-debian/184264/1 "2010-02-27T17:24:11Z")

</div>

Rails 3 requires bundler to be installed, but bundler can’t be installed  
on Debian lenny because the gem version 1.2 is too old, an attempt  
update is also failed, any idea?

# 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.

---

<div class="post-metadata">

**Author:** ![kenfc](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/b782af/32.png) [@kenfc](https://www.ruby-forum.com/u/kenfc)\
**Post date:** [February 27, 2010, 5:53pm UTC](https://www.ruby-forum.com/t/rails-3-on-debian/184264/2 "2010-02-27T17:53:24Z")

</div>

On Sat, Feb 27, 2010 at 8:24 AM, Ken P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Rails 3 requires bundler to be installed, but bundler can’t be installed  
> on Debian lenny because the gem version 1.2 is too old, an attempt  
> update is also failed, any idea?

Several:

1. don’t use Debian
2. don’t rely on _any_ brain-dead, perpetually out-of-date package  
management system
3. remove anything ruby/rails-related from your system and install  
fresh from source

At least, that’s what I would do… 🙂

–  
Hassan S. ------------------------ removed\_email\_address@domain.invalid  
twitter: @hassan

---

<div class="post-metadata">

**Author:** ![kenfc](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/b782af/32.png) [@kenfc](https://www.ruby-forum.com/u/kenfc)\
**Post date:** [February 27, 2010, 7:40pm UTC](https://www.ruby-forum.com/t/rails-3-on-debian/184264/3 "2010-02-27T19:40:23Z")

</div>

> 1. don’t use Debian
> 2. don’t rely on _any_ brain-dead, perpetually out-of-date package  
> management system
> 3. remove anything ruby/rails-related from your system and install  
> fresh from source
> 
> At least, that’s what I would do… 🙂
> 
> –  
> Hassan S. ------------------------ removed\_email\_address@domain.invalid  
> twitter: @hassan

Yes, Rubygems must be installed from source. Depending on your tastes,  
Ruby can also be installed from source.

Disregard 1 & 2 as they are just trolls.

---

<div class="post-metadata">

**Author:** ![kenfc](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/b782af/32.png) [@kenfc](https://www.ruby-forum.com/u/kenfc)\
**Post date:** [February 27, 2010, 7:55pm UTC](https://www.ruby-forum.com/t/rails-3-on-debian/184264/4 "2010-02-27T19:55:08Z")

</div>

On Sat, Feb 27, 2010 at 10:40 AM, Fernando P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> Disregard 1 & 2 as they are just trolls.

Au contraire - I see so many cases of people struggling with problems  
directly caused by “the Debian way” of packaging 3rd-party software  
(not just Ruby-related).

The OP’s problem is exactly that; pointing it out is hardly a “troll”.

–  
Hassan S. ------------------------ removed\_email\_address@domain.invalid  
twitter: @hassan

---

<div class="post-metadata">

**Author:** ![kenfc](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/b782af/32.png) [@kenfc](https://www.ruby-forum.com/u/kenfc)\
**Post date:** [February 28, 2010, 4:42am UTC](https://www.ruby-forum.com/t/rails-3-on-debian/184264/5 "2010-02-28T04:42:34Z")

</div>

> Yes, Rubygems must be installed from source. Depending on your tastes,  
> Ruby can also be installed from source.
> 
> Disregard 1 & 2 as they are just trolls.

what about ubuntu Linux, does it also provide out dated rails related  
resources?

---

<div class="post-metadata">

**Author:** ![kenfc](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/b782af/32.png) [@kenfc](https://www.ruby-forum.com/u/kenfc)\
**Post date:** [February 28, 2010, 7:00pm UTC](https://www.ruby-forum.com/t/rails-3-on-debian/184264/6 "2010-02-28T19:00:58Z")

</div>

Hassan, so you deploy your applications on a macbook pro, do you?

Nine out of ten apps are deployed onto a Linux machine; the majority of  
those are Ubuntu(Of course, Debian based). That means you need to figure  
out  
how to make rubygems work nicely there. You can install rubygems from  
source, or you can install upgrade\_rubygems which essentially does the  
same  
thing. Both of these circumvent the package management system; not a  
good  
idea.

The correct way to do it is to use backports. For Debian you can get to  
rubygems 1.3.4 by using this backport:  
[Debian -- Error](http://packages.debian.org/lenny-backports/rubygems1.8) (1.9 is also  
available)

Instructions on how to do it:  
[http://www.backports.org/dokuwiki/doku.php?id=instructions](http://www.backports.org/dokuwiki/doku.php?id=instructions)

Foing outside the package management system is almost always a bad move.  
As  
soon as you do that it is much more difficult to backup and replicate  
that  
machine.

Hope this helps  
-Jeremy

On Sat, Feb 27, 2010 at 11:52 AM, Hassan S. \<

---

<div class="post-metadata">

**Author:** ![kenfc](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/b782af/32.png) [@kenfc](https://www.ruby-forum.com/u/kenfc)\
**Post date:** [February 28, 2010, 7:29pm UTC](https://www.ruby-forum.com/t/rails-3-on-debian/184264/7 "2010-02-28T19:29:03Z")

</div>

On Sun, Feb 28, 2010 at 9:59 AM, Jeremy C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> Hassan, so you deploy your applications on a macbook pro, do you?

No, I develop primarily on a Mac, but I deploy (mostly) to Linux. No  
Ubuntu, though 🙂

> Both of these circumvent the package management system; not a good  
> idea.

> Foing outside the package management system is almost always a bad move. As  
> soon as you do that it is much more difficult to backup and replicate that  
> machine.

Well, that’s where we disagree; I don’t use the package management  
system for anything specific to my application. I certainly don’t need  
someone else determining that I should run some down-level hacked  
up version of the software I want.

And I see no reason that implies any problems with either backup or  
replication of a system. At least, that hasn’t been my experience.

## YMMV!

Hassan S. ------------------------ removed\_email\_address@domain.invalid  
twitter: @hassan
