[DRE-maint] [Bug 643768] Re: gem build broken by recent upgrade

[Clint Byrum]

A patch for this has been submitted upstream and in Debian, and should
be uploaded, so the fix will hopefully be included in the next sync with
Debian.

-- 
gem build broken by recent upgrade
https://bugs.launchpad.net/bugs/643768
You received this bug notification because you are subscribed to Ubuntu.

Status in “libgems-ruby” package in Ubuntu: Triaged

Bug description:
After updating my maverick system, the latest uploaded package seems to have broken the 'gem build' command:

ubuntu at ip-10-196-111-253:~/g$ gem build metadata 
ERROR:  While executing gem ... (NameError)
    uninitialized constant Gem::Specification::YAML

However, if I add a .gemrc file, it works:

ubuntu at ip-10-196-111-253:~/g$ touch ~/.gemrc
ubuntu at ip-10-196-111-253:~/g$ gem build metadata 
WARNING:  no rubyforge_project specified
WARNING:  description and summary are identical
  Successfully built RubyGem
  Name: piggy
  Version: 0.0.6
  File: piggy-0.0.6.gem

This is because the existence of the .gemrc file triggers a conditional require "yaml" in rubygems/config_file.rb

Seems this has also been seen in NetBSD

http://mail-index.netbsd.org/pkgsrc-bugs/2010/09/13/msg039540.html