Ruby 1.8.8dev stable snapshot?


#1

Hello ~

Went to do a routine ruby install from source, grabbed a stable
snapshot, and instead of getting an expected 1.8.7 I got:

$ ruby -v
ruby 1.8.8dev (2009-03-11)

Should this really be the STABLE snapshot? It throws up trying to
RubyGems installed:
$ sudo ruby setup.rb
Password:
/home/deploy/src/rubygems-1.3.1/lib/rubygems/version.rb:53:in
initialize': Malformed version number string 1.8.8.-1 (ArgumentError) from /home/deploy/src/rubygems-1.3.1/lib/rubygems.rb:676:innew’
from /home/deploy/src/rubygems-1.3.1/lib/rubygems.rb:676:in
`ruby_version’
from setup.rb:111


#2

On Thu, Mar 12, 2009 at 10:52 AM, benr75 removed_email_address@domain.invalid wrote:

Hello ~

Went to do a routine ruby install from source, grabbed a stable
snapshot, and instead of getting an expected 1.8.7 I got:

$ ruby -v
ruby 1.8.8dev (2009-03-11)

Should this really be the STABLE snapshot?

It’s stable, it runs and i think even the tests are passing. This
tarball is made directly from the svn repo, and the ruby version in
the repo is 1.8.8 since 1.8.7 was released already (that’s also why it
says ‘dev’).

It throws up trying to RubyGems installed:
$ sudo ruby setup.rb
Password:
/home/deploy/src/rubygems-1.3.1/lib/rubygems/version.rb:53:in
initialize': Malformed version number string 1.8.8.-1 (ArgumentError) Â Â Â Â from /home/deploy/src/rubygems-1.3.1/lib/rubygems.rb:676:innew’
    from /home/deploy/src/rubygems-1.3.1/lib/rubygems.rb:676:in
`ruby_version’
    from setup.rb:111

rubygems/version.rb doesn’t allow anything but \d and . in the
version string, so i guess this version would confuse it :slight_smile:
Don’t expect any libraries to work with a yet unreleased ruby version
if you don’t want to get down, read and understand their code and get
tweaking.

^ manveru


#3

On Mar 11, 2009, at 18:52, benr75 wrote:

$ sudo ruby setup.rb
Password:
/home/deploy/src/rubygems-1.3.1/lib/rubygems/version.rb:53:in
initialize': Malformed version number string 1.8.8.-1 (ArgumentError) from /home/deploy/src/rubygems-1.3.1/lib/rubygems.rb:676:innew’
from /home/deploy/src/rubygems-1.3.1/lib/rubygems.rb:676:in
`ruby_version’
from setup.rb:111

This is new behavior in the 1.8 branch, so RubyGems wasn’t equipped to
deal with it until last week, when I checked a fix into trunk.


#4

Eric H. wrote:

This is new behavior in the 1.8 branch, so RubyGems wasn’t equipped to
deal with it until last week, when I checked a fix into trunk.

Excellent, we’ve had this issue with JRuby too, for versions like
1.2.0RC1 or 1.3.0dev. What’s the new rules for version numbering?

  • Charlie

#5

On Mar 16, 2009, at 11:57, Charles Oliver N. wrote:

Eric H. wrote:

This is new behavior in the 1.8 branch, so RubyGems wasn’t equipped
to deal with it until last week, when I checked a fix into trunk.

Excellent, we’ve had this issue with JRuby too, for versions like
1.2.0RC1 or 1.3.0dev. What’s the new rules for version numbering?

I’m not sure what the details are, I just applied this patch from
Jeremy K.:

http://rubyforge.org/tracker/index.php?func=detail&aid=24048&group_id=126&atid=577

Apparently if there’s an unreleased version, RUBY_PATCHLEVEL is -1