[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

Updating Ruby 1.8.6 to 1.8.6-p287 in Debian 4

The Neurochild

10/12/2008 7:14:00 AM

Hi

I have a Debian 4 machine with Ruby 1.8.6 (installed from source) and
some gems including Rails 2.1 and Phusion Passenger 2.0.3 (mod_rails,
which needs fastthread and rack gems). I want to update to the latest
patch of that version (1.8.6-p287), but I have my concerns. Can I do
it safely? Is there any warning, any catch? Will I have to reinstall
RubyGems and every single gem? What's your advice before patching?
Will all the dependent apps be screwed up? I'm asking this because,
unfortunately, there's no "make uninstall" command after installing
Ruby from source... Really! I tried, but failed miserably. The only
choice I see is to erase the folder where it's located, I doubt
installing the patch overwrites all the files.

Any suggestion is welcomed. Later...

Juan "The Neurochild" Escajadillo
20 Answers

Bill Kelly

10/12/2008 7:55:00 AM

0


From: "The Neurochild" <neurochild@gmail.com>
>
> I have a Debian 4 machine with Ruby 1.8.6 (installed from source) and
> some gems including Rails 2.1 and Phusion Passenger 2.0.3 (mod_rails,
> which needs fastthread and rack gems). I want to update to the latest
> patch of that version (1.8.6-p287), but I have my concerns. Can I do
> it safely? Is there any warning, any catch? Will I have to reinstall
> RubyGems and every single gem? What's your advice before patching?
> Will all the dependent apps be screwed up? I'm asking this because,
> unfortunately, there's no "make uninstall" command after installing
> Ruby from source... Really! I tried, but failed miserably. The only
> choice I see is to erase the folder where it's located, I doubt
> installing the patch overwrites all the files.

Hi,

On Debian, I always build ruby from source, but I install it in
/opt .

This avoids any conflict with apt/dpkg.

E.g.

/configure --prefix=/opt --enable-shared

Since you are updating from 1.8.6 to a later version of 1.8.6,
you can probably keep your gems.


Regards,

Bill

Brian Candler

10/12/2008 9:19:00 AM

0

The Neurochild wrote:
> I have a Debian 4 machine with Ruby 1.8.6 (installed from source) and
> some gems including Rails 2.1 and Phusion Passenger 2.0.3 (mod_rails,
> which needs fastthread and rack gems). I want to update to the latest
> patch of that version (1.8.6-p287)

Do you have a particular reason to do this?

I only ask because there have been bad problems with Rails running under
Ruby released versions later than p114. I'm not sure if p287 has fixed
them all (perhaps others can comment on this). If you want stability in
production, and your distribution has a p111 or p114 plus just the
security patches, then personally I'd stick with that.

Unfortunately there is no official "stable" branch of Ruby at present -
that is, one which receives security fixes only. The 1.8.6 branch has
received a number of "enhancements" which have turned out to break
things. It's therefore up to the distro maintainers to provide their own
"stable" version of Ruby.
--
Posted via http://www.ruby-....

The Neurochild

10/12/2008 4:29:00 PM

0

> Do you have a particular reason to do this?
>
> I only ask because there have been bad problems with Rails running under
> Ruby released versions later than p114. I'm not sure if p287 has fixed
> them all (perhaps others can comment on this). If you want stability in
> production, and your distribution has a p111 or p114 plus just the
> security patches, then personally I'd stick with that.

I understand your point of view, but as you can see, I have the first
release (patch level 0), so I'm very concerned. Debian only has v.
1.8.5, and I'm also working with Rails 2.1. I always pass through the
Ruby website and didn't know the importance of the patch but now.

I don't know if Rails will break, but it didn't die on me. I'm going
to install the recent version tomorrow. Wish me luck because I'm going
armed to the teeth.

Later.

The Neurochild

Erik Hollensbe

10/12/2008 4:42:00 PM

0

The Neurochild wrote:
>> Do you have a particular reason to do this?
>>
>> I only ask because there have been bad problems with Rails running under
>> Ruby released versions later than p114. I'm not sure if p287 has fixed
>> them all (perhaps others can comment on this). If you want stability in
>> production, and your distribution has a p111 or p114 plus just the
>> security patches, then personally I'd stick with that.
>
> I understand your point of view, but as you can see, I have the first
> release (patch level 0), so I'm very concerned. Debian only has v.
> 1.8.5, and I'm also working with Rails 2.1. I always pass through the
> Ruby website and didn't know the importance of the patch but now.

# apt-get install checkinstall

then:

# ./configure <options, make sure to set the "postfix the binary with
the version" option>
# make
# checkinstall

checkinstall will ask you several questions about your package, and then
run 'make install' but instead of putting it into your normal filesystem
it will install it into a faked fs. then, it will build a .deb out of
the contents.

HTH.

-Erik
--
Posted via http://www.ruby-....

Ken Bloom

10/12/2008 6:08:00 PM

0

On Sun, 12 Oct 2008 11:41:58 -0500, Erik Hollensbe wrote:

> The Neurochild wrote:
>>> Do you have a particular reason to do this?
>>>
>>> I only ask because there have been bad problems with Rails running
>>> under Ruby released versions later than p114. I'm not sure if p287 has
>>> fixed them all (perhaps others can comment on this). If you want
>>> stability in production, and your distribution has a p111 or p114 plus
>>> just the security patches, then personally I'd stick with that.
>>
>> I understand your point of view, but as you can see, I have the first
>> release (patch level 0), so I'm very concerned. Debian only has v.
>> 1.8.5, and I'm also working with Rails 2.1. I always pass through the
>> Ruby website and didn't know the importance of the patch but now.
>
> # apt-get install checkinstall
>
> then:
>
> # ./configure <options, make sure to set the "postfix the binary with
> the version" option>
> # make
> # checkinstall
>
> checkinstall will ask you several questions about your package, and then
> run 'make install' but instead of putting it into your normal filesystem
> it will install it into a faked fs. then, it will build a .deb out of
> the contents.
>
> HTH.
>
> -Erik

You don't want to do that in this case because there are a whole bunch of
Ruby packages in Debian that will be replaced by one if you do this, and
wierd unexplained packaging conflicts will abound if you try to install
one of those parts of ruby in conjunction with your own package.

Since you're running Debian Stable, why don't you just upgrade to 1.8.7
from backports.org.

Instructions are at http://backports.org/dokuwiki/doku.php?id=in...

--
Chanoch (Ken) Bloom. PhD candidate. Linguistic Cognition Laboratory.
Department of Computer Science. Illinois Institute of Technology.
http://www.iit.edu...

Ken Bloom

10/12/2008 6:11:00 PM

0

On Sun, 12 Oct 2008 02:13:33 -0500, The Neurochild wrote:

> Hi
>
> I have a Debian 4 machine with Ruby 1.8.6 (installed from source) and
> some gems including Rails 2.1 and Phusion Passenger 2.0.3 (mod_rails,
> which needs fastthread and rack gems). I want to update to the latest
> patch of that version (1.8.6-p287), but I have my concerns. Can I do it
> safely? Is there any warning, any catch? Will I have to reinstall
> RubyGems and every single gem? What's your advice before patching? Will
> all the dependent apps be screwed up? I'm asking this because,
> unfortunately, there's no "make uninstall" command after installing Ruby
> from source... Really! I tried, but failed miserably. The only choice I
> see is to erase the folder where it's located, I doubt installing the
> patch overwrites all the files.
>
> Any suggestion is welcomed. Later...
>
> Juan "The Neurochild" Escajadillo

Upgrade to 1.8.7 from backports.org
There will be no need to reinstall rubygems or your gems, though some C
extensions that work with internal structures in the ruby interpreter may
require reinstallation. (I don't have a list of what would, but let's
just say those are few and far between.)

--Ken

--
Chanoch (Ken) Bloom. PhD candidate. Linguistic Cognition Laboratory.
Department of Computer Science. Illinois Institute of Technology.
http://www.iit.edu...

Brian Candler

10/12/2008 7:24:00 PM

0

Is there general consensus on the stability of 1.8.7pXXX with Rails?
Anyone running it in large-scale production?

1.8.7 backports a number of new features from 1.9, which concerns me
somewhat, but my biggest concern is how well it's been tested with
Rails.

Thanks,

Brian.
--
Posted via http://www.ruby-....

Ryan Davis

10/12/2008 10:03:00 PM

0


On Oct 12, 2008, at 12:23 , Brian Candler wrote:

> Is there general consensus on the stability of 1.8.7pXXX with Rails?
> Anyone running it in large-scale production?

I wouldn't touch it with a 10 foot pole for production. Esp not for
rails. I think that was terrible advice.

Ken Bloom

10/12/2008 10:49:00 PM

0

On Sun, 12 Oct 2008 17:03:23 -0500, Ryan Davis wrote:

> On Oct 12, 2008, at 12:23 , Brian Candler wrote:
>
>> Is there general consensus on the stability of 1.8.7pXXX with Rails?
>> Anyone running it in large-scale production?
>
> I wouldn't touch it with a 10 foot pole for production. Esp not for
> rails. I think that was terrible advice.

I don't know Rails, but I do know Debian (and ruby). Using checkinstall
for something that's in Debian's archives is as bad (if not worse) advice
than using 1.8.7 for Rails, especially given that Ruby is broken up into
several packages the way it is.

--
Chanoch (Ken) Bloom. PhD candidate. Linguistic Cognition Laboratory.
Department of Computer Science. Illinois Institute of Technology.
http://www.iit.edu...

The Neurochild

10/13/2008 12:22:00 AM

0

I don't install v.1.8.7 yet because of it's not as "stable" as v.
1.8.6. My guide is the version of the One-Click Installer for
Windows... Mostly. I saw they have the 1.8.6-27 Release Candidate 1
with the latest patchlevel of Ruby.

Even Ruby Enterprise Edition stick to v.1.8.6. The latest version was
released in August 10th, meaning they have the latest patchlevel.

While the companies and project don't make the jump to v.1.8.7, I
won't either.

I'm also eager to test REE as someone told me on another thread, but
I'm already stuck to the original Ruby despite its benefits with
Passenger. Maybe I'll test it on my computer to see if it's worth it
on my job.

Tomorrow I'll post my opinion of what happened with the installation
of Ruby v.1.8.6-p287.

Later...

The Neurochild