Another Ruby-ng stable request; since I'm not sure if all the deptree is safe from Ruby 1.9/JRuby dependencies, please let me know if there is anything blocking this. Thanks, Diego
There are many dependencies that need to be stabled first. We won't be adding arches until ready. In addition to the depend bugs we also need net-*, mocha, coderay to be stabilized. Bugs for those will be forthcoming.
Please stabilize dev-ruby/capistrano-2.5.20 and its dependencies. Also note additional dependencies in the bugs on which this bug depends. =dev-ruby/net-ssh-gateway-1.0.1-r1 =dev-ruby/net-sftp-2.0.5 =dev-ruby/net-scp-1.0.4 =dev-ruby/capistrano-2.5.20
net-ssh-gateway-1.0.1-r1 needs newer net-ssh (>= 2.0.24) for RUBY_TARGETS=ree18. Do you want newer net-ssh stable or do you want to remove ree18 from the net-ssh-gateway stable candidate? Seems like that target doesn't make much sense anyway, considering everything else only has RUBY_TARGETS=ruby18
amd64. Curious, emerged ok. Ran test, pulled up with (in /var/tmp/portage/dev-ruby/capistrano-2.5.20/work/ruby18/capistrano-2.5.20) Jeweler (or a dependency) not available. Install it with: sudo gem install jeweler /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- mocha (LoadError) Obediently ran gentoo64 / # sudo gem install jeweler yielding Successfully installed git-1.2.5 Successfully installed bundler-1.0.13 Successfully installed jeweler-1.6.0 3 gems installed Installing ri documentation for git-1.2.5... Installing ri documentation for bundler-1.0.13... Installing ri documentation for jeweler-1.6.0... Installing RDoc documentation for git-1.2.5... Installing RDoc documentation for bundler-1.0.13... Installing RDoc documentation for jeweler-1.6.0... Re-ran it and it pulled up but without "Jeweler (or a dependency) not available. Install it with: sudo gem install jeweler" Clearly rubygems appears lacking. Ensured RUBY_TARGETS=ree18 ruby18 in /etc/make.conf and re-emerged =dev-ruby/net-ssh-gateway-1.0.1-r1. Adjusted rubygems to =dev-ruby/rubygems-1.3.7-r1 ruby_targets_ruby18 -doc -ruby_targets_jruby ruby_targets_ree18 -server in /etc/portage/package.use, re-emerged rubygems. yielding Calculating dependencies... done! >>> Verifying ebuild manifests >>> Starting parallel fetch >>> Emerging (1 of 2) dev-lang/ruby-enterprise-1.8.7.2010.02-r1 >>> Jobs: 0 of 2 complete, 1 running Load avg: 0.13, 0.11, 0.26openpty failed: 'out of pty devices' >>> Installing (1 of 2) dev-lang/ruby-enterprise-1.8.7.2010.02-r1 >>> Emerging (2 of 2) dev-ruby/rubygems-1.3.7-r1 >>> Installing (2 of 2) dev-ruby/rubygems-1.3.7-r1 This time for sure. Still pulled up at the same very early point. Missing some dependency.
Created attachment 272101 [details] the build log
Created attachment 272103 [details] my emerge --info
(In reply to comment #3) > net-ssh-gateway-1.0.1-r1 needs newer net-ssh (>= 2.0.24) for > RUBY_TARGETS=ree18. > Do you want newer net-ssh stable or do you want to remove ree18 from the > net-ssh-gateway stable candidate? Seems like that target doesn't make much > sense anyway, considering everything else only has RUBY_TARGETS=ruby18 I'd rather have a newer net-ssh, since the goal for ree18 is to keep on expanding as much as possible. We'll tackle the other dependencies on the next update. New complete list: =dev-ruby/net-ssh-2.1.3 =dev-ruby/net-ssh-gateway-1.0.1-r1 =dev-ruby/net-sftp-2.0.5 =dev-ruby/net-scp-1.0.4 =dev-ruby/capistrano-2.5.20
(In reply to comment #4) > (in /var/tmp/portage/dev-ruby/capistrano-2.5.20/work/ruby18/capistrano-2.5.20) > Jeweler (or a dependency) not available. Install it with: sudo gem install > jeweler > /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in > `gem_original_require': no such file to load -- mocha (LoadError) mocha is a test dependency of capistrano, so this should have been installed as part of the emerge process. The package in question is dev-ruby/mocha. > > Obediently ran > > gentoo64 / # sudo gem install jeweler Very bad idea. Don't believe everything a build system tells you. Ebuilds will sometimes tell you things using e.g. einfo (with nice green/yellow * in front). Anything else probably isn't a good idea. In this case the message is harmless and we don't pull in jeweler to avoid a set of meaningless and unused dependencies.
amd64 stable
!!! All ebuilds that could satisfy "=dev-ruby/test-unit-2.1.2:2[ruby_targets_ruby18]" have been masked. !!! One of the following masked packages is required to complete your request: - dev-ruby/test-unit-2.1.2 (masked by: ~x86 keyword) (dependency required by "dev-ruby/net-ssh-2.1.3[test,ruby_targets_ruby18]" [ebuild]) (dependency required by "dev-ruby/capistrano-2.5.20[test,ruby_targets_ruby18]" [ebuild]) (dependency required by "capistrano" [argument]) For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook.
(In reply to comment #10) > !!! All ebuilds that could satisfy > "=dev-ruby/test-unit-2.1.2:2[ruby_targets_ruby18]" have been masked. > !!! One of the following masked packages is required to complete your request: > - dev-ruby/test-unit-2.1.2 (masked by: ~x86 keyword) > > (dependency required by "dev-ruby/net-ssh-2.1.3[test,ruby_targets_ruby18]" > [ebuild]) > (dependency required by "dev-ruby/capistrano-2.5.20[test,ruby_targets_ruby18]" > [ebuild]) > (dependency required by "capistrano" [argument]) > For more information, see the MASKED PACKAGES section in the emerge > man page or refer to the Gentoo Handbook. Fixed by relaxing the net-ssh dependency to include test-unit-2.1.2-r1 which is already stable.
Tested on x86, all good here. USE='ruby_targets_ruby18' succeeded for =dev-ruby/capistrano-2.5.20 FEATURES= test succeeded for =dev-ruby/capistrano-2.5.20 ">=dev-ruby/net-ssh-gateway-1.0.0[ruby_targets_ruby18]" ">=dev-ruby/net-sftp-2.0.2[ruby_targets_ruby18]" ">=dev-ruby/net-scp-1.0.2[ruby_targets_ruby18]" "dev-ruby/capistrano-2.5.20[test,ruby_targets_ruby18]"
x86 stable, thanks David
ia64 stable
ppc/ppc64 done