This was fixed in Debian in version 1.3.7-3 (and subsequently synced into natty), and upstream in v1.5.0
http://rubyforge.org/tracker/?func=detail&atid=577&aid=28582&group_id=126 ** Changed in: libgems-ruby (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are subscribed to Ubuntu. https://bugs.launchpad.net/bugs/643768 Title: gem build broken by recent upgrade Status in “libgems-ruby” package in Ubuntu: Fix Released Bug description: After updating my maverick system, the latest uploaded package seems to have broken the 'gem build' command: ubuntu@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@ip-10-196-111-253:~/g$ touch ~/.gemrc ubuntu@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 _______________________________________________ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
