Forum: Ruby ruby 1.8.8dev stable snapshot?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Aaa24974425d6542198c2ae0b5f9c49a?d=identicon&s=25 benr75 (Guest)
on 2009-03-12 02:55
(Received via mailing list)
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:in `new'
  from /home/deploy/src/rubygems-1.3.1/lib/rubygems.rb:676:in
`ruby_version'
  from setup.rb:111
86e33dee4a89a8879a26487051c216a8?d=identicon&s=25 Michael Fellinger (Guest)
on 2009-03-13 03:11
(Received via mailing list)
On Thu, Mar 12, 2009 at 10:52 AM, benr75 <benr75@gmail.com> 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:in `new'
>        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 :)
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
58479f76374a3ba3c69b9804163f39f4?d=identicon&s=25 Eric Hodel (Guest)
on 2009-03-16 19:52
(Received via mailing list)
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:in `new'
>   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.
Ede2aa10c6462f1d825143879be59e38?d=identicon&s=25 Charles Oliver Nutter (Guest)
on 2009-03-16 20:01
(Received via mailing list)
Eric Hodel 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
58479f76374a3ba3c69b9804163f39f4?d=identicon&s=25 Eric Hodel (Guest)
on 2009-03-16 21:16
(Received via mailing list)
On Mar 16, 2009, at 11:57, Charles Oliver Nutter wrote:
> Eric Hodel 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 Kemper:

http://rubyforge.org/tracker/index.php?func=detail...

Apparently if there's an unreleased version, RUBY_PATCHLEVEL is -1
This topic is locked and can not be replied to.