# Re: Question about Lo4R

**URL:** <https://www.ruby-forum.com/t/re-question-about-lo4r/98686>\
**Category:** Ruby\
**Created:** [January 30, 2006, 6:17am UTC](https://www.ruby-forum.com/t/re-question-about-lo4r/98686 "2006-01-30T06:17:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![zmoazeni](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/3da27b/32.png) [@zmoazeni](https://www.ruby-forum.com/u/zmoazeni)\
**Post date:** [January 30, 2006, 6:17am UTC](https://www.ruby-forum.com/t/re-question-about-lo4r/98686/1 "2006-01-30T06:17:41Z")

</div>

Looking at the RubyForge website, this seems to be an open bug.

-Zach

On Monday 30 January 2006 07:27 am, Alex C. wrote:

> $ cat /etc/lsb-release  
> DISTRIB\_ID=Ubuntu  
> DISTRIB\_RELEASE=5.10  
> DISTRIB\_CODENAME=breezy  
> DISTRIB\_DESCRIPTION=“Ubuntu (The Breezy Badger Release)”
> 
> $ ruby -v  
> ruby 1.8.3 (2005-06-23) [i486-linux]

Exactly, 1.8.3 was released on 09/21/2005. Somebody took a development  
snapshot instead of taking critical patches and declared it the ruby to  
be  
used in Ubuntu Breezy. The people who noticed the version were a bit too  
late  
and Breezy had already been frozen.

Tsume