Created attachment 304927 [details] full build log >>> Install ruby-postgres-0.7.9.20080128-r2 into /var/tmp/portage/dev-ruby/ruby-postgres-0.7.9.20080128-r2/image/ category dev-ruby [32;01m*[0m Running install phase for ruby18 ... /usr/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:179:in `fix_syck_default_key_in_requirements': uninitialized constant Gem::SyckDefaultKey (NameError) from /usr/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:178:in `each' from /usr/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:178:in `fix_syck_default_key_in_requirements' from /usr/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:129:in `yaml_initialize' from /usr/lib/ruby/1.8/yaml.rb:133:in `transfer' from /usr/lib/ruby/1.8/yaml.rb:133:in `node_import' from /usr/lib/ruby/1.8/yaml.rb:133:in `load' from /usr/lib/ruby/1.8/yaml.rb:133:in `load' from /usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:488:in `from_yaml' from -e:1 [31;01m*[0m ERROR: dev-ruby/ruby-postgres-0.7.9.20080128-r2 failed (install phase): [31;01m*[0m Unable to generate gemspec file. [31;01m*[0m [31;01m*[0m Call stack: [31;01m*[0m ebuild.sh, line 85: Called src_install [31;01m*[0m environment, line 4041: Called ruby-ng_src_install [31;01m*[0m environment, line 3742: Called _ruby_each_implementation 'each_ruby_install' [31;01m*[0m environment, line 299: Called _ruby_invoke_environment 'ruby18' 'each_ruby_install' [31;01m*[0m environment, line 351: Called each_ruby_install [31;01m*[0m environment, line 636: Called each_fakegem_install [31;01m*[0m environment, line 611: Called ruby_fakegem_install_gemspec [31;01m*[0m environment, line 3899: Called die [31;01m*[0m The specific snippet of code: [31;01m*[0m fi ) || die "Unable to generate gemspec file."; [31;01m*[0m [31;01m*[0m If you need support, post the output of 'emerge --info =dev-ruby/ruby-postgres-0.7.9.20080128-r2', [31;01m*[0m the complete build log and the output of 'emerge -pqv =dev-ruby/ruby-postgres-0.7.9.20080128-r2'. !!! When you file a bug report, please include the following information: GENTOO_VM= CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm" JAVACFLAGS="" COMPILER="" and of course, the output of emerge --info [31;01m*[0m The complete build log is located at '/var/tmp/portage/dev-ruby/ruby-postgres-0.7.9.20080128-r2/temp/build.log'. [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/dev-ruby/ruby-postgres-0.7.9.20080128-r2/temp/environment'. [31;01m*[0m S: '/var/tmp/portage/dev-ruby/ruby-postgres-0.7.9.20080128-r2/work/ruby18/ruby-postgres-0.7.9.20080128' emerge --info output: https://bugs.gentoo.org/attachment.cgi?id=304777
I can't reproduce this. Which version of rubygems are you using?
(In reply to comment #1) > I can't reproduce this. Which version of rubygems are you using? dev-ruby/rubygems-1.8.15
Gem::SyckDefaultKey is defined in syck_hack.rb, which is loaded as part of "require 'rubygems'". I can't explain how Gem is available but not Gem::SyckDefaultKey. Probably requires some digging on your system to figure that out. Do you really need ruby-postgres? These bindings are deprecated. You might be looking for dev-ruby/pg instead.
(In reply to comment #3) > Gem::SyckDefaultKey is defined in syck_hack.rb, which is loaded as part of > "require 'rubygems'". I can't explain how Gem is available but not > Gem::SyckDefaultKey. Probably requires some digging on your system to figure > that out. > > Do you really need ruby-postgres? These bindings are deprecated. You might > be looking for dev-ruby/pg instead. i have only one, but important package, which still depends on ruby-postgres - net-analyzer/metasploit-4.2.0 with "postgres" USE flag
I've just dropped use of the yaml gemspec metadata in favour of our own more simple version. Can you try emerging it again and see if this fixes things?
