i hope the ruby maintainer for debian frequents this list since i'd like to ask when will the ruby deb package be updated to ruby1.8.3 (it is still 1.8.2).
or do i have to worry about security? This server will host (hopefully) ror.
thanks and kind regards -botp
ps: don't ask, i'm an apt-spoiled brat so compiling will be last resort 
Selon "Pe帽a, Botp" <botp@delmonte-phil.com>:
i hope the ruby maintainer for debian frequents this list since i'd like to
ask when will the ruby deb package be updated to ruby1.8.3 (it is still
1.8.2).
Disclaimer: I'm not the ruby package maintainer, nor any package maintainer,
just another Rubyist using Debian (as a desktop, so I'm happy with unstable 
).
It is already at 1.8.3 in unstable, so I'd guess you'll only have to wait a
month or two if you're running testing. If you are running stable, then the
bets are off. It's not only about security, it's also about running well with
everything else in the distribution, and in all the platforms that Debian
supports. Also, IIRC in stable version numbers are frozen, unless a security
issue makes updating necessary. I think minor release updates do happen though,
so maybe Ruby 1.8.3 will find its way in stable before the next Debian release.
I wouldn't count too much on it though.
If your server isn't too mission-critical, you might consider running testing.
Testing is already extremely stable as it is, and the only problem that was the
lack of security updates has now been solved. For a non-mission-critical server,
I believe Debian testing is now a valid choice, and it stays closer to
up-to-date software than stable. It isn't cutting edge either, but for servers
that's actually a good thing . Be aware though that testing hasn't been as
much proof-tested as stable has (of course not, it *is* the playground where
all the testing for stable happens ), so you might want to be more careful
with updates then you would be with stable. Stable can safely be set on
automatic updates. Apart from security updates, I'm not sure testing can.
--
Christophe Grandsire.
http://rainbow.conlang.free.fr
It takes a straight mind to create a twisted conlang.
Ruby 1.8.3 has entered the unstable tree of Debian (sid) about 3 weeks
ago. Hopefully it will make it to the testing tree (etch) this week if
the open and resolved bugs are closed by the maintainer (Akira Yamada).
Note that Ruby 1.8.2 is present in stable (sarge) and it will remain and
that version, stable releases are (version-wise) frozen.
See also the Debian QA Package Tracking System:
http://packages.qa.debian.org/r/ruby1.8.html
I hope I have clarified it sufficiently for you.
Regards,
Paul
On Mon, Oct 17, 2005 at 07:42:41PM +0900, Pe帽a, Botp wrote:
i hope the ruby maintainer for debian frequents this list since i'd
like to ask when will the ruby deb package be updated to ruby1.8.3 (it
is still 1.8.2).
--
Student @ Eindhoven | email: paul@luon.net
University of Technology, The Netherlands | JID: paul@luon.net
Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181
Selon Christophe Grandsire <christophe.grandsire@free.fr>:
Selon "Pe帽a, Botp" <botp@delmonte-phil.com>:
> i hope the ruby maintainer for debian frequents this list since i'd like to
> ask when will the ruby deb package be updated to ruby1.8.3 (it is still
> 1.8.2).
>If your server isn't too mission-critical, you might consider running
testing.
Testing is already extremely stable as it is, and the only problem that was
the
lack of security updates has now been solved. For a non-mission-critical
server,
I believe Debian testing is now a valid choice, and it stays closer to
up-to-date software than stable. It isn't cutting edge either, but for
servers
that's actually a good thing
much proof-tested as stable has (of course not, it *is* the playground where
all the testing for stable happens
with updates then you would be with stable. Stable can safely be set on
automatic updates. Apart from security updates, I'm not sure testing can.
I forgot one thing. You might want to look at backports. There is a backport of
Ruby 1.8.2 for Woody, so there's no reason why one wouldn't be able to find one
of Ruby 1.8.3 for Sarge. I haven't found one, but that's maybe because Sarge is
still relatively new and backports when the only difference is 1 unit in the
third version number are usually not worth it.
--
Christophe Grandsire.
http://rainbow.conlang.free.fr
It takes a straight mind to create a twisted conlang.