[DRE-maint] Bug#597554: rubygems1.8: gem build on yaml files produces error "uninitialized constant Gem::Specification::YAML"

[Lucas Nussbaum]

On 20/09/10 at 11:58 -0700, Clint Byrum wrote:
> Package: rubygems1.8
> Version: 1.3.7-2
> Severity: normal
> Tags: upstream
> 
> 
> Hello! 
> 
> This was originally reported in Ubuntu here:
> 
> https://bugs.launchpad.net/ubuntu/+source/libgems-ruby/+bug/643768
> 
> Upon trying to build a gem file from a raw yaml specfile,
> gem build fails:
> 
> clint at debian:~/g$ gem build metadata 
> ERROR:  While executing gem ... (NameError)
>     uninitialized constant Gem::Specification::YAML
> 
> However, if a ~/.gemrc exists, no error is printed:
> 
> clint at debian:~/g$ touch ~/.gemrc
> clint at debian:~/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
> 
> rubygems/specification.rb should explicitly require "yaml"
> 
> This was not broken in rubygems 1.3.6, and in fact has been
> reported on other OS's too:
> 
> http://mail-index.netbsd.org/pkgsrc-bugs/2010/09/13/msg039540.html

Hi Clint,

Would you have time to investigate this bug? I'm a bit out of time, but
would like to prepare a last rubygems upload for squeeze fixing at least
this issue.

- Lucas