Please test and mark stable dev-lang/ruby:1.9. This new slot has been in the tree for almost two months. dev-lang/ruby:1.8 will no longer be supported by upstream starting this summer and we want to make sure we are ready to make ruby:1.9 the primary ruby implementation at this time. Please note that will technically not a dependency, we also need to mark stable a newer version of rubygems, since ruby:1.9 blocks older versions and ruby without rubygems is not usable. =dev-lang/ruby-1.9.3_p125 =dev-ruby/rubygems-1.8.15 =virtual/rubygems-4 =virtual/ruby-minitest-0-r2 =virtual/ruby-ssl-1 =virtual/ruby-test-unit-0-r4 =virtual/ruby-threads-1
A new list with update rubygems version to ensure that we also fix bug 412901 and a few more essential packages. =dev-lang/ruby-1.9.3_p125 =dev-ruby/rubygems-1.8.24 =virtual/rubygems-4 =virtual/ruby-minitest-0-r2 =virtual/ruby-rdoc-1 =virtual/ruby-ssl-1 =virtual/ruby-test-unit-0-r4 =virtual/ruby-threads-1 =dev-ruby/rake-0.8.7-r6 =dev-ruby/rdoc-3.5.3
Updated list with a new enough rdoc for ruby 1.9: =dev-lang/ruby-1.9.3_p125 =dev-ruby/rubygems-1.8.24 =virtual/rubygems-4 =virtual/ruby-minitest-0-r2 =virtual/ruby-rdoc-1 =virtual/ruby-ssl-1 =virtual/ruby-test-unit-0-r4 =virtual/ruby-threads-1 =dev-ruby/rake-0.8.7-r6 =dev-ruby/rdoc-3.12
Apologies for the additional bugspam, but rdoc itself obviously also has dependencies that I missed in the list. Below I've created two lists, since rdoc is a PDEPEND of dev-lang/ruby. =dev-lang/ruby-1.9.3_p125 =dev-ruby/rubygems-1.8.24 =virtual/rubygems-4 =virtual/ruby-minitest-0-r2 =virtual/ruby-rdoc-1 =virtual/ruby-ssl-1 =virtual/ruby-test-unit-0-r4 =virtual/ruby-threads-1 =dev-ruby/rake-0.8.7-r6 =dev-ruby/racc-1.4.6-r1 =dev-ruby/json-1.5.4-r1 =dev-ruby/minitest-2.8.1 =dev-ruby/rubyforge-2.0.4-r2 =dev-ruby/rdoc-3.12
... and while copying the list from my notes I somehow forgot to include hoe... =dev-lang/ruby-1.9.3_p125 =dev-ruby/rubygems-1.8.24 =virtual/rubygems-4 =virtual/ruby-minitest-0-r2 =virtual/ruby-rdoc-1 =virtual/ruby-ssl-1 =virtual/ruby-test-unit-0-r4 =virtual/ruby-threads-1 =dev-ruby/rake-0.8.7-r6 =dev-ruby/racc-1.4.6-r1 =dev-ruby/json-1.5.4-r1 =dev-ruby/minitest-2.8.1 =dev-ruby/rubyforge-2.0.4-r2 =dev-ruby/hoe-2.12.5 =dev-ruby/rdoc-3.12
amd64 stable
arm stable
on x86: dev-ruby/rubygems-1.8.24 with FEATURES=test and RUBY_TARGET=jruby would like to pull in =virtual/ruby-rdoc-2. Should virtual/ruby-rdoc-2 also get marked stable on x86? But even with it, i get a test failure if i have jruby as target and emerge =dev-ruby/minitest-2.8.1 * Running test phase for jruby ... (in /var/tmp/portage/dev-ruby/minitest-2.8.1/work/jruby/minitest-2.8.1) /usr/bin/jruby -w -Ilib:bin:test:. -e 'require "rubygems"; require "minitest/autorun"; require "test/test_minitest_mock.rb"; require "test/test_minitest_benchmark.rb"; require "test/test_minitest_spec.rb"' -- Run options: --seed 46514 # Running tests: ...............................................................E.E. Finished tests in 0.349000s, 191.9771 tests/s, 644.6991 assertions/s. 1) Error: test_mock_args_does_not_raise(TestMiniTestMock): NoMethodError: unmocked method :==, expected one of [] org/jruby/RubyArray.java:1928:in `==' org/jruby/RubyHash.java:979:in `==' org/jruby/RubyArray.java:1309:in `include?' org/jruby/RubyHash.java:1236:in `each_key' ./test/test_minitest_mock.rb:73:in `test_mock_args_does_not_raise' org/jruby/RubyKernel.java:2093:in `send' org/jruby/RubyArray.java:2318:in `collect' org/jruby/RubyArray.java:2318:in `collect' org/jruby/RubyKernel.java:2093:in `send' org/jruby/RubyArray.java:1612:in `each' org/jruby/RubyProc.java:270:in `call' org/jruby/RubyProc.java:224:in `call' 2) Error: test_return_mock_does_not_raise(TestMiniTestMock): NoMethodError: unmocked method :==, expected one of [] org/jruby/RubyHash.java:979:in `==' org/jruby/RubyArray.java:1309:in `include?' org/jruby/RubyHash.java:1236:in `each_key' ./test/test_minitest_mock.rb:64:in `test_return_mock_does_not_raise' org/jruby/RubyKernel.java:2093:in `send' org/jruby/RubyArray.java:2318:in `collect' org/jruby/RubyArray.java:2318:in `collect' org/jruby/RubyKernel.java:2093:in `send' org/jruby/RubyArray.java:1612:in `each' org/jruby/RubyProc.java:270:in `call' org/jruby/RubyProc.java:224:in `call' 67 tests, 225 assertions, 0 failures, 2 errors, 0 skips rake aborted! Command failed with status (1): [/usr/bin/jruby -w -Ilib:bin:test:. -e 'req...]
(In reply to comment #7) > Should virtual/ruby-rdoc-2 also get marked stable on x86? It should already have been marked stable when jruby went stable. I've marked it stable now.
(In reply to comment #7) > on x86: > But even with it, i get a test failure if i have jruby as target and emerge > =dev-ruby/minitest-2.8.1 It looks like something got broken with newer jruby releases. We'll need a newer minitest version. New complete list: =dev-lang/ruby-1.9.3_p125 =dev-ruby/rubygems-1.8.24 =virtual/rubygems-4 =virtual/ruby-minitest-0-r2 =virtual/ruby-rdoc-1 =virtual/ruby-ssl-1 =virtual/ruby-test-unit-0-r4 =virtual/ruby-threads-1 =dev-ruby/rake-0.8.7-r6 =dev-ruby/racc-1.4.6-r1 =dev-ruby/json-1.5.4-r1 =dev-ruby/minitest-2.12.1 =dev-ruby/rubyforge-2.0.4-r2 =dev-ruby/hoe-2.12.5 =dev-ruby/rdoc-3.12
(In reply to comment #9) > It looks like something got broken with newer jruby releases. We'll need a > newer minitest version. New complete list: Thanks, that looks good now! :-) A revdep (sci-biology/bioruby) has no ruby-target support yet and only seem to work with 1.8! dev-ruby/quixml suffers from the same thing in current stable (0.2.1-r1), but 0.2.1-r2 looks good... should we also add dev-ruby/quixml-0.2.1-r2 to the list?
(In reply to comment #10) > A revdep (sci-biology/bioruby) has no ruby-target support yet and only seem > to work with 1.8! > dev-ruby/quixml suffers from the same thing in current stable (0.2.1-r1), > but 0.2.1-r2 looks good... should we also add dev-ruby/quixml-0.2.1-r2 to > the list? There has been ample warning for the new ruby version, so please continue with stabling. Also some arches are already done and I don't want to add new packages to this list unless we have to. We can file new bugs for packages that still have issues (and quixml seems to work fine for me).
x86 stable! Thank you!
ppc stable
We are now targeting a newer version of dev-lang/ruby. New complete list: =dev-lang/ruby-1.9.4_p94-r1 =dev-ruby/rubygems-1.8.24 =virtual/rubygems-4 =virtual/ruby-minitest-0-r2 =virtual/ruby-rdoc-1 =virtual/ruby-ssl-1 =virtual/ruby-test-unit-0-r4 =virtual/ruby-threads-1 =dev-ruby/rake-0.8.7-r6 =dev-ruby/racc-1.4.6-r1 =dev-ruby/json-1.5.4-r1 =dev-ruby/minitest-2.12.1 =dev-ruby/rubyforge-2.0.4-r2 =dev-ruby/hoe-2.12.5 =dev-ruby/rdoc-3.12
> =dev-lang/ruby-1.9.4_p94-r1 I think you mean here ruby-1.9.3_p194-r1 You're missing a 1 after the _p
Okay ppc64 done. Here's what was stabilized in the order that it was committed (due to unstable deps leading to repoman warnings): dev-lang/ruby-1.9.3_p194-r1 virtual/rubygems-4 virtual/ruby-minitest-0-r2 virtual/ruby-rdoc-1 virtual/ruby-ssl-1 virtual/ruby-test-unit-0-r4 virtual/ruby-threads-1 dev-ruby/rake-0.8.7-r6 dev-ruby/racc-1.4.6-r1 dev-ruby/json-1.5.4-r1 dev-ruby/rubyforge-2.0.4-r2 dev-ruby/rdoc-3.12 dev-ruby/hoe-2.12.5 dev-ruby/minitest-2.12.1 dev-ruby/rubygems-1.8.24
We are now targeting a newer version of json. New complete list: dev-lang/ruby-1.9.3_p194-r1 virtual/rubygems-4 virtual/ruby-minitest-0-r2 virtual/ruby-rdoc-1 virtual/ruby-ssl-1 virtual/ruby-test-unit-0-r4 virtual/ruby-threads-1 dev-ruby/rake-0.8.7-r6 dev-ruby/racc-1.4.6-r1 dev-ruby/json-1.6.7 dev-ruby/rubyforge-2.0.4-r2 dev-ruby/rdoc-3.12 dev-ruby/hoe-2.12.5 dev-ruby/minitest-2.12.1 dev-ruby/rubygems-1.8.24
(In reply to comment #17) > We are now targeting a newer version of json. New complete list: > You should re-add the arches that need to do that. I would never have seen that if I had not revisited the bug.
*** Bug 436878 has been marked as a duplicate of this bug. ***
We will start recommending that people select ruby 1.9 as their default ruby in a month or so. We are starting to see packages no longer supporting ruby 1.8, and ruby 1.8 is currently in end-of-life security-only support. It would be great if all remaining arches could also mark ruby 1.9 stable so we can tell the same story to everyone.
There is still bug #388123 which seems pretty grave to me. I'll test this new ruby version soon.
alpha/ia64/s390/sh/sparc stable, i believe
Stable for HPPA. Closing.
