From thewoolleyman at gmail.com  Tue Feb  1 01:04:04 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Mon, 31 Jan 2011 23:04:04 -0700
Subject: [Rubygems-developers] Release coming,
 but still no response on broken 1.9.x CI builds
In-Reply-To: <A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
	<2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
	<A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>
Message-ID: <AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>

On Mon, Jan 31, 2011 at 6:49 PM, Eric Hodel <drbrain at segment7.net> wrote:
>> Well... these are finally running, but they're not running properly. We had a failure on the 20th and we didn't get notified about it:
>>
>> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p378/48967276d584c52ec2e8b1a2ce9946fb3855766c
>>
>> says:
>>
>> Connection refused - connect(2) at /home/pivotal/ccrb/lib/smtp_tls.rb:76:in `initialize'

First of all, thanks a lot for the follow up and attention to the
build.  I'll try to get the floating point releases soon - but I need
to make a dedicated VPS so I can aggressively auto-update RVM to get
new interpreters.  I'm afraid to do that on this shared box with a lot
of other builds.

On the emails - I didn't want to unilaterally spam people, so you have
to opt-in to receive the emails, or turn them on for this entire list.
 I've made this easily configurable, so have at it if you want to
opt-in to the emails or want them to go to the entire list:

https://github.com/rubygems/rubygems/blob/master/cruise_config.rb#L13

As for this specific smtp_tls email failure, this appears to be a
rails bug with CCRB+some ruby versions
(https://cruisecontrolrb.lighthouseapp.com/projects/9150/tickets/209-fail-to-send-auth-tls-mail-ruby-1-8-7).
However, I am successfully receiving failure mail for all three
builds, so I think it's bogus message.  Opt-in and you should get them
too.  Feel free to temporarily break the build after you opt-in, and
let me know if you don't get an email - I'll look into it.

> They all passed except 1.9.2 which couldn't upgrade to hoe 2.9.

This is pretty funny.  The rubygems master build can't build, because
hoe can't install, because the RVM-installed rubygems is < 1.4.

I can fix this by manually upgrading rubygems, but I'm not sure what
version.  The 1.5 release notes still say to not upgrade to 1.4 on on
1.9.x - so what exact version should I install under RVM to resolve
this?

Plus, the scripted install of hoe and other gems is just a hack
because I never got an answer on how to make Hoe's check_extra_deps
not use sudo under RVM:
https://github.com/rubygems/rubygems/blob/master/ci_build.sh#L7

Thanks,
-- Chad

From thewoolleyman at gmail.com  Tue Feb  1 01:14:04 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Mon, 31 Jan 2011 23:14:04 -0700
Subject: [Rubygems-developers] Release coming,
 but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
	<2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
	<A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>
	<AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>
Message-ID: <AANLkTimztkn=9G6FMBkuUSRJ38rq-4PrGJU04VcohByK@mail.gmail.com>

On Mon, Jan 31, 2011 at 11:04 PM, Chad Woolley <thewoolleyman at gmail.com> wrote:
> I can fix this by manually upgrading rubygems, but I'm not sure what
> version. ?The 1.5 release notes still say to not upgrade to 1.4 on on
> 1.9.x - so what exact version should I install under RVM to resolve
> this?

Oops, I didn't read the whole release thread.  1.9.2 is green now with
1.5.0 rubygems installed to RVM.  It would still be great to get a
response on the other items discussed, though...

From noreply at rubyforge.org  Tue Feb  1 09:21:48 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 09:21:48 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28897 ] 1.5.0 broken on Ruby
	1.8.6
Message-ID: <20110201142148.702431858374@rubyforge.org>

Bugs item #28897, was opened at 2011-02-01 14:21
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28897&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Wincent Colaiuta (wincent)
Assigned to: Nobody (None)
Summary: 1.5.0 broken on Ruby 1.8.6

Initial Comment:
Initially reported here:

http://help.rubygems.org/discussions/problems/477

Pasting that in:

Just tested the 1.5.0 release on a couple of Linux boxes and looks like it's not compatible with Ruby 1.8.6. I get this when running sudo gem update --system:

./lib/rubygems/custom_require.rb:31:in `require': undefined method `end_with?' for "no such file to load -- Win32API":String (NoMethodError)

This is on ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-linux]. RubyGems 1.4.2 worked fine.

I gather the end_with? method was only added in Ruby 1.8.7 (tested on ruby 1.8.7 (2010-01-10 patchlevel 249) [i686-linux] and it works fine).

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28897&group_id=126

From noreply at rubyforge.org  Tue Feb  1 14:05:43 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 14:05:43 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28897 ] 1.5.0 broken on Ruby
	1.8.6
Message-ID: <20110201190543.8C3DF1858367@rubyforge.org>

Bugs item #28897, was opened at 2011-02-01 06:21
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28897&group_id=126

Category: `gem install` command
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: Wincent Colaiuta (wincent)
>Assigned to: Eric Hodel (drbrain)
Summary: 1.5.0 broken on Ruby 1.8.6

Initial Comment:
Initially reported here:

http://help.rubygems.org/discussions/problems/477

Pasting that in:

Just tested the 1.5.0 release on a couple of Linux boxes and looks like it's not compatible with Ruby 1.8.6. I get this when running sudo gem update --system:

./lib/rubygems/custom_require.rb:31:in `require': undefined method `end_with?' for "no such file to load -- Win32API":String (NoMethodError)

This is on ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-linux]. RubyGems 1.4.2 worked fine.

I gather the end_with? method was only added in Ruby 1.8.7 (tested on ruby 1.8.7 (2010-01-10 patchlevel 249) [i686-linux] and it works fine).

----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-01 11:05

Message:
Upgrade your ruby.  Ruby 1.8.6 is no longer supported per:

http://blog.segment7.net/2010/04/23/ruby-1-8-6-policy

I've updated trunk to no longer install on ruby 1.8.6, sorry we forgot that.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28897&group_id=126

From noreply at rubyforge.org  Tue Feb  1 14:07:27 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 14:07:27 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28897 ] 1.5.0 broken on Ruby
	1.8.6
Message-ID: <20110201190727.7EAB01858367@rubyforge.org>

Bugs item #28897, was opened at 2011-02-01 14:21
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28897&group_id=126

Category: `gem install` command
Group: None
Status: Closed
Resolution: Rejected
Priority: 3
Submitted By: Wincent Colaiuta (wincent)
Assigned to: Eric Hodel (drbrain)
Summary: 1.5.0 broken on Ruby 1.8.6

Initial Comment:
Initially reported here:

http://help.rubygems.org/discussions/problems/477

Pasting that in:

Just tested the 1.5.0 release on a couple of Linux boxes and looks like it's not compatible with Ruby 1.8.6. I get this when running sudo gem update --system:

./lib/rubygems/custom_require.rb:31:in `require': undefined method `end_with?' for "no such file to load -- Win32API":String (NoMethodError)

This is on ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-linux]. RubyGems 1.4.2 worked fine.

I gather the end_with? method was only added in Ruby 1.8.7 (tested on ruby 1.8.7 (2010-01-10 patchlevel 249) [i686-linux] and it works fine).

----------------------------------------------------------------------

>Comment By: Wincent Colaiuta (wincent)
Date: 2011-02-01 19:07

Message:
I already am on 1.8.7 on all machines that I do actual work 
on.

I just thought I'd let you know about the bug. Glad to hear 
you've fixed it in trunk.

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-01 19:05

Message:
Upgrade your ruby.  Ruby 1.8.6 is no longer supported per:

http://blog.segment7.net/2010/04/23/ruby-1-8-6-policy

I've updated trunk to no longer install on ruby 1.8.6, sorry we forgot that.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28897&group_id=126

From noreply at rubyforge.org  Tue Feb  1 14:27:55 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 14:27:55 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28898 ] Character set issues
	installing RubyGems 1.5.0 and documentation with Ruby 1.9.2
Message-ID: <20110201192756.085DF185836B@rubyforge.org>

Bugs item #28898, was opened at 2011-02-01 13:27
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28898&group_id=126

Category: documentation
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: mathew ! (meta)
Assigned to: Nobody (None)
Summary: Character set issues installing RubyGems 1.5.0 and documentation with Ruby 1.9.2

Initial Comment:
Installing RubyGems 1.5.0
RubyGems 1.5.0 installed
unable to convert "\xE1" from ASCII-8BIT to UTF-8 for lib/rubygems/package/tar_reader/entry.rb, skipping
unable to convert "\xE1" from ASCII-8BIT to UTF-8 for lib/rubygems/package/tar_reader/entry.rb, skipping


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28898&group_id=126

From noreply at rubyforge.org  Tue Feb  1 19:02:27 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 19:02:27 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28898 ] Character set issues
	installing RubyGems 1.5.0 and documentation with Ruby 1.9.2
Message-ID: <20110202000227.EE1FF1858396@rubyforge.org>

Bugs item #28898, was opened at 2011-02-01 11:27
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28898&group_id=126

Category: documentation
>Group: v1.5.x
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: mathew ! (meta)
>Assigned to: Eric Hodel (drbrain)
Summary: Character set issues installing RubyGems 1.5.0 and documentation with Ruby 1.9.2

Initial Comment:
Installing RubyGems 1.5.0
RubyGems 1.5.0 installed
unable to convert "\xE1" from ASCII-8BIT to UTF-8 for lib/rubygems/package/tar_reader/entry.rb, skipping
unable to convert "\xE1" from ASCII-8BIT to UTF-8 for lib/rubygems/package/tar_reader/entry.rb, skipping


----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-01 16:02

Message:
This has been fixed, thanks!

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28898&group_id=126

From noreply at rubyforge.org  Tue Feb  1 19:03:43 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 19:03:43 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-27154 ] Computed hash is
	sometimes too large.
Message-ID: <20110202000343.EFD9A1678323@rubyforge.org>

Bugs item #27154, was opened at 2009-09-21 07:42
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=27154&group_id=126

Category: `gem install` command
>Group: v1.3.x
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Ryan Riley (panesofglass)
Assigned to: John Barnette (jbarnette)
Summary: Computed hash is sometimes too large.

Initial Comment:
The current hash algorithm in dependency.rb (line 138) and specification.rb (line 658) can sometimes create a hash that is too large. This is also possible with Array#hash in MRI, which can also misbehave if one of the array elements returns a large hash value:

class C
  def hash
    100000000000000000000
  end
end

[C.new].hash  # => in `hash': bignum too big to convert into 
`long' (RangeError)

REXML has a similar issue. http://redmine.ruby-
lang.org/issues/show/1883 tracks the issue, and MRI will be 
fixing the issue.

Suggested fixes are:

edit: c:/ruby/libs/ruby/site_ruby/1.8/rubygems/dependency.rb;C840659
File: dependency.rb
===================================================================
--- c:/ruby/libs/ruby/site_ruby/1.8/rubygems/dependency.rb;C840659  (server)    6/23/2009 1:21 PM
+++ c:/ruby/libs/ruby/site_ruby/1.8/rubygems/dependency.rb
@@ -112,7 +112,7 @@
   end
 
   def hash # :nodoc:
-    name.hash + type.hash + version_requirements.hash
+    name.hash ^ type.hash ^ version_requirements.hash
   end
 
 end
===================================================================
edit: c:/ruby/libs/ruby/site_ruby/1.8/rubygems/specification.rb;C908357
File: specification.rb
===================================================================
--- c:/ruby/libs/ruby/site_ruby/1.8/rubygems/specification.rb;C908357  (server)    6/23/2009 1:24 PM
+++ c:/ruby/libs/ruby/site_ruby/1.8/rubygems/specification.rb
@@ -661,9 +661,8 @@
     private :same_attributes?
 
     def hash # :nodoc:
-      @@attributes.inject(0) { |hash_code, (name, default_value)|
-        n = self.send(name).hash
-        hash_code + n
+      @@attributes.inject(612553) { |hash_code, (name, default_value)|
+        hash_code ^ self.send(name).hash
       }
     end
 
===================================================================

----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-01 16:03

Message:
This is fixed.

----------------------------------------------------------------------

Comment By: Daniel Weaver (zlern2k)
Date: 2010-12-20 12:20

Message:
I realize these are bugs in the underlying Ruby implementation of hash, but it really helps us to have them fixed in gem.

This is the patch for requirement.rb that we currently need to deploy to make bundler happy with our apps:

zlerntop:rubygems danielweaver$ diff -u requirement.rb.orig requirement.rb
--- requirement.rb.orig	2010-12-20 12:13:40.000000000 -0800
+++ requirement.rb	2010-12-20 12:13:40.000000000 -0800
@@ -106,7 +106,7 @@
   end
 
   def hash # :nodoc:
-    requirements.hash
+    requirements.inject(0) { |h, r| h ^ r.first.hash ^ r.last.hash }
   end
 
   def marshal_dump # :nodoc:


----------------------------------------------------------------------

Comment By: George Mendoza (gsmendoza)
Date: 2010-12-06 20:06

Message:
Hello again,

I got the bignum error again, but this time with cucumber-0.9.4. These commands weren't able to install the gem:

  * bundle install
  * bundle install --local
  * sudo bundle install --local
  * sudo bundle install --local --system
  * sudo bundle install --system
  
However, I was able to work around the issue by

  1. installing the gem to my system manually (sudo gem install cucumber --version "0.9.4"), and
  2. installing the bundle to the system (sudo bundle install --system)

For step 2, trying "bundle install --local" worked only if all the gems in the bundle are already installed. If there were some gems from the bundle that are not installed, running "sudo bundle install --system" was the only way I could install them.

George Mendoza
Philippines


----------------------------------------------------------------------

Comment By: George Mendoza (gsmendoza)
Date: 2010-11-30 19:52

Message:
Hello,

Appreciate if anybody can re-open this ticket. I am also getting the error when I try to install the dmitryv-backup gem via bundle. Please let me know if I need to provide any other information in order to fix this bug. Thanks!

Gemfile:
----------------------------------------
source :rubygems
source "http://gems.github.com"

#...

gem 'dmitryv-backup', '2.4.0', :require => "backup"

#...

----------------------------------------

Running:
----------------------------------------
bundle install --local
/usr/local/lib/site_ruby/1.8/rubygems/requirement.rb:109:in `hash': bignum too big to convert into `long' (RangeError)
  from /usr/local/lib/site_ruby/1.8/rubygems/requirement.rb:109:in `hash'
  from /usr/local/lib/site_ruby/1.8/rubygems/specification.rb:675:in `hash'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/index.rb:36:in `inject'
  from /usr/local/lib/site_ruby/1.8/rubygems/specification.rb:674:in `each'
  from /usr/local/lib/site_ruby/1.8/rubygems/specification.rb:674:in `inject'
  from /usr/local/lib/site_ruby/1.8/rubygems/specification.rb:674:in `hash'
  from /usr/lib/ruby/1.8/tsort.rb:204:in `include?'
  from /usr/lib/ruby/1.8/tsort.rb:204:in `each_strongly_connected_component_from'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:130:in `tsort_each_child'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:130:in `each'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:130:in `tsort_each_child'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:128:in `each'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:128:in `tsort_each_child'
  from /usr/lib/ruby/1.8/tsort.rb:203:in `each_strongly_connected_component_from'
  from /usr/lib/ruby/1.8/tsort.rb:209:in `each_strongly_connected_component_from'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:130:in `tsort_each_child'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:130:in `each'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:130:in `tsort_each_child'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:128:in `each'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:128:in `tsort_each_child'
  from /usr/lib/ruby/1.8/tsort.rb:203:in `each_strongly_connected_component_from'
  from /usr/lib/ruby/1.8/tsort.rb:182:in `each_strongly_connected_component'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:124:in `tsort_each_node'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:124:in `each'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:124:in `tsort_each_node'
  from /usr/lib/ruby/1.8/tsort.rb:180:in `each_strongly_connected_component'
  from /usr/lib/ruby/1.8/tsort.rb:148:in `tsort_each'
  from /usr/lib/ruby/1.8/tsort.rb:135:in `tsort'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:107:in `sorted'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/spec_set.rb:12:in `each'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/installer.rb:44:in `run'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/installer.rb:8:in `install'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/cli.rb:225:in `install'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/vendor/thor/task.rb:22:in `send'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/vendor/thor/task.rb:22:in `run'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/vendor/thor/invocation.rb:118:in `invoke_task'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/vendor/thor.rb:246:in `dispatch'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib/bundler/vendor/thor/base.rb:389:in `start'
  from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/bin/bundle:13
  from /usr/bin/bundle:19:in `load'
  from /usr/bin/bundle:19
----------------------------------------

Thanks,

George Mendoza
Philippines


----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2010-11-12 14:46

Message:
This ticket has been deemed stale and we're closing it in order to catch up 
with our ticket list. If you think it is still valid, please reopen.

----------------------------------------------------------------------

Comment By: Craig Cook (ccook)
Date: 2010-10-18 14:08

Message:
Hello,

I tried this patch, but I am still getting the error, at the same place in the code.  The error is the same with or without the patch to specification.rb; dependency.rb was already like the patched part shown above.  This happened when installing using bundler, executed via capistrano.

We  had been using hpricot, it wasn't needed, it was giving this error first.  I took it out, but then the same  RangeError happened with mysql.  I've seen it before also with nokogiri.  (Always with native gems, though).

Here's the relevant part of the log:
----------- begin log ----------------------------
 ** [out :: 192.168.10.63] Installing mysql (2.8.1)
 ** [out :: 192.168.10.63] with native extensions
 ** [out :: 192.168.10.62] /usr/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:109:in `hash'
 ** [out :: 192.168.10.62] :
 ** [out :: 192.168.10.62] bignum too big to convert into `long'
 ** [out :: 192.168.10.62] (
 ** [out :: 192.168.10.62] RangeError
 ** [out :: 192.168.10.62] )
 ** [out :: 192.168.10.62] from /usr/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:109:in `hash'
 ** [out :: 192.168.10.62] from /usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:675:in `hash'
 ** [out :: 192.168.10.62] from /usr/lib/ruby/1.8/fileutils.rb:243:in `inject'
 ** [out :: 192.168.10.62] from /usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:674:in `each'
 ** [out :: 192.168.10.62] from /usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:674:in `inject'
 ** [out :: 192.168.10.62] from /usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:674:in `hash'
 ** [out :: 192.168.10.62] from /usr/lib/ruby/1.8/tsort.rb:205:in `include?'
 ** [out :: 192.168.10.62] from /usr/lib/ruby/1.8/tsort.rb:205:in `each_strongly_connected_component_from'
 ** [out :: 192.168.10.62] ... 22 levels...
 ** [out :: 192.168.10.62] from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.2/lib/bundler/vendor/thor/base.rb:389:in `start'
 ** [out :: 192.168.10.62] from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.2/bin/bundle:13
 ** [out :: 192.168.10.62] from /usr/bin/bundle:19:in `load'
 ** [out :: 192.168.10.62] from /usr/bin/bundle:19
----------- end cap output -------------------


running:
------------ system & ruby info ------------------
[ccook at ev2-stage ~]$ ruby -v
ruby 1.8.7 (2010-08-16 patchlevel 302) [i686-linux]
[ccook at ev2-stage ~]$ gem  -v
1.3.7
[ccook at ev2-stage ~]$ uname -a
Linux ev2-stage 2.6.18-194.11.4.el5xen #1 SMP Tue Sep 21 06:28:04 EDT 2010 i686 i686 i386 GNU/Linux
------ end system / ruby info  ----------

Gemfile:

----------- begin Gemfile -----------------
  source :gemcutter
             
  gem 'rails',          '2.3.8'    
  gem 'mysql',          '2.8.1'
  gem "geokit"
  gem "geokit-rails" 
  gem "builder"
  gem 'chronic'
  gem 'whenever'
  gem 'database_cleaner'       
  gem 'apn_on_rails'
  gem 'factory_girl'
  gem 'net-sftp'   
  gem 'will_paginate'    # dependency for squirrel & jqgrid
  gem 'nokogiri'           # only for test/functional/auth_controller_test.rb           
  
  gem 'cucumber'
  gem 'cucumber-rails'
  gem 'webrat'
  gem 'rspec'

---------- end Gemfile -----------------


So, is this the same issue? It sure looks like it to me.  I hope not to have to dive into the innards of rubygems if  possible.  But we need to be able to deploy.  The app is working and passing tests on development, but hard to say on staging as we can't get it over there with cap.  I suppose it could all be done by hand once anyway, but we (other dev on my team and I ) need to be able to do this over again.

Thanks for your time in this!

Cheers,
Craig

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=27154&group_id=126

From noreply at rubyforge.org  Tue Feb  1 19:04:18 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 19:04:18 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28845 ] Please move
	RubyGemTestCase to lib/
Message-ID: <20110202000418.8D69018583C0@rubyforge.org>

Bugs item #28845, was opened at 2011-01-09 19:23
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28845&group_id=126

Category: other
>Group: v1.4.x
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Erik Hollensbe (erikh)
>Assigned to: Eric Hodel (drbrain)
Summary: Please move RubyGemTestCase to lib/

Initial Comment:
Eric requested I insert this ticket.

rubygems-test could use this to perform better testing of its own suite. I will be happy to provide a pull request at a later time, but wanted to get this in here.

----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-01 16:04

Message:
This is fixed!

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28845&group_id=126

From noreply at rubyforge.org  Tue Feb  1 19:16:15 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 19:16:15 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28900 ] Cygwin: Gem::SilentUI
	tries to open Windows' NUL file
Message-ID: <20110202001615.44BD318583BE@rubyforge.org>

Bugs item #28900, was opened at 2011-02-02 00:16
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

Category: None
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: S Shaw (skye)
Assigned to: Nobody (None)
Summary: Cygwin: Gem::SilentUI tries to open Windows' NUL file

Initial Comment:
>From user_interaction.rb:

class Gem::SilentUI < Gem::StreamUI

  def initialize

    reader, writer = nil, nil

    if Gem.win_platform?
      reader = File.open('nul', 'r')
      writer = File.open('nul', 'w')
    else
      reader = File.open('/dev/null', 'r')
      writer = File.open('/dev/null', 'w')
    end

    super reader, writer, writer
  end
end

When running on cygwin Gem::SilentUI will be in a POSIX environment where the NUL file is /dev/null. 

Skye at Skye-PC ~
$ ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2008-08-11 patchlevel 72) [i386-cygwin]
-e:1:in `initialize': No such file or directory - nul (Errno::ENOENT)
        from -e:1:in `open'
        from -e:1

Skye at Skye-PC ~
$ /cygdrive/c/Ruby187/bin/ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]


RubyGems version is 1.5


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

From noreply at rubyforge.org  Tue Feb  1 19:41:24 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 19:41:24 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28837 ] `gem update` attempts
	to upgrade rubygems without using the --system flag
Message-ID: <20110202004124.137461858381@rubyforge.org>

Bugs item #28837, was opened at 2011-01-07 17:00
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28837&group_id=126

Category: `gem` commands (other)
Group: v1.4.x
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Lee Jarvis (injekt)
Assigned to: Ryan Davis (zenspider)
Summary: `gem update` attempts to upgrade rubygems without using the --system flag

Initial Comment:
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /home/injekt/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gemcutter.org

Verbose output of `gem update` can be found attached.

Even after running `gem uninstall rubygems-update`, this issue still occurs.

----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-01 16:41

Message:
RubyGems no longer attempts to upgrade rubygems itself when a newer rubygems-update is available.  It will still be downloaded and installed (which will be harmless)

----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2011-01-09 14:52

Message:
This _should_ (or at least could) be fixed on trunk. There are exactly zero tests for update --system but eric has a strategy for that so we'll get it patched up soon. In the meantime, manual verification would be great.

Just to note: we can't do a damn thing about this bug being released in 1.9... so... yeah.

----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:57

Message:
OK. I have a repro, and this is indeed a bug:

% gem uninstall -a rubygems-update
% gem install rubygems-update -v 1.3.7
% gem update -V

Extra notes:

It doesn't actually update your system, as it fails before writing anything.

It shouldn't be doing what it is doing regardless. We need to look into this asap.

----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:21

Message:
I just updated:

https://github.com/rubygems/rubygems/blob/master/UPGRADING.rdoc

with force downgrade instructions appropriate for 1.9.2 & rubygems 1.4.x.

Without a working repro, I can't address this ticket and will prolly have to reject it.

----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:19

Message:
I can't repro this at all:

% gem update -V
Updating installed gems
Nothing to update


% gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-darwin10.6.0]
  - INSTALLATION DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /Users/ryan/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-10
  - GEM PATHS:
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - "gemcutter_key" => "********************************"
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

Comment By: Lee Jarvis (injekt)
Date: 2011-01-08 01:47

Message:
Whoops! Didn't see that there. Attached.

----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2011-01-07 23:24

Message:
Not attached. Make sure you check that infernal checkbox.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28837&group_id=126

From noreply at rubyforge.org  Tue Feb  1 19:53:11 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 19:53:11 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28900 ] Cygwin: Gem::SilentUI
	tries to open Windows' NUL file
Message-ID: <20110202005311.627E91858381@rubyforge.org>

Bugs item #28900, was opened at 2011-02-01 16:16
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

Category: None
Group: v1.5.x
Status: Open
>Resolution: Accepted
Priority: 3
Submitted By: S Shaw (skye)
>Assigned to: Eric Hodel (drbrain)
Summary: Cygwin: Gem::SilentUI tries to open Windows' NUL file

Initial Comment:
>From user_interaction.rb:

class Gem::SilentUI < Gem::StreamUI

  def initialize

    reader, writer = nil, nil

    if Gem.win_platform?
      reader = File.open('nul', 'r')
      writer = File.open('nul', 'w')
    else
      reader = File.open('/dev/null', 'r')
      writer = File.open('/dev/null', 'w')
    end

    super reader, writer, writer
  end
end

When running on cygwin Gem::SilentUI will be in a POSIX environment where the NUL file is /dev/null. 

Skye at Skye-PC ~
$ ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2008-08-11 patchlevel 72) [i386-cygwin]
-e:1:in `initialize': No such file or directory - nul (Errno::ENOENT)
        from -e:1:in `open'
        from -e:1

Skye at Skye-PC ~
$ /cygdrive/c/Ruby187/bin/ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]


RubyGems version is 1.5


----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-01 16:53

Message:
Can you verify this is fixed in rubygems trunk?

https://github.com/rubygems/rubygems/commit/d434c98

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

From drbrain at segment7.net  Tue Feb  1 20:35:41 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Tue, 1 Feb 2011 17:35:41 -0800
Subject: [Rubygems-developers] [ rubygems-Bugs-28900 ] Cygwin:
	Gem::SilentUI tries to open Windows' NUL file
In-Reply-To: <20110202005311.627E91858381@rubyforge.org>
References: <20110202005311.627E91858381@rubyforge.org>
Message-ID: <5C31B987-2965-4588-B02D-71B3B14DED3B@segment7.net>

On Feb 1, 2011, at 16:53, <noreply at rubyforge.org> wrote:

> Summary: Cygwin: Gem::SilentUI tries to open Windows' NUL file
> 
>> Comment By: Eric Hodel (drbrain)
> Date: 2011-02-01 16:53
> 
> Message:
> Can you verify this is fixed in rubygems trunk?
> 
> https://github.com/rubygems/rubygems/commit/d434c98

Luis, can you verify this does not break on rubyinstaller as well?

From noreply at rubyforge.org  Tue Feb  1 20:43:08 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 20:43:08 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28837 ] `gem update` attempts
	to upgrade rubygems without using the --system flag
Message-ID: <20110202014308.940F5185837F@rubyforge.org>

Bugs item #28837, was opened at 2011-01-07 17:00
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28837&group_id=126

Category: `gem` commands (other)
Group: v1.4.x
>Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: Lee Jarvis (injekt)
Assigned to: Ryan Davis (zenspider)
Summary: `gem update` attempts to upgrade rubygems without using the --system flag

Initial Comment:
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [i686-linux]
  - INSTALLATION DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /home/injekt/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/injekt/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136
     - /home/injekt/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://gemcutter.org

Verbose output of `gem update` can be found attached.

Even after running `gem uninstall rubygems-update`, this issue still occurs.

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-01 16:41

Message:
RubyGems no longer attempts to upgrade rubygems itself when a newer rubygems-update is available.  It will still be downloaded and installed (which will be harmless)

----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2011-01-09 14:52

Message:
This _should_ (or at least could) be fixed on trunk. There are exactly zero tests for update --system but eric has a strategy for that so we'll get it patched up soon. In the meantime, manual verification would be great.

Just to note: we can't do a damn thing about this bug being released in 1.9... so... yeah.

----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:57

Message:
OK. I have a repro, and this is indeed a bug:

% gem uninstall -a rubygems-update
% gem install rubygems-update -v 1.3.7
% gem update -V

Extra notes:

It doesn't actually update your system, as it fails before writing anything.

It shouldn't be doing what it is doing regardless. We need to look into this asap.

----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:21

Message:
I just updated:

https://github.com/rubygems/rubygems/blob/master/UPGRADING.rdoc

with force downgrade instructions appropriate for 1.9.2 & rubygems 1.4.x.

Without a working repro, I can't address this ticket and will prolly have to reject it.

----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2011-01-08 22:19

Message:
I can't repro this at all:

% gem update -V
Updating installed gems
Nothing to update


% gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-darwin10.6.0]
  - INSTALLATION DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136
  - RUBY EXECUTABLE: /Users/ryan/.rvm/rubies/ruby-1.9.2-p136/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/ryan/.rvm/gems/ruby-1.9.2-p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-10
  - GEM PATHS:
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136
     - /Users/ryan/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - "gemcutter_key" => "********************************"
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

Comment By: Lee Jarvis (injekt)
Date: 2011-01-08 01:47

Message:
Whoops! Didn't see that there. Attached.

----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2011-01-07 23:24

Message:
Not attached. Make sure you check that infernal checkbox.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28837&group_id=126

From noreply at rubyforge.org  Tue Feb  1 20:46:34 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 20:46:34 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28844 ] rubygems plugins,
	1.9 and circular requires
Message-ID: <20110202014634.183671678327@rubyforge.org>

Bugs item #28844, was opened at 2011-01-09 17:24
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28844&group_id=126

Category: #gem and #require methods
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Erik Hollensbe (erikh)
>Assigned to: Eric Hodel (drbrain)
Summary: rubygems plugins, 1.9 and circular requires

Initial Comment:
I apologize in advance if this is confusing.

I'm not entirely sure if this is gem_prelude's fault or rubygems's or even ruby proper's fault, but here goes:

http://www.gem-testers.org/gems/rubygems-test/v/0.2.1/test_results/2

If you carefully examine the stack trace, you'll see that the rdoc plugin is being pulled in, then hanna is being pulled in. What happens in hanna is that rubygems is pulled in, ergo our problem. This is all done in from a rake process spawned by rubygems-test which uses open4 which in 1.9 uses threads, so threading may be a part of the issue here.

This issue does not exhibit in 1.8, but it uses fork there. I was unable to test in RG 1.4 because of the obvious.

I was able to fix this in rubygems-test 0.2.1 for the 'gem test' provider. The commit below is the fix.

https://github.com/rubygems/rubygems-test/commit/72b0e136889fcd2509bb040de3fe9220c4b8bc13

You can see that I abuse autoload there to ensure that any rubygems dependencies (and YAML to be safe)  are only loaded once. This is because of the above issue. These patches fix it but not for rdoc and (I presume) other plugins.

What probably needs to happen is some beyond-the-call-of-duty $:/$" inspection before plugin load runs or to somehow load plugins with autoload (I don't think this is possible though). Obviously I'm deferring to your experience.

Please feel free to tell me where to stick this bug report if it does not belong here, I'm just convinced after the discrete repros that it at least gets close to starting in rubygems.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28844&group_id=126

From noreply at rubyforge.org  Tue Feb  1 20:47:08 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 20:47:08 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28806 ] Re-install of a gem
	can leave prior gem files remaining
Message-ID: <20110202014708.C00C11678327@rubyforge.org>

Bugs item #28806, was opened at 2010-12-28 17:26
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28806&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: David Kellum (dekellum)
>Assigned to: Ryan Davis (zenspider)
Summary: Re-install of a gem can leave prior gem files remaining

Initial Comment:
The problem arises when the contents of gem change over multiple builds with the same gem version, typically when a gem is under development and installed repeatedly to a local gem home.  There are several cases where gems load or otherwise use all files in a particular directory within the gem install dir.  When a file is removed or renamed over subsequent builds, old files from the prior "gem install" will remain after the new "gem install", leading to often unexpected behavior.

One specific example would be gem packaged ActiveRecord migrations directory, where all migrations in a gem installed "db/" directory are applied.

To avoid any chance of inconsistent behavior from prior installed gem files, it would be best if the gem Installer removed all old files from the gem_dir before installing the new files.

It looks like an easy change. I will offer a patch for this issue up on github.


----------------------------------------------------------------------

Comment By: David Kellum (dekellum)
Date: 2010-12-28 17:35

Message:
Pull request: 

https://github.com/rubygems/rubygems/pull/18

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28806&group_id=126

From noreply at rubyforge.org  Tue Feb  1 20:47:20 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 20:47:20 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28742 ] Manual states gemrc
	is looked up in home directory only whereas /etc/gemrc is
	also consulted
Message-ID: <20110202014720.900541678327@rubyforge.org>

Bugs item #28742, was opened at 2010-11-22 09:02
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28742&group_id=126

Category: documentation
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Rich Meyers (richmeyers)
>Assigned to: Eric Hodel (drbrain)
Summary: Manual states gemrc is looked up in home directory only whereas /etc/gemrc is also consulted

Initial Comment:
Documentation here: http://docs.rubygems.org/read/chapter/11 states:

gem looks for a configuration file .gemrc in your home directory, although you can specify another file on the command-line if you wish (with the ?config-file modifier). Only one configuration file will be processed: the rightmost one on the command-line, or the default $HOME/.gemrc, or none at all.

In actuality, configuration may be taken from /etc/gemrc if it exists.

RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.8.7 (2009-12-24 patchlevel 248) [amd64-freebsd8]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: /usr/local/bin/ruby18
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - amd64-freebsd-8
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.8
     - /home/rm/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28742&group_id=126

From noreply at rubyforge.org  Tue Feb  1 20:48:52 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 20:48:52 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28889 ] gem rdoc --all
	--overwrite doesn't work
Message-ID: <20110202014852.F34DE1858389@rubyforge.org>

Bugs item #28889, was opened at 2011-01-28 12:07
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28889&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: V?t Ondruch (voxik)
>Assigned to: Eric Hodel (drbrain)
Summary: gem rdoc --all --overwrite doesn't work

Initial Comment:
C:\>gem rdoc --all --overwrite
Installing ri documentation for bundler-1.0.9...
Installing ri documentation for minitest-2.0.2...
ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory - C:/Users/vita/.pik/rubies/Ruby-193-dev/lib/ruby/gems/1.9.1/gems/minitest-2.0.2

It is apparently one of the bundled gems, therefore the directory cannot be found.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28889&group_id=126

From noreply at rubyforge.org  Tue Feb  1 20:54:10 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 20:54:10 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28726 ] gem install
	--user-install as root adds cached .gem file outside of HOME
Message-ID: <20110202015410.AB8781678323@rubyforge.org>

Bugs item #28726, was opened at 2010-11-16 12:43
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28726&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Jeremy Evans (jeremyevans)
>Assigned to: Ryan Davis (zenspider)
Summary: gem install --user-install as root adds cached .gem file outside of HOME

Initial Comment:
I think the problem is at https://github.com/rubygems/rubygems/blob/master/lib/rubygems/remote_fetcher.rb#L80

Basically, in RemoteFetcher#download, it's checking whether the install_dir (Gem.dir by default) is writable, and if so, it uses that dir.  However, if the user is using the --user-install option, even if the user is root, it should not be writing outside of HOME/.gem.  Basically, if the --user-install option is given, it should always download to HOME/.gem.  This may require an API change.

This affects building OpenBSD ports for some gems, since the --user-install option is used (in combination with a fake HOME).  Usually, building is done as a regular user and is fine.  However, if the builder is root, rubygems adds the .gem files to the /usr/local/lib/ruby directory when the gem is installed to HOME/.gem.  Then when the package builder goes to install the package, the cached .gem file already exists and the package install fails.

This isn't a critical bug, as it can be trivially worked around by specifying GEM_HOME=$HOME/.gem in the environment when using gem install --user-install (which the OpenBSD ports system now does).

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28726&group_id=126

From luislavena at gmail.com  Tue Feb  1 21:41:57 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Tue, 1 Feb 2011 23:41:57 -0300
Subject: [Rubygems-developers] [ rubygems-Bugs-28900 ] Cygwin:
 Gem::SilentUI tries to open Windows' NUL file
In-Reply-To: <5C31B987-2965-4588-B02D-71B3B14DED3B@segment7.net>
References: <20110202005311.627E91858381@rubyforge.org>
	<5C31B987-2965-4588-B02D-71B3B14DED3B@segment7.net>
Message-ID: <AANLkTi=FQd4j2T5ZQTFv=5V36ZvYKUt64XLi59mfUn6T@mail.gmail.com>

On Tue, Feb 1, 2011 at 10:35 PM, Eric Hodel <drbrain at segment7.net> wrote:
>
> Luis, can you verify this does not break on rubyinstaller as well?

It will only affect if user has a folder named dev at the root of the
drive, but that is highly unlikely ;-)

irb(main):001:0> reader = File.open('/dev/null', 'r')
Errno::ENOENT: No such file or directory - /dev/null
        from (irb):1:in `initialize'
        from (irb):1:in `open'
        from (irb):1

irb(main):001:0> writer = File.open('/dev/null', 'w')
Errno::ENOENT: No such file or directory - /dev/null
        from (irb):1:in `initialize'
        from (irb):1:in `open'
        from (irb):1

>mkdir \dev

irb(main):002:0> writer = File.open('/dev/null0', 'w')
=> #<File:/dev/null0>

But it will throw the exception first due the 'r' mode been invoked first.

I think we are cool ;-)
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From noreply at rubyforge.org  Tue Feb  1 22:13:32 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 22:13:32 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-26109 ] gem install gemname
	--remote will fail if gemname is in current directory
Message-ID: <20110202031332.C6DD01678323@rubyforge.org>

Bugs item #26109, was opened at 2009-06-02 15:03
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26109&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: ara howard (ahoward)
>Assigned to: Ryan Davis (zenspider)
Summary: gem install gemname --remote will fail if gemname is in current directory

Initial Comment:
gem install gemname --remote  will prefer a gem in the current directory.  seems like --remote should *never* do *anything* local?

----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2010-12-17 02:19

Message:
Thanks Asari. Seems valid to me. 

Assigning to JB and leaving this one open since it also talks about local cache and there might be extra edge cases here.

----------------------------------------------------------------------

Comment By: Hirotsugu Asari (asarih)
Date: 2010-12-16 22:35

Message:
Ryan,

Could this other ticket help your reproduce it?

http://rubyforge.org/tracker/index.php?func=detail&aid=28481&group_id=126&atid=575

Also, `gem install` appears to search the local cache before querying remote sources, so if foo-1.0.0.dev1.gem exists in cache, it will be chosen, even when foo-1.0.0.gem (with seemingly more recent version number) is available on a remote server.

----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2010-11-12 14:46

Message:
This ticket has been deemed stale and we're closing it in order to catch up 
with our ticket list. If you think it is still valid, please reopen.

----------------------------------------------------------------------

Comment By: Christof Spies (wingfire)
Date: 2010-08-19 23:52

Message:
gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [x86_64-linux]
  - INSTALLATION DIRECTORY: /usr/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: /usr/bin/ruby1.8
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-linux
  - GEM PATHS:
     - /usr/lib/ruby/gems/1.8
     - /root/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/



----------------------------------------------------------------------

Comment By: Christof Spies (wingfire)
Date: 2010-08-19 23:47

Message:
I can confirm this issue.
i.e. you have an outdated gem file in your home directory and run  "gem update" from home then gem reinstall the old gem from the home directory. "gem update -r" is also "updating" with the outdated local gem.

----------------------------------------------------------------------

Comment By: Nick Hildebrant (nihildeb)
Date: 2009-08-27 15:37

Message:
Just familiarizing myself with the code here. I now see the issue.

#find_gems_with_sources probably should only merge gem sources if @domain == :both

also I don't see a case in which setting @domain = :local after rescuing a RemoteFetch exception would be useful or make sense

----------------------------------------------------------------------

Comment By: Nick Hildebrant (nihildeb)
Date: 2009-08-26 13:54

Message:
I can not reproduce this issue as a "preference". 

Rubygems appears to do remote as requested with requested gem in pwd.

In the case of no network availability, the requested gem in the pwd is installed. This is as designed: Gem::DependencyInstaller#find_gems_with_sources rescues with @domain = :local

RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.3
  - RUBY VERSION: 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux]
  - INSTALLATION DIRECTORY: /usr/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: /usr/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-linux
  - GEM PATHS:
     - /usr/lib/ruby/gems/1.8
     - /home/nihildeb/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://gems.rubyforge.org", "http://gems.github.com"]
  - REMOTE SOURCES:
     - http://gems.rubyforge.org
     - http://gems.github.com






----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=26109&group_id=126

From noreply at rubyforge.org  Tue Feb  1 22:13:45 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 22:13:45 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28286 ] Removal of wrappers
	should occur *after* successful uninstallation
Message-ID: <20110202031345.43DB0185838D@rubyforge.org>

Bugs item #28286, was opened at 2010-06-08 21:11
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28286&group_id=126

Category: None
Group: None
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Sakuro OZAWA (sakuro)
>Assigned to: Ryan Davis (zenspider)
Summary: Removal of wrappers should occur *after* successful uninstallation

Initial Comment:
When one terminates uninstallation of a gem, he/she would expect wrapper scripts remain.

$ ruby --version
ruby 1.9.3dev (2010-06-08 trunk 28202) [i386-darwin9.8.0]
$ gem --version
1.3.7
$ gem uninstall nokogiri
Remove executables:
	nokogiri

in addition to the gem? [Yn]  y
Removing nokogiri

You have requested to uninstall the gem:
	nokogiri-1.4.2
cucumber-0.8.0 depends on [nokogiri (>= 1.4.2)]
mime-types-1.16 depends on [nokogiri (~> 1.2)]
webrat-0.7.1 depends on [nokogiri (>= 1.2.0)]
If you remove this gems, one or more dependencies will not be met.
Continue with Uninstall? [Yn]  n
ERROR:  While executing gem ... (Gem::DependencyRemovalException)
    Uninstallation aborted due to dependent gem(s)
$ which nokogiri
nokogiri not found


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28286&group_id=126

From noreply at rubyforge.org  Tue Feb  1 22:14:17 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 22:14:17 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28454 ] gem install
	--development installs transitive development dependencies
Message-ID: <20110202031418.074D91858389@rubyforge.org>

Bugs item #28454, was opened at 2010-08-07 07:49
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28454&group_id=126

Category: None
Group: None
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Roger Pack (rogerdpack)
>Assigned to: Ryan Davis (zenspider)
Summary: gem install --development installs transitive development dependencies

Initial Comment:
Currently it appears that if you install a gem with --development, it installs not only its development dependencies, and also its development dependencies' development dependencies (not just runtime).  

This results in a failure, for example not being able to use 

$ jruby -S gem install sensible-cinema --development 

because though all of its development dependencies are jruby friendly, their respective development dependencies are not, and it ends up trying to build binary extensions which don't work, since this is C, but they are for gems that aren't actual development dependencies for sensible-cinema, so I don't need them anyway.

This prevents --development from being useful in this situation.

Suggestion: only install development dependencies' run-time dependencies if --development is passed.
Thanks.
-r

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28454&group_id=126

From noreply at rubyforge.org  Tue Feb  1 22:17:40 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 22:17:40 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28481 ] 'gem install' always
	prefers local files with partial name match
Message-ID: <20110202031740.13428185838D@rubyforge.org>

Bugs item #28481, was opened at 2010-08-17 05:21
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28481&group_id=126

Category: `gem install` command
Group: v1.3.x
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Hirotsugu Asari (asarih)
>Assigned to: Ryan Davis (zenspider)
Summary: 'gem install' always prefers local files with partial name match

Initial Comment:
If you try to install gem with a shorter name (e.g., active_form) from a remote server but you have a .gem file of another gem with a longer name (e.g., active_forms) in the working directory, 'gem install' will use the gem file. The exact match should be preferred.

$ ruby -v -S gem install --ignore-dependencies --no-rdoc --no-ri active_forms-0.2.1.gem
ruby 1.8.7 (2010-06-23 patchlevel 299) [i686-darwin10.4.0]
Successfully installed active_forms-0.2.1
1 gem installed
$ ruby -v -S gem install --ignore-dependencies --no-rdoc --no-ri active_form
ruby 1.8.7 (2010-06-23 patchlevel 299) [i686-darwin10.4.0]
Successfully installed active_forms-0.2.1
1 gem installed

This was first reported by Stephen Bannasch in http://jira.codehaus.org/browse/JRUBY-4934.

----------------------------------------------------------------------

Comment By: Christof Spies (wingfire)
Date: 2010-08-19 23:59

Message:
seams to be the same bug as #26109 http://rubyforge.org/tracker/index.php?func=detail&aid=26109&group_id=126&atid=575

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28481&group_id=126

From noreply at rubyforge.org  Tue Feb  1 22:18:21 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 22:18:21 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28491 ] fetch a specific
	prerelease version
Message-ID: <20110202031821.B9D3A1858389@rubyforge.org>

Bugs item #28491, was opened at 2010-08-19 15:30
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28491&group_id=126

Category: `gem` commands (remote behavior)
Group: v1.3.x
Status: Open
Resolution: None
Priority: 3
Submitted By: gabriel horner (cldwalker)
>Assigned to: Ryan Davis (zenspider)
Summary: fetch a specific prerelease version

Initial Comment:
I can't fetch a specific prerelease version:
  $ gem fetch dm-core -v '1.0.0.rc2' --pre --debug
   Exception `NameError' at /Users/bozo/.rvm/rubies/ruby-1.8.7-p299/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:164 - uninitialized constant Gem::Commands::FetchCommand
   Exception `OptionParser::InvalidOption' at /Users/bozo/.rvm/rubies/ruby-1.8.7-p299/lib/ruby/1.8/optparse.rb:1450 - invalid option: no-ri
   Exception `OptionParser::InvalidOption' at /Users/bozo/.rvm/rubies/ruby-1.8.7-p299/lib/ruby/1.8/optparse.rb:1263 - invalid option: --no-ri
   ERROR:  Could not find a valid gem 'dm-core' (= 1.0.0.rc2) in any repository
  
I'm aware I can fetch the latest prerelease version: gem fetch dm-core --pre
but I need specific prerelease versions of gems. Is this possible?

FYI, I originally asked about this on help.rubygems.org: http://help.rubygems.org/discussions/questions/38-gem-fetch-a-specific-prerelease-version

My gem environment:

$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.7
  - RUBY VERSION: 1.8.7 (2010-06-23 patchlevel 299) [i686-darwin9.4.0]
  - INSTALLATION DIRECTORY: /Users/bozo/.rvm/gems/ruby-1.8.7-p299 at ext
  - RUBY EXECUTABLE: /Users/bozo/.rvm/rubies/ruby-1.8.7-p299/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/bozo/.rvm/gems/ruby-1.8.7-p299 at ext/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-darwin-9
  - GEM PATHS:
     - /Users/bozo/.rvm/gems/ruby-1.8.7-p299 at ext
     - /Users/bozo/.rvm/gems/ruby-1.8.7-p299 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - "gem" => "--no-ri"
     - :sources => ["http://rubygems.org"]
  - REMOTE SOURCES:
     - http://rubygems.org

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28491&group_id=126

From noreply at rubyforge.org  Tue Feb  1 22:18:37 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 22:18:37 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28713 ] clean and remove
	should run in reverse topo sort
Message-ID: <20110202031837.D8B2D1858389@rubyforge.org>

Bugs item #28713, was opened at 2010-11-12 13:46
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28713&group_id=126

Category: `gem` commands (other)
Group: None
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: Ryan Davis (zenspider)
>Assigned to: Ryan Davis (zenspider)
Summary: clean and remove should run in reverse topo sort

Initial Comment:
kiss my ass rubyforge. see summary.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28713&group_id=126

From noreply at rubyforge.org  Tue Feb  1 22:28:37 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 22:28:37 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Feature Requests-28901 ] gem
	install -v X should fail if multiple gems named
Message-ID: <20110202032837.6BD121858389@rubyforge.org>

Feature Requests item #28901, was opened at 2011-02-01 19:28
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=28901&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Ryan Davis (zenspider)
Assigned to: Ryan Davis (zenspider)
Summary: gem install -v X should fail if multiple gems named

Initial Comment:
Instead of making things even more complicated, rubygems should simply not allow multiple gems to be named if --version is used.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=28901&group_id=126

From noreply at rubyforge.org  Tue Feb  1 23:12:42 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  1 Feb 2011 23:12:42 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28902 ]
	Specification#ruby_code should be more secure with arrays
Message-ID: <20110202041242.23B191858381@rubyforge.org>

Bugs item #28902, was opened at 2011-02-01 20:12
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28902&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Ryan Davis (zenspider)
Assigned to: Ryan Davis (zenspider)
Summary: Specification#ruby_code should be more secure with arrays

Initial Comment:
Either check that everything within is clean, or recurse on each member.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28902&group_id=126

From jftucker at gmail.com  Wed Feb  2 12:10:20 2011
From: jftucker at gmail.com (James Tucker)
Date: Wed, 2 Feb 2011 09:10:20 -0800
Subject: [Rubygems-developers] [ rubygems-Bugs-28900 ] Cygwin:
	Gem::SilentUI tries to open Windows' NUL file
In-Reply-To: <AANLkTi=FQd4j2T5ZQTFv=5V36ZvYKUt64XLi59mfUn6T@mail.gmail.com>
References: <20110202005311.627E91858381@rubyforge.org>
	<5C31B987-2965-4588-B02D-71B3B14DED3B@segment7.net>
	<AANLkTi=FQd4j2T5ZQTFv=5V36ZvYKUt64XLi59mfUn6T@mail.gmail.com>
Message-ID: <68F634F6-674C-4A4C-BACE-874323F47185@gmail.com>

Using the device name explicitly might also be recommended, i.e. "nul:", rather than "nul"

On Feb 1, 2011, at 6:41 PM, Luis Lavena wrote:

> On Tue, Feb 1, 2011 at 10:35 PM, Eric Hodel <drbrain at segment7.net> wrote:
>> 
>> Luis, can you verify this does not break on rubyinstaller as well?
> 
> It will only affect if user has a folder named dev at the root of the
> drive, but that is highly unlikely ;-)
> 
> irb(main):001:0> reader = File.open('/dev/null', 'r')
> Errno::ENOENT: No such file or directory - /dev/null
>        from (irb):1:in `initialize'
>        from (irb):1:in `open'
>        from (irb):1
> 
> irb(main):001:0> writer = File.open('/dev/null', 'w')
> Errno::ENOENT: No such file or directory - /dev/null
>        from (irb):1:in `initialize'
>        from (irb):1:in `open'
>        from (irb):1
> 
>> mkdir \dev
> 
> irb(main):002:0> writer = File.open('/dev/null0', 'w')
> => #<File:/dev/null0>
> 
> But it will throw the exception first due the 'r' mode been invoked first.
> 
> I think we are cool ;-)
> -- 
> Luis Lavena
> AREA 17
> -
> Perfection in design is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away.
> Antoine de Saint-Exup?ry
> _______________________________________________
> Rubygems-developers mailing list
> http://rubyforge.org/projects/rubygems
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers


From noreply at rubyforge.org  Thu Feb  3 09:42:59 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  3 Feb 2011 09:42:59 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28906 ] Gems built with
	(rubygems 1.5.0 / ruby 1.9.2) do not install properly with
	(1.5.0 / 1.8.7)
Message-ID: <20110203144259.2E6401858344@rubyforge.org>

Bugs item #28906, was opened at 2011-02-03 15:42
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28906&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Bernard Lambeau (blambeau)
Assigned to: Nobody (None)
Summary: Gems built with (rubygems 1.5.0 / ruby 1.9.2) do not install properly with (1.5.0 / 1.8.7)

Initial Comment:
The build/install scenario below fails. It seems that the metadata generated by 1.9.2 is not properly loaded by 1.8.7.  I've attached foo.gemspec. 

blambeau at yemana foo  % rvm use 1.9.2 && rm -rf pkg && gem build foo.gemspec 
  Successfully built RubyGem
  Name: foo
  Version: 1.0.0
  File: foo-1.0.0.gem
blambeau at yemana foo  % rvm use 1.8.7 && gem install foo-1.0.0.gem      
ERROR:  While executing gem ... (Gem::Exception)
    ruby_code case not handled: YAML::PrivateType

I've made some investgations and here is what I've found:

* expection raise in ruby_code, which receives a YAML::PrivateType object
* called in Specification#to_ruby
* that the first entry that fails is autorequire: !!null 
* I suspect !!null to behave differently in ruby 1.8.7 and 1.9.2, probably Syck <> Psych

See also http://help.rubygems.org/discussions/problems/483-gems-built-with-rubygems-150-ruby-192-do-not-install-properly-with-150-187

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28906&group_id=126

From noreply at rubyforge.org  Thu Feb  3 13:59:44 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  3 Feb 2011 13:59:44 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28907 ] [RG 1.5.0/Ruby 1.9.x]
	source gem build error due to syck?
Message-ID: <20110203185944.C982E1678324@rubyforge.org>

Bugs item #28907, was opened at 2011-02-03 18:59
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

Category: `gem` commands (other)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Jon Forums (jonforums)
Assigned to: Nobody (None)
Summary: [RG 1.5.0/Ruby 1.9.x] source gem build error due to syck?

Initial Comment:
When building a source gem from http://github.com/oopsforge/oops-null using 'rake gem' I get the following error on Win7 with:

  * ruby 1.9.2p174 (2011-01-28 revision 30696) [i386-mingw32]
  * ruby 1.9.3dev (2011-02-04 trunk 30776) [i386-mingw32]

but no errors using "ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32]".  

Manually building via 'gem build oops-null.gemspec' work fine on all the Ruby versions including JRuby 1.6.0.RC1.  All versions have been upgraded to RG 1.5.0 via "gem update --system".

FWIW, the failure does not occur on "ruby 1.9.2 (2010-12-25 patchlevel 136) [i386-mingw32]" using RG 1.3.7

My "fix" was to add the following lines to the project Rakefile after the 3 require's:

require 'yaml'
YAML::ENGINE.yamler='psych' if defined?(YAML::ENGINE)

I will try to replicate on my Arch system later this afternoon.

Reproducible?

Jon


== ERROR ==

C:\projects\oops-null-git>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.2 (2011-01-28 patchlevel 174) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/Users/Jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", "http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org


C:\projects\oops-null-git>rake gem
(in C:/projects/oops-null-git)
mkdir -p pkg
mkdir -p pkg
mkdir -p pkg/oops-null-0.3.0/bin
rm -f pkg/oops-null-0.3.0/bin/nulloops
ln bin/nulloops pkg/oops-null-0.3.0/bin/nulloops
rm -f pkg/oops-null-0.3.0/Rakefile
ln Rakefile pkg/oops-null-0.3.0/Rakefile
rm -f pkg/oops-null-0.3.0/oops-null.gemspec
ln oops-null.gemspec pkg/oops-null-0.3.0/oops-null.gemspec
mkdir -p pkg/oops-null-0.3.0/ext/oops_null
rm -f pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
ln ext/oops_null/extconf.rb pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
ln ext/oops_null/oops_null.c pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
ln ext/oops_null/oops_null.h pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
mkdir -p pkg/oops-null-0.3.0/lib
rm -f pkg/oops-null-0.3.0/lib/oops-null.rb
ln lib/oops-null.rb pkg/oops-null-0.3.0/lib/oops-null.rb
cd pkg/oops-null-0.3.0
rake aborted!
undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
C:/ruby192/lib/ruby/1.9.1/psych.rb:166:in `dump'
C:/ruby192/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block (2 levels) in to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `map'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `block in to_yaml'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `call'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `emit'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:725:in `to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1157:in `when_writing'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1092:in `chdir'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `call'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `block in execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:595:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:605:in `block in invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:594:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:581:in `invoke'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2041:in `invoke_task'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block (2 levels) in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2013:in `top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1992:in `run'
C:/ruby192/bin/rake:31:in `<main>'

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

From noreply at rubyforge.org  Thu Feb  3 14:13:25 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  3 Feb 2011 14:13:25 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28907 ] [RG 1.5.0/Ruby 1.9.x]
	source gem build error due to syck?
Message-ID: <20110203191325.5EC0A1858354@rubyforge.org>

Bugs item #28907, was opened at 2011-02-03 18:59
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

Category: `gem` commands (other)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Jon Forums (jonforums)
Assigned to: Nobody (None)
Summary: [RG 1.5.0/Ruby 1.9.x] source gem build error due to syck?

Initial Comment:
When building a source gem from http://github.com/oopsforge/oops-null using 'rake gem' I get the following error on Win7 with:

  * ruby 1.9.2p174 (2011-01-28 revision 30696) [i386-mingw32]
  * ruby 1.9.3dev (2011-02-04 trunk 30776) [i386-mingw32]

but no errors using "ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32]".  

Manually building via 'gem build oops-null.gemspec' work fine on all the Ruby versions including JRuby 1.6.0.RC1.  All versions have been upgraded to RG 1.5.0 via "gem update --system".

FWIW, the failure does not occur on "ruby 1.9.2 (2010-12-25 patchlevel 136) [i386-mingw32]" using RG 1.3.7

My "fix" was to add the following lines to the project Rakefile after the 3 require's:

require 'yaml'
YAML::ENGINE.yamler='psych' if defined?(YAML::ENGINE)

I will try to replicate on my Arch system later this afternoon.

Reproducible?

Jon


== ERROR ==

C:\projects\oops-null-git>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.2 (2011-01-28 patchlevel 174) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/Users/Jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", "http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org


C:\projects\oops-null-git>rake gem
(in C:/projects/oops-null-git)
mkdir -p pkg
mkdir -p pkg
mkdir -p pkg/oops-null-0.3.0/bin
rm -f pkg/oops-null-0.3.0/bin/nulloops
ln bin/nulloops pkg/oops-null-0.3.0/bin/nulloops
rm -f pkg/oops-null-0.3.0/Rakefile
ln Rakefile pkg/oops-null-0.3.0/Rakefile
rm -f pkg/oops-null-0.3.0/oops-null.gemspec
ln oops-null.gemspec pkg/oops-null-0.3.0/oops-null.gemspec
mkdir -p pkg/oops-null-0.3.0/ext/oops_null
rm -f pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
ln ext/oops_null/extconf.rb pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
ln ext/oops_null/oops_null.c pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
ln ext/oops_null/oops_null.h pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
mkdir -p pkg/oops-null-0.3.0/lib
rm -f pkg/oops-null-0.3.0/lib/oops-null.rb
ln lib/oops-null.rb pkg/oops-null-0.3.0/lib/oops-null.rb
cd pkg/oops-null-0.3.0
rake aborted!
undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
C:/ruby192/lib/ruby/1.9.1/psych.rb:166:in `dump'
C:/ruby192/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block (2 levels) in to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `map'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `block in to_yaml'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `call'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `emit'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:725:in `to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1157:in `when_writing'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1092:in `chdir'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `call'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `block in execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:595:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:605:in `block in invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:594:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:581:in `invoke'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2041:in `invoke_task'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block (2 levels) in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2013:in `top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1992:in `run'
C:/ruby192/bin/rake:31:in `<main>'

----------------------------------------------------------------------

>Comment By: Jon Forums (jonforums)
Date: 2011-02-03 19:13

Message:
similar failure and working "fix" on Arch using:

ruby 1.9.3dev (2011-02-04 trunk 30776) [i686-linux]

RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.3 (2011-02-04 patchlevel -1) [i686-
linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.9.1
     - /home/jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", 
"http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

From noreply at rubyforge.org  Thu Feb  3 16:45:55 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  3 Feb 2011 16:45:55 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28900 ] Cygwin: Gem::SilentUI
	tries to open Windows' NUL file
Message-ID: <20110203214556.2BEA21858346@rubyforge.org>

Bugs item #28900, was opened at 2011-02-01 19:16
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

Category: None
Group: v1.5.x
Status: Open
Resolution: Accepted
Priority: 3
Submitted By: S Shaw (skye)
Assigned to: Eric Hodel (drbrain)
Summary: Cygwin: Gem::SilentUI tries to open Windows' NUL file

Initial Comment:
>From user_interaction.rb:

class Gem::SilentUI < Gem::StreamUI

  def initialize

    reader, writer = nil, nil

    if Gem.win_platform?
      reader = File.open('nul', 'r')
      writer = File.open('nul', 'w')
    else
      reader = File.open('/dev/null', 'r')
      writer = File.open('/dev/null', 'w')
    end

    super reader, writer, writer
  end
end

When running on cygwin Gem::SilentUI will be in a POSIX environment where the NUL file is /dev/null. 

Skye at Skye-PC ~
$ ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2008-08-11 patchlevel 72) [i386-cygwin]
-e:1:in `initialize': No such file or directory - nul (Errno::ENOENT)
        from -e:1:in `open'
        from -e:1

Skye at Skye-PC ~
$ /cygdrive/c/Ruby187/bin/ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]


RubyGems version is 1.5


----------------------------------------------------------------------

Comment By: Tim Anderegg (tanderegg)
Date: 2011-02-03 16:45

Message:
Hello, I had this same problem, although the code listed below by Eric does indeed fix the problem, this fix has not yet been committed.

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-01 19:53

Message:
Can you verify this is fixed in rubygems trunk?

https://github.com/rubygems/rubygems/commit/d434c98

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

From noreply at rubyforge.org  Fri Feb  4 03:53:46 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri,  4 Feb 2011 03:53:46 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28909 ] rubygems 1.5.0
	uninitialized constant Gem::UserInteraction (NameError)
Message-ID: <20110204085346.B6C021858357@rubyforge.org>

Bugs item #28909, was opened at 2011-02-04 17:53
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28909&group_id=126

Category: other
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: John Mettraux (jmettraux)
Assigned to: Nobody (None)
Summary: rubygems 1.5.0 uninitialized constant Gem::UserInteraction  (NameError)

Initial Comment:

# 1.8.7 or 1.9.2
# rubygems 1.5.0


require 'rubygems'

gemspec = Gem::Specification.new do |s|
end

gemspec.validate

 # ==>
 # /Users/toto/.rvm/rubies/ruby-1.8.7-p249/lib/ruby/site_ruby/1.8/rubygems/specification.rb:832:in `validate': uninitialized constant Gem::UserInteraction (NameError)
 #   from t.rb:8


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28909&group_id=126

From noreply at rubyforge.org  Fri Feb  4 04:24:04 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri,  4 Feb 2011 04:24:04 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28909 ] rubygems 1.5.0
	uninitialized constant Gem::UserInteraction (NameError)
Message-ID: <20110204092405.0E0F31858357@rubyforge.org>

Bugs item #28909, was opened at 2011-02-04 09:53
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28909&group_id=126

Category: other
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: John Mettraux (jmettraux)
Assigned to: Nobody (None)
Summary: rubygems 1.5.0 uninitialized constant Gem::UserInteraction  (NameError)

Initial Comment:

# 1.8.7 or 1.9.2
# rubygems 1.5.0


require 'rubygems'

gemspec = Gem::Specification.new do |s|
end

gemspec.validate

 # ==>
 # /Users/toto/.rvm/rubies/ruby-1.8.7-p249/lib/ruby/site_ruby/1.8/rubygems/specification.rb:832:in `validate': uninitialized constant Gem::UserInteraction (NameError)
 #   from t.rb:8


----------------------------------------------------------------------

Comment By: Torsten Sch?nebaum (tosch)
Date: 2011-02-04 10:24

Message:
Adding
require 'rubygems/user_interaction'
to lib/rubygems/specification.rb solves this issue for me.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28909&group_id=126

From noreply at rubyforge.org  Fri Feb  4 09:53:40 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri,  4 Feb 2011 09:53:40 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28907 ] [RG 1.5.0/Ruby 1.9.x]
	source gem build error due to syck?
Message-ID: <20110204145340.1768B1858377@rubyforge.org>

Bugs item #28907, was opened at 2011-02-03 18:59
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

Category: `gem` commands (other)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Jon Forums (jonforums)
Assigned to: Nobody (None)
Summary: [RG 1.5.0/Ruby 1.9.x] source gem build error due to syck?

Initial Comment:
When building a source gem from http://github.com/oopsforge/oops-null using 'rake gem' I get the following error on Win7 with:

  * ruby 1.9.2p174 (2011-01-28 revision 30696) [i386-mingw32]
  * ruby 1.9.3dev (2011-02-04 trunk 30776) [i386-mingw32]

but no errors using "ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32]".  

Manually building via 'gem build oops-null.gemspec' work fine on all the Ruby versions including JRuby 1.6.0.RC1.  All versions have been upgraded to RG 1.5.0 via "gem update --system".

FWIW, the failure does not occur on "ruby 1.9.2 (2010-12-25 patchlevel 136) [i386-mingw32]" using RG 1.3.7

My "fix" was to add the following lines to the project Rakefile after the 3 require's:

require 'yaml'
YAML::ENGINE.yamler='psych' if defined?(YAML::ENGINE)

I will try to replicate on my Arch system later this afternoon.

Reproducible?

Jon


== ERROR ==

C:\projects\oops-null-git>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.2 (2011-01-28 patchlevel 174) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/Users/Jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", "http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org


C:\projects\oops-null-git>rake gem
(in C:/projects/oops-null-git)
mkdir -p pkg
mkdir -p pkg
mkdir -p pkg/oops-null-0.3.0/bin
rm -f pkg/oops-null-0.3.0/bin/nulloops
ln bin/nulloops pkg/oops-null-0.3.0/bin/nulloops
rm -f pkg/oops-null-0.3.0/Rakefile
ln Rakefile pkg/oops-null-0.3.0/Rakefile
rm -f pkg/oops-null-0.3.0/oops-null.gemspec
ln oops-null.gemspec pkg/oops-null-0.3.0/oops-null.gemspec
mkdir -p pkg/oops-null-0.3.0/ext/oops_null
rm -f pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
ln ext/oops_null/extconf.rb pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
ln ext/oops_null/oops_null.c pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
ln ext/oops_null/oops_null.h pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
mkdir -p pkg/oops-null-0.3.0/lib
rm -f pkg/oops-null-0.3.0/lib/oops-null.rb
ln lib/oops-null.rb pkg/oops-null-0.3.0/lib/oops-null.rb
cd pkg/oops-null-0.3.0
rake aborted!
undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
C:/ruby192/lib/ruby/1.9.1/psych.rb:166:in `dump'
C:/ruby192/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block (2 levels) in to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `map'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `block in to_yaml'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `call'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `emit'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:725:in `to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1157:in `when_writing'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1092:in `chdir'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `call'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `block in execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:595:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:605:in `block in invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:594:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:581:in `invoke'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2041:in `invoke_task'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block (2 levels) in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2013:in `top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1992:in `run'
C:/ruby192/bin/rake:31:in `<main>'

----------------------------------------------------------------------

>Comment By: Jon Forums (jonforums)
Date: 2011-02-04 14:53

Message:
same failure on "ruby 1.9.2p136 (2010-12-25) [i386-mingw32]" 
upgraded from RG 1.3.7 to RG 1.5.0

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-03 19:13

Message:
similar failure and working "fix" on Arch using:

ruby 1.9.3dev (2011-02-04 trunk 30776) [i686-linux]

RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.3 (2011-02-04 patchlevel -1) [i686-
linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.9.1
     - /home/jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", 
"http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

From noreply at rubyforge.org  Fri Feb  4 15:29:51 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri,  4 Feb 2011 15:29:51 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28900 ] Cygwin: Gem::SilentUI
	tries to open Windows' NUL file
Message-ID: <20110204202951.1CC1D1858387@rubyforge.org>

Bugs item #28900, was opened at 2011-02-01 16:16
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

Category: None
Group: v1.5.x
>Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: S Shaw (skye)
Assigned to: Eric Hodel (drbrain)
Summary: Cygwin: Gem::SilentUI tries to open Windows' NUL file

Initial Comment:
>From user_interaction.rb:

class Gem::SilentUI < Gem::StreamUI

  def initialize

    reader, writer = nil, nil

    if Gem.win_platform?
      reader = File.open('nul', 'r')
      writer = File.open('nul', 'w')
    else
      reader = File.open('/dev/null', 'r')
      writer = File.open('/dev/null', 'w')
    end

    super reader, writer, writer
  end
end

When running on cygwin Gem::SilentUI will be in a POSIX environment where the NUL file is /dev/null. 

Skye at Skye-PC ~
$ ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2008-08-11 patchlevel 72) [i386-cygwin]
-e:1:in `initialize': No such file or directory - nul (Errno::ENOENT)
        from -e:1:in `open'
        from -e:1

Skye at Skye-PC ~
$ /cygdrive/c/Ruby187/bin/ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]


RubyGems version is 1.5


----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 12:29

Message:
Tim, check again, it's been committed, that's why there's a link to the commit below.

Closing this as it's been found to work via mailing-list reporters.

----------------------------------------------------------------------

Comment By: Tim Anderegg (tanderegg)
Date: 2011-02-03 13:45

Message:
Hello, I had this same problem, although the code listed below by Eric does indeed fix the problem, this fix has not yet been committed.

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-01 16:53

Message:
Can you verify this is fixed in rubygems trunk?

https://github.com/rubygems/rubygems/commit/d434c98

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

From noreply at rubyforge.org  Fri Feb  4 15:33:16 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri,  4 Feb 2011 15:33:16 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28907 ] [RG 1.5.0/Ruby 1.9.x]
	source gem build error due to syck?
Message-ID: <20110204203316.79AF41858389@rubyforge.org>

Bugs item #28907, was opened at 2011-02-03 10:59
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

Category: `gem` commands (other)
Group: v1.5.x
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: Jon Forums (jonforums)
>Assigned to: Eric Hodel (drbrain)
Summary: [RG 1.5.0/Ruby 1.9.x] source gem build error due to syck?

Initial Comment:
When building a source gem from http://github.com/oopsforge/oops-null using 'rake gem' I get the following error on Win7 with:

  * ruby 1.9.2p174 (2011-01-28 revision 30696) [i386-mingw32]
  * ruby 1.9.3dev (2011-02-04 trunk 30776) [i386-mingw32]

but no errors using "ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32]".  

Manually building via 'gem build oops-null.gemspec' work fine on all the Ruby versions including JRuby 1.6.0.RC1.  All versions have been upgraded to RG 1.5.0 via "gem update --system".

FWIW, the failure does not occur on "ruby 1.9.2 (2010-12-25 patchlevel 136) [i386-mingw32]" using RG 1.3.7

My "fix" was to add the following lines to the project Rakefile after the 3 require's:

require 'yaml'
YAML::ENGINE.yamler='psych' if defined?(YAML::ENGINE)

I will try to replicate on my Arch system later this afternoon.

Reproducible?

Jon


== ERROR ==

C:\projects\oops-null-git>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.2 (2011-01-28 patchlevel 174) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/Users/Jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", "http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org


C:\projects\oops-null-git>rake gem
(in C:/projects/oops-null-git)
mkdir -p pkg
mkdir -p pkg
mkdir -p pkg/oops-null-0.3.0/bin
rm -f pkg/oops-null-0.3.0/bin/nulloops
ln bin/nulloops pkg/oops-null-0.3.0/bin/nulloops
rm -f pkg/oops-null-0.3.0/Rakefile
ln Rakefile pkg/oops-null-0.3.0/Rakefile
rm -f pkg/oops-null-0.3.0/oops-null.gemspec
ln oops-null.gemspec pkg/oops-null-0.3.0/oops-null.gemspec
mkdir -p pkg/oops-null-0.3.0/ext/oops_null
rm -f pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
ln ext/oops_null/extconf.rb pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
ln ext/oops_null/oops_null.c pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
ln ext/oops_null/oops_null.h pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
mkdir -p pkg/oops-null-0.3.0/lib
rm -f pkg/oops-null-0.3.0/lib/oops-null.rb
ln lib/oops-null.rb pkg/oops-null-0.3.0/lib/oops-null.rb
cd pkg/oops-null-0.3.0
rake aborted!
undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
C:/ruby192/lib/ruby/1.9.1/psych.rb:166:in `dump'
C:/ruby192/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block (2 levels) in to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `map'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `block in to_yaml'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `call'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `emit'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:725:in `to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1157:in `when_writing'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1092:in `chdir'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `call'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `block in execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:595:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:605:in `block in invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:594:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:581:in `invoke'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2041:in `invoke_task'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block (2 levels) in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2013:in `top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1992:in `run'
C:/ruby192/bin/rake:31:in `<main>'

----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 12:33

Message:
Do not mix syck (require 'yaml') and psych (require 'psych') in the same ruby.

RubyGems uses psych on ruby 1.9.2 and newer as syck is deprecated and will be removed at a future date.  Please update your Rakefile to match.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 06:53

Message:
same failure on "ruby 1.9.2p136 (2010-12-25) [i386-mingw32]" 
upgraded from RG 1.3.7 to RG 1.5.0

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-03 11:13

Message:
similar failure and working "fix" on Arch using:

ruby 1.9.3dev (2011-02-04 trunk 30776) [i686-linux]

RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.3 (2011-02-04 patchlevel -1) [i686-
linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.9.1
     - /home/jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", 
"http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

From noreply at rubyforge.org  Fri Feb  4 15:47:37 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri,  4 Feb 2011 15:47:37 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28909 ] rubygems 1.5.0
	uninitialized constant Gem::UserInteraction (NameError)
Message-ID: <20110204204737.B664B185837F@rubyforge.org>

Bugs item #28909, was opened at 2011-02-04 00:53
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28909&group_id=126

Category: other
Group: v1.5.x
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: John Mettraux (jmettraux)
>Assigned to: Eric Hodel (drbrain)
Summary: rubygems 1.5.0 uninitialized constant Gem::UserInteraction  (NameError)

Initial Comment:

# 1.8.7 or 1.9.2
# rubygems 1.5.0


require 'rubygems'

gemspec = Gem::Specification.new do |s|
end

gemspec.validate

 # ==>
 # /Users/toto/.rvm/rubies/ruby-1.8.7-p249/lib/ruby/site_ruby/1.8/rubygems/specification.rb:832:in `validate': uninitialized constant Gem::UserInteraction (NameError)
 #   from t.rb:8


----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 12:47

Message:
I put the require in #validate, thank you for the report.

https://github.com/rubygems/rubygems/commit/d37083cb

----------------------------------------------------------------------

Comment By: Torsten Sch?nebaum (tosch)
Date: 2011-02-04 01:24

Message:
Adding
require 'rubygems/user_interaction'
to lib/rubygems/specification.rb solves this issue for me.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28909&group_id=126

From noreply at rubyforge.org  Fri Feb  4 16:01:28 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri,  4 Feb 2011 16:01:28 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28907 ] [RG 1.5.0/Ruby 1.9.x]
	source gem build error due to syck?
Message-ID: <20110204210129.D0BB71678323@rubyforge.org>

Bugs item #28907, was opened at 2011-02-03 18:59
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

Category: `gem` commands (other)
Group: v1.5.x
Status: Closed
Resolution: Rejected
Priority: 3
Submitted By: Jon Forums (jonforums)
Assigned to: Eric Hodel (drbrain)
Summary: [RG 1.5.0/Ruby 1.9.x] source gem build error due to syck?

Initial Comment:
When building a source gem from http://github.com/oopsforge/oops-null using 'rake gem' I get the following error on Win7 with:

  * ruby 1.9.2p174 (2011-01-28 revision 30696) [i386-mingw32]
  * ruby 1.9.3dev (2011-02-04 trunk 30776) [i386-mingw32]

but no errors using "ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32]".  

Manually building via 'gem build oops-null.gemspec' work fine on all the Ruby versions including JRuby 1.6.0.RC1.  All versions have been upgraded to RG 1.5.0 via "gem update --system".

FWIW, the failure does not occur on "ruby 1.9.2 (2010-12-25 patchlevel 136) [i386-mingw32]" using RG 1.3.7

My "fix" was to add the following lines to the project Rakefile after the 3 require's:

require 'yaml'
YAML::ENGINE.yamler='psych' if defined?(YAML::ENGINE)

I will try to replicate on my Arch system later this afternoon.

Reproducible?

Jon


== ERROR ==

C:\projects\oops-null-git>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.2 (2011-01-28 patchlevel 174) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/Users/Jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", "http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org


C:\projects\oops-null-git>rake gem
(in C:/projects/oops-null-git)
mkdir -p pkg
mkdir -p pkg
mkdir -p pkg/oops-null-0.3.0/bin
rm -f pkg/oops-null-0.3.0/bin/nulloops
ln bin/nulloops pkg/oops-null-0.3.0/bin/nulloops
rm -f pkg/oops-null-0.3.0/Rakefile
ln Rakefile pkg/oops-null-0.3.0/Rakefile
rm -f pkg/oops-null-0.3.0/oops-null.gemspec
ln oops-null.gemspec pkg/oops-null-0.3.0/oops-null.gemspec
mkdir -p pkg/oops-null-0.3.0/ext/oops_null
rm -f pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
ln ext/oops_null/extconf.rb pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
ln ext/oops_null/oops_null.c pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
ln ext/oops_null/oops_null.h pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
mkdir -p pkg/oops-null-0.3.0/lib
rm -f pkg/oops-null-0.3.0/lib/oops-null.rb
ln lib/oops-null.rb pkg/oops-null-0.3.0/lib/oops-null.rb
cd pkg/oops-null-0.3.0
rake aborted!
undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
C:/ruby192/lib/ruby/1.9.1/psych.rb:166:in `dump'
C:/ruby192/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block (2 levels) in to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `map'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `block in to_yaml'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `call'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `emit'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:725:in `to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1157:in `when_writing'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1092:in `chdir'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `call'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `block in execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:595:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:605:in `block in invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:594:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:581:in `invoke'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2041:in `invoke_task'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block (2 levels) in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2013:in `top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1992:in `run'
C:/ruby192/bin/rake:31:in `<main>'

----------------------------------------------------------------------

>Comment By: Jon Forums (jonforums)
Date: 2011-02-04 21:01

Message:
That's not the issue, sorry I wasn't clear.  I'm not mixing 
syck or psyck in the same ruby in my code.

My original Rakefile https://github.com/oopsforge/oops-
null/blob/master/Rakefile that worked pre-1.5.0 didn't 
explicitly require 'yaml' or the YAML::ENGINE.yamler= 
nonsense.

I added these lines to get the gem to build when I saw the 
error message

undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in 
`end_document'
...

..as I guessed that explicitly setting the YAML engine to 
psych would prevent syck from being visited/wrapped by 
psych.

I think something's changed in RG 1.5.0 and/or ruby_1_9_2 or 
trunk that's causing the problem. I wanted to dig into how 
psych was visiting/wrapping syck but ran out of time. I also 
did a quick look through rake-compiler and don't think it's 
to blame.

Given that my original Rakefile fails on Win7 MRI 1.9.2-
p174, 1.9.2-p136, 1.9.3dev and Arch 1.9.3dev when using RG 
1.5.0 I still think the problem is in RG.

Hopefully I explained it more clearly this time.

Would you take one more look at that long back trace and see 
if you change your mind on the issue?

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 20:33

Message:
Do not mix syck (require 'yaml') and psych (require 'psych') in the same ruby.

RubyGems uses psych on ruby 1.9.2 and newer as syck is deprecated and will be removed at a future date.  Please update your Rakefile to match.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 14:53

Message:
same failure on "ruby 1.9.2p136 (2010-12-25) [i386-mingw32]" 
upgraded from RG 1.3.7 to RG 1.5.0

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-03 19:13

Message:
similar failure and working "fix" on Arch using:

ruby 1.9.3dev (2011-02-04 trunk 30776) [i686-linux]

RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.3 (2011-02-04 patchlevel -1) [i686-
linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.9.1
     - /home/jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", 
"http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

From noreply at rubyforge.org  Fri Feb  4 17:00:25 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri,  4 Feb 2011 17:00:25 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28900 ] Cygwin: Gem::SilentUI
	tries to open Windows' NUL file
Message-ID: <20110204220026.0D2421678324@rubyforge.org>

Bugs item #28900, was opened at 2011-02-01 19:16
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

Category: None
Group: v1.5.x
Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: S Shaw (skye)
Assigned to: Eric Hodel (drbrain)
Summary: Cygwin: Gem::SilentUI tries to open Windows' NUL file

Initial Comment:
>From user_interaction.rb:

class Gem::SilentUI < Gem::StreamUI

  def initialize

    reader, writer = nil, nil

    if Gem.win_platform?
      reader = File.open('nul', 'r')
      writer = File.open('nul', 'w')
    else
      reader = File.open('/dev/null', 'r')
      writer = File.open('/dev/null', 'w')
    end

    super reader, writer, writer
  end
end

When running on cygwin Gem::SilentUI will be in a POSIX environment where the NUL file is /dev/null. 

Skye at Skye-PC ~
$ ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2008-08-11 patchlevel 72) [i386-cygwin]
-e:1:in `initialize': No such file or directory - nul (Errno::ENOENT)
        from -e:1:in `open'
        from -e:1

Skye at Skye-PC ~
$ /cygdrive/c/Ruby187/bin/ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]


RubyGems version is 1.5


----------------------------------------------------------------------

Comment By: Tim Anderegg (tanderegg)
Date: 2011-02-04 17:00

Message:
Yes, sorry, I must have pulled down the source right before you committed the change, looks good!

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 15:29

Message:
Tim, check again, it's been committed, that's why there's a link to the commit below.

Closing this as it's been found to work via mailing-list reporters.

----------------------------------------------------------------------

Comment By: Tim Anderegg (tanderegg)
Date: 2011-02-03 16:45

Message:
Hello, I had this same problem, although the code listed below by Eric does indeed fix the problem, this fix has not yet been committed.

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-01 19:53

Message:
Can you verify this is fixed in rubygems trunk?

https://github.com/rubygems/rubygems/commit/d434c98

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

From noreply at rubyforge.org  Fri Feb  4 17:17:26 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri,  4 Feb 2011 17:17:26 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28900 ] Cygwin: Gem::SilentUI
	tries to open Windows' NUL file
Message-ID: <20110204221726.15B2D1858379@rubyforge.org>

Bugs item #28900, was opened at 2011-02-02 00:16
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

Category: None
Group: v1.5.x
Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: S Shaw (skye)
Assigned to: Eric Hodel (drbrain)
Summary: Cygwin: Gem::SilentUI tries to open Windows' NUL file

Initial Comment:
>From user_interaction.rb:

class Gem::SilentUI < Gem::StreamUI

  def initialize

    reader, writer = nil, nil

    if Gem.win_platform?
      reader = File.open('nul', 'r')
      writer = File.open('nul', 'w')
    else
      reader = File.open('/dev/null', 'r')
      writer = File.open('/dev/null', 'w')
    end

    super reader, writer, writer
  end
end

When running on cygwin Gem::SilentUI will be in a POSIX environment where the NUL file is /dev/null. 

Skye at Skye-PC ~
$ ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2008-08-11 patchlevel 72) [i386-cygwin]
-e:1:in `initialize': No such file or directory - nul (Errno::ENOENT)
        from -e:1:in `open'
        from -e:1

Skye at Skye-PC ~
$ /cygdrive/c/Ruby187/bin/ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]


RubyGems version is 1.5


----------------------------------------------------------------------

Comment By: S Shaw (skye)
Date: 2011-02-04 22:17

Message:
Verified. TestGemSilentUI now passes. 

----------------------------------------------------------------------

Comment By: Tim Anderegg (tanderegg)
Date: 2011-02-04 22:00

Message:
Yes, sorry, I must have pulled down the source right before you committed the change, looks good!

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 20:29

Message:
Tim, check again, it's been committed, that's why there's a link to the commit below.

Closing this as it's been found to work via mailing-list reporters.

----------------------------------------------------------------------

Comment By: Tim Anderegg (tanderegg)
Date: 2011-02-03 21:45

Message:
Hello, I had this same problem, although the code listed below by Eric does indeed fix the problem, this fix has not yet been committed.

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-02 00:53

Message:
Can you verify this is fixed in rubygems trunk?

https://github.com/rubygems/rubygems/commit/d434c98

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

From noreply at rubyforge.org  Fri Feb  4 17:17:29 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri,  4 Feb 2011 17:17:29 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28900 ] Cygwin: Gem::SilentUI
	tries to open Windows' NUL file
Message-ID: <20110204221730.0E0B6185837F@rubyforge.org>

Bugs item #28900, was opened at 2011-02-02 00:16
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

Category: None
Group: v1.5.x
Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: S Shaw (skye)
Assigned to: Eric Hodel (drbrain)
Summary: Cygwin: Gem::SilentUI tries to open Windows' NUL file

Initial Comment:
>From user_interaction.rb:

class Gem::SilentUI < Gem::StreamUI

  def initialize

    reader, writer = nil, nil

    if Gem.win_platform?
      reader = File.open('nul', 'r')
      writer = File.open('nul', 'w')
    else
      reader = File.open('/dev/null', 'r')
      writer = File.open('/dev/null', 'w')
    end

    super reader, writer, writer
  end
end

When running on cygwin Gem::SilentUI will be in a POSIX environment where the NUL file is /dev/null. 

Skye at Skye-PC ~
$ ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2008-08-11 patchlevel 72) [i386-cygwin]
-e:1:in `initialize': No such file or directory - nul (Errno::ENOENT)
        from -e:1:in `open'
        from -e:1

Skye at Skye-PC ~
$ /cygdrive/c/Ruby187/bin/ruby -ve'File.open("nul","r")'
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]


RubyGems version is 1.5


----------------------------------------------------------------------

Comment By: S Shaw (skye)
Date: 2011-02-04 22:17

Message:
Verified. TestGemSilentUI now passes. 

----------------------------------------------------------------------

Comment By: S Shaw (skye)
Date: 2011-02-04 22:17

Message:
Verified. TestGemSilentUI now passes. 

----------------------------------------------------------------------

Comment By: Tim Anderegg (tanderegg)
Date: 2011-02-04 22:00

Message:
Yes, sorry, I must have pulled down the source right before you committed the change, looks good!

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 20:29

Message:
Tim, check again, it's been committed, that's why there's a link to the commit below.

Closing this as it's been found to work via mailing-list reporters.

----------------------------------------------------------------------

Comment By: Tim Anderegg (tanderegg)
Date: 2011-02-03 21:45

Message:
Hello, I had this same problem, although the code listed below by Eric does indeed fix the problem, this fix has not yet been committed.

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-02 00:53

Message:
Can you verify this is fixed in rubygems trunk?

https://github.com/rubygems/rubygems/commit/d434c98

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28900&group_id=126

From thewoolleyman at gmail.com  Fri Feb  4 17:39:33 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Fri, 4 Feb 2011 15:39:33 -0700
Subject: [Rubygems-developers] Release coming,
 but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
	<2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
	<A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>
	<AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>
Message-ID: <AANLkTinL+QuNSCdQ0=zpyMK2J=1hSi7W3gzve2yNzobP@mail.gmail.com>

On Mon, Jan 31, 2011 at 11:04 PM, Chad Woolley <thewoolleyman at gmail.com> wrote:
> On the emails - I didn't want to unilaterally spam people, so you have
> to opt-in to receive the emails, or turn them on for this entire list.
> ?I've made this easily configurable, so have at it if you want to
> opt-in to the emails or want them to go to the entire list:
>
> https://github.com/rubygems/rubygems/blob/master/cruise_config.rb#L13

Builds just broke, but I see I am still the only person opting in to
the emails, and they are not pointed at the list.

Do you want me to just point them at the list now?  Is it stable?

From ryand-ruby at zenspider.com  Fri Feb  4 18:01:55 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Fri, 4 Feb 2011 15:01:55 -0800
Subject: [Rubygems-developers] Release coming,
	but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTinL+QuNSCdQ0=zpyMK2J=1hSi7W3gzve2yNzobP@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
	<2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
	<A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>
	<AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>
	<AANLkTinL+QuNSCdQ0=zpyMK2J=1hSi7W3gzve2yNzobP@mail.gmail.com>
Message-ID: <DD4545B3-4E0C-44EC-BCDC-302E2D184AF7@zenspider.com>


On Feb 4, 2011, at 14:39 , Chad Woolley wrote:

> Builds just broke, but I see I am still the only person opting in to
> the emails, and they are not pointed at the list.
> 
> Do you want me to just point them at the list now?  Is it stable?

Not yet. I'm not willing to have it pointing at the list until it is more trustworthy.


From noreply at rubyforge.org  Fri Feb  4 18:37:06 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri,  4 Feb 2011 18:37:06 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28907 ] [RG 1.5.0/Ruby 1.9.x]
	source gem build error due to syck?
Message-ID: <20110204233706.9F24A1858389@rubyforge.org>

Bugs item #28907, was opened at 2011-02-03 10:59
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

Category: `gem` commands (other)
Group: v1.5.x
Status: Closed
Resolution: Rejected
Priority: 3
Submitted By: Jon Forums (jonforums)
Assigned to: Eric Hodel (drbrain)
Summary: [RG 1.5.0/Ruby 1.9.x] source gem build error due to syck?

Initial Comment:
When building a source gem from http://github.com/oopsforge/oops-null using 'rake gem' I get the following error on Win7 with:

  * ruby 1.9.2p174 (2011-01-28 revision 30696) [i386-mingw32]
  * ruby 1.9.3dev (2011-02-04 trunk 30776) [i386-mingw32]

but no errors using "ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32]".  

Manually building via 'gem build oops-null.gemspec' work fine on all the Ruby versions including JRuby 1.6.0.RC1.  All versions have been upgraded to RG 1.5.0 via "gem update --system".

FWIW, the failure does not occur on "ruby 1.9.2 (2010-12-25 patchlevel 136) [i386-mingw32]" using RG 1.3.7

My "fix" was to add the following lines to the project Rakefile after the 3 require's:

require 'yaml'
YAML::ENGINE.yamler='psych' if defined?(YAML::ENGINE)

I will try to replicate on my Arch system later this afternoon.

Reproducible?

Jon


== ERROR ==

C:\projects\oops-null-git>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.2 (2011-01-28 patchlevel 174) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/Users/Jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", "http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org


C:\projects\oops-null-git>rake gem
(in C:/projects/oops-null-git)
mkdir -p pkg
mkdir -p pkg
mkdir -p pkg/oops-null-0.3.0/bin
rm -f pkg/oops-null-0.3.0/bin/nulloops
ln bin/nulloops pkg/oops-null-0.3.0/bin/nulloops
rm -f pkg/oops-null-0.3.0/Rakefile
ln Rakefile pkg/oops-null-0.3.0/Rakefile
rm -f pkg/oops-null-0.3.0/oops-null.gemspec
ln oops-null.gemspec pkg/oops-null-0.3.0/oops-null.gemspec
mkdir -p pkg/oops-null-0.3.0/ext/oops_null
rm -f pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
ln ext/oops_null/extconf.rb pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
ln ext/oops_null/oops_null.c pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
ln ext/oops_null/oops_null.h pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
mkdir -p pkg/oops-null-0.3.0/lib
rm -f pkg/oops-null-0.3.0/lib/oops-null.rb
ln lib/oops-null.rb pkg/oops-null-0.3.0/lib/oops-null.rb
cd pkg/oops-null-0.3.0
rake aborted!
undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
C:/ruby192/lib/ruby/1.9.1/psych.rb:166:in `dump'
C:/ruby192/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block (2 levels) in to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `map'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `block in to_yaml'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `call'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `emit'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:725:in `to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1157:in `when_writing'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1092:in `chdir'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `call'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `block in execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:595:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:605:in `block in invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:594:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:581:in `invoke'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2041:in `invoke_task'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block (2 levels) in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2013:in `top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1992:in `run'
C:/ruby192/bin/rake:31:in `<main>'

----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 15:37

Message:
Yes, you are loading syck (require 'yaml') before psych (require 'psych'):

https://github.com/luislavena/rake-compiler/blob/master/lib/rake/baseextensiontask.rb

This is not supported.

A patch will be sent to rake-compiler.

You can work around this by requiring psych before rake-compiler.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 13:01

Message:
That's not the issue, sorry I wasn't clear.  I'm not mixing 
syck or psyck in the same ruby in my code.

My original Rakefile https://github.com/oopsforge/oops-
null/blob/master/Rakefile that worked pre-1.5.0 didn't 
explicitly require 'yaml' or the YAML::ENGINE.yamler= 
nonsense.

I added these lines to get the gem to build when I saw the 
error message

undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in 
`end_document'
...

..as I guessed that explicitly setting the YAML engine to 
psych would prevent syck from being visited/wrapped by 
psych.

I think something's changed in RG 1.5.0 and/or ruby_1_9_2 or 
trunk that's causing the problem. I wanted to dig into how 
psych was visiting/wrapping syck but ran out of time. I also 
did a quick look through rake-compiler and don't think it's 
to blame.

Given that my original Rakefile fails on Win7 MRI 1.9.2-
p174, 1.9.2-p136, 1.9.3dev and Arch 1.9.3dev when using RG 
1.5.0 I still think the problem is in RG.

Hopefully I explained it more clearly this time.

Would you take one more look at that long back trace and see 
if you change your mind on the issue?

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 12:33

Message:
Do not mix syck (require 'yaml') and psych (require 'psych') in the same ruby.

RubyGems uses psych on ruby 1.9.2 and newer as syck is deprecated and will be removed at a future date.  Please update your Rakefile to match.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 06:53

Message:
same failure on "ruby 1.9.2p136 (2010-12-25) [i386-mingw32]" 
upgraded from RG 1.3.7 to RG 1.5.0

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-03 11:13

Message:
similar failure and working "fix" on Arch using:

ruby 1.9.3dev (2011-02-04 trunk 30776) [i686-linux]

RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.3 (2011-02-04 patchlevel -1) [i686-
linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.9.1
     - /home/jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", 
"http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

From thewoolleyman at gmail.com  Fri Feb  4 19:44:19 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Fri, 4 Feb 2011 17:44:19 -0700
Subject: [Rubygems-developers] Release coming,
 but still no response on broken 1.9.x CI builds
In-Reply-To: <DD4545B3-4E0C-44EC-BCDC-302E2D184AF7@zenspider.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
	<2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
	<A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>
	<AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>
	<AANLkTinL+QuNSCdQ0=zpyMK2J=1hSi7W3gzve2yNzobP@mail.gmail.com>
	<DD4545B3-4E0C-44EC-BCDC-302E2D184AF7@zenspider.com>
Message-ID: <AANLkTikTCUxnO+mXD1KYqsx9=wYtT57cjeCaqwe_zbLR@mail.gmail.com>

On Fri, Feb 4, 2011 at 4:01 PM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
> Not yet. I'm not willing to have it pointing at the list until it is more trustworthy.

Please elaborate on what you think is untrustworthy.  As well as
perhaps some make some effort to answer my detailed requests for
feedback which you have thusfar ignored.

Hugs,
-- Chad

From thewoolleyman at gmail.com  Fri Feb  4 20:51:07 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Fri, 4 Feb 2011 18:51:07 -0700
Subject: [Rubygems-developers] Release coming,
 but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTikTCUxnO+mXD1KYqsx9=wYtT57cjeCaqwe_zbLR@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
	<2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
	<A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>
	<AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>
	<AANLkTinL+QuNSCdQ0=zpyMK2J=1hSi7W3gzve2yNzobP@mail.gmail.com>
	<DD4545B3-4E0C-44EC-BCDC-302E2D184AF7@zenspider.com>
	<AANLkTikTCUxnO+mXD1KYqsx9=wYtT57cjeCaqwe_zbLR@mail.gmail.com>
Message-ID: <AANLkTimXwBwyRve9ZgUPPS3A1nnwZUp3LjdcUkiKHr0X@mail.gmail.com>

On Fri, Feb 4, 2011 at 5:44 PM, Chad Woolley <thewoolleyman at gmail.com> wrote:
> On Fri, Feb 4, 2011 at 4:01 PM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
>> Not yet. I'm not willing to have it pointing at the list until it is more trustworthy.
>
> Please elaborate on what you think is untrustworthy. ?As well as
> perhaps some make some effort to answer my detailed requests for
> feedback which you have thusfar ignored.
>
> Hugs,
> -- Chad

If you ignore this too, I'm going to start sending notifications to
the list again.

I've responded to everything promptly, and indicated where I'm
deferring things that I don't have time for right now.

AFAIK it is stable, running all the requested interpreters, and I've
gone to extra effort to make it easy for any committer to turn off
emails for selected builds if they go awry, as well as selectively
opt-in to them.

The committers on this project asked for CI, and I have provided it.
I don't have the time nor inclination to play whatever power trip
games you are playing with your selective communication.  It is
immature, disrespectful, and uncalled for.

Thanks,
-- Chad

From rick.denatale at gmail.com  Sat Feb  5 10:10:04 2011
From: rick.denatale at gmail.com (Rick DeNatale)
Date: Sat, 5 Feb 2011 10:10:04 -0500
Subject: [Rubygems-developers] Bundler and prerelease gems
Message-ID: <AANLkTikv2T_Od478fzmxVnYYhakDeCzfQ2neOoSky1ur@mail.gmail.com>

Is it possible to tell bundler to load a prerelease version of a gem?

I'm using the latest prawn and was using the git option in the Gemfile
to get Prawn 10.x.  Recently I needed to also tag a reference because
of changes made to the submoduled components.

I now notice that there are prerelease prawn gems, which gem list
--prerelease can see.

But I can't seem to find anywhere in the bundler documentation how to
tell bundler to consider a prerelease version.

-- 
Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Github: http://github.com/rubyredrick
Twitter: @RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale

From luislavena at gmail.com  Sat Feb  5 10:51:43 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Sat, 5 Feb 2011 12:51:43 -0300
Subject: [Rubygems-developers] Bundler and prerelease gems
In-Reply-To: <AANLkTikv2T_Od478fzmxVnYYhakDeCzfQ2neOoSky1ur@mail.gmail.com>
References: <AANLkTikv2T_Od478fzmxVnYYhakDeCzfQ2neOoSky1ur@mail.gmail.com>
Message-ID: <AANLkTikS5q1b2krheni=TG7MCFEd1gi5jvVQqXNghPhK@mail.gmail.com>

On Sat, Feb 5, 2011 at 12:10 PM, Rick DeNatale <rick.denatale at gmail.com> wrote:
> Is it possible to tell bundler to load a prerelease version of a gem?
>
> I'm using the latest prawn and was using the git option in the Gemfile
> to get Prawn 10.x. ?Recently I needed to also tag a reference because
> of changes made to the submoduled components.
>
> I now notice that there are prerelease prawn gems, which gem list
> --prerelease can see.
>
> But I can't seem to find anywhere in the bundler documentation how to
> tell bundler to consider a prerelease version.
>

I believe you can specify the version directly, like this:

gem "prawn", "~> 0.11.1.pre"

At least that works with Isolate.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From drbrain at segment7.net  Sat Feb  5 16:30:09 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Sat, 5 Feb 2011 13:30:09 -0800
Subject: [Rubygems-developers] Bundler and prerelease gems
In-Reply-To: <AANLkTikv2T_Od478fzmxVnYYhakDeCzfQ2neOoSky1ur@mail.gmail.com>
References: <AANLkTikv2T_Od478fzmxVnYYhakDeCzfQ2neOoSky1ur@mail.gmail.com>
Message-ID: <6D6D315B-5C9A-4A92-A29F-16EB5047AB7A@segment7.net>

On Feb 5, 2011, at 7:10 AM, Rick DeNatale wrote:

> Is it possible to tell bundler to load a prerelease version of a gem?
> 
> I'm using the latest prawn and was using the git option in the Gemfile
> to get Prawn 10.x.  Recently I needed to also tag a reference because
> of changes made to the submoduled components.
> 
> I now notice that there are prerelease prawn gems, which gem list
> --prerelease can see.
> 
> But I can't seem to find anywhere in the bundler documentation how to
> tell bundler to consider a prerelease version.

Maybe the bundler list would know.

From noreply at rubyforge.org  Sat Feb  5 17:00:36 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat,  5 Feb 2011 17:00:36 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28907 ] [RG 1.5.0/Ruby 1.9.x]
	source gem build error due to syck?
Message-ID: <20110205220036.D34341678324@rubyforge.org>

Bugs item #28907, was opened at 2011-02-03 18:59
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

Category: `gem` commands (other)
Group: v1.5.x
Status: Closed
Resolution: Rejected
Priority: 3
Submitted By: Jon Forums (jonforums)
Assigned to: Eric Hodel (drbrain)
Summary: [RG 1.5.0/Ruby 1.9.x] source gem build error due to syck?

Initial Comment:
When building a source gem from http://github.com/oopsforge/oops-null using 'rake gem' I get the following error on Win7 with:

  * ruby 1.9.2p174 (2011-01-28 revision 30696) [i386-mingw32]
  * ruby 1.9.3dev (2011-02-04 trunk 30776) [i386-mingw32]

but no errors using "ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32]".  

Manually building via 'gem build oops-null.gemspec' work fine on all the Ruby versions including JRuby 1.6.0.RC1.  All versions have been upgraded to RG 1.5.0 via "gem update --system".

FWIW, the failure does not occur on "ruby 1.9.2 (2010-12-25 patchlevel 136) [i386-mingw32]" using RG 1.3.7

My "fix" was to add the following lines to the project Rakefile after the 3 require's:

require 'yaml'
YAML::ENGINE.yamler='psych' if defined?(YAML::ENGINE)

I will try to replicate on my Arch system later this afternoon.

Reproducible?

Jon


== ERROR ==

C:\projects\oops-null-git>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.2 (2011-01-28 patchlevel 174) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/Users/Jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", "http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org


C:\projects\oops-null-git>rake gem
(in C:/projects/oops-null-git)
mkdir -p pkg
mkdir -p pkg
mkdir -p pkg/oops-null-0.3.0/bin
rm -f pkg/oops-null-0.3.0/bin/nulloops
ln bin/nulloops pkg/oops-null-0.3.0/bin/nulloops
rm -f pkg/oops-null-0.3.0/Rakefile
ln Rakefile pkg/oops-null-0.3.0/Rakefile
rm -f pkg/oops-null-0.3.0/oops-null.gemspec
ln oops-null.gemspec pkg/oops-null-0.3.0/oops-null.gemspec
mkdir -p pkg/oops-null-0.3.0/ext/oops_null
rm -f pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
ln ext/oops_null/extconf.rb pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
ln ext/oops_null/oops_null.c pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
ln ext/oops_null/oops_null.h pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
mkdir -p pkg/oops-null-0.3.0/lib
rm -f pkg/oops-null-0.3.0/lib/oops-null.rb
ln lib/oops-null.rb pkg/oops-null-0.3.0/lib/oops-null.rb
cd pkg/oops-null-0.3.0
rake aborted!
undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
C:/ruby192/lib/ruby/1.9.1/psych.rb:166:in `dump'
C:/ruby192/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block (2 levels) in to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `map'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `block in to_yaml'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `call'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `emit'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:725:in `to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1157:in `when_writing'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1092:in `chdir'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `call'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `block in execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:595:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:605:in `block in invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:594:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:581:in `invoke'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2041:in `invoke_task'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block (2 levels) in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2013:in `top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1992:in `run'
C:/ruby192/bin/rake:31:in `<main>'

----------------------------------------------------------------------

>Comment By: Jon Forums (jonforums)
Date: 2011-02-05 22:00

Message:
All OK now with the updated rake-compiler.

So I'm clear, this is the main commit to pay attention to?

https://github.com/rubygems/rubygems/commit/67f9f760c782142d9bfd8099750274ba498d6682

Given the simple tweak to rake-compiler, is your
recommendation that other gems requiring yaml also prefer
psych when running on 1.9.2+ and RG 1.5.0+

FWIW, I personally like the idea of preferring psych, but
would like to have first seen it mentioned in one of the
following rather than in a bt:

http://blog.segment7.net/2011/01/31/rubygems-1-5

https://github.com/rubygems/rubygems/blob/master/UPGRADING.rdoc 

Jon

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 23:37

Message:
Yes, you are loading syck (require 'yaml') before psych (require 'psych'):

https://github.com/luislavena/rake-compiler/blob/master/lib/rake/baseextensiontask.rb

This is not supported.

A patch will be sent to rake-compiler.

You can work around this by requiring psych before rake-compiler.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 21:01

Message:
That's not the issue, sorry I wasn't clear.  I'm not mixing 
syck or psyck in the same ruby in my code.

My original Rakefile https://github.com/oopsforge/oops-
null/blob/master/Rakefile that worked pre-1.5.0 didn't 
explicitly require 'yaml' or the YAML::ENGINE.yamler= 
nonsense.

I added these lines to get the gem to build when I saw the 
error message

undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in 
`end_document'
...

..as I guessed that explicitly setting the YAML engine to 
psych would prevent syck from being visited/wrapped by 
psych.

I think something's changed in RG 1.5.0 and/or ruby_1_9_2 or 
trunk that's causing the problem. I wanted to dig into how 
psych was visiting/wrapping syck but ran out of time. I also 
did a quick look through rake-compiler and don't think it's 
to blame.

Given that my original Rakefile fails on Win7 MRI 1.9.2-
p174, 1.9.2-p136, 1.9.3dev and Arch 1.9.3dev when using RG 
1.5.0 I still think the problem is in RG.

Hopefully I explained it more clearly this time.

Would you take one more look at that long back trace and see 
if you change your mind on the issue?

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 20:33

Message:
Do not mix syck (require 'yaml') and psych (require 'psych') in the same ruby.

RubyGems uses psych on ruby 1.9.2 and newer as syck is deprecated and will be removed at a future date.  Please update your Rakefile to match.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 14:53

Message:
same failure on "ruby 1.9.2p136 (2010-12-25) [i386-mingw32]" 
upgraded from RG 1.3.7 to RG 1.5.0

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-03 19:13

Message:
similar failure and working "fix" on Arch using:

ruby 1.9.3dev (2011-02-04 trunk 30776) [i686-linux]

RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.3 (2011-02-04 patchlevel -1) [i686-
linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.9.1
     - /home/jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", 
"http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

From thewoolleyman at gmail.com  Sun Feb  6 22:51:31 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sun, 6 Feb 2011 20:51:31 -0700
Subject: [Rubygems-developers] Release coming,
 but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTikTCUxnO+mXD1KYqsx9=wYtT57cjeCaqwe_zbLR@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
	<2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
	<A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>
	<AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>
	<AANLkTinL+QuNSCdQ0=zpyMK2J=1hSi7W3gzve2yNzobP@mail.gmail.com>
	<DD4545B3-4E0C-44EC-BCDC-302E2D184AF7@zenspider.com>
	<AANLkTikTCUxnO+mXD1KYqsx9=wYtT57cjeCaqwe_zbLR@mail.gmail.com>
Message-ID: <AANLkTim2+rPsMX8ohjode4fTyEi8OgLn97fW3302=+AX@mail.gmail.com>

On Fri, Feb 4, 2011 at 5:44 PM, Chad Woolley <thewoolleyman at gmail.com> wrote:
> Please elaborate on what you think is untrustworthy. ?As well as
> perhaps some make some effort to answer my detailed requests for
> feedback which you have thusfar ignored.

I have turned on email notifications to this list for the following
green and currently-stable builds (pending list membership approval
for thewoolleyman+rubygems-ci at gmail.com as sender):

http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_8_7-p330
http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_1-p378
http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p136

All notifications are configurable by committers via cruise_config.rb.

Still no response (after multiple requests) about Hoe's problems
supporting non-sudo check_extra_deps in Rakefile, for which there is
an unapplied patch almost a year old:

http://rubyforge.org/tracker/index.php?func=detail&aid=27881&group_id=1513&atid=5923

This means I'm still installing dependencies in with duplicate non-dry
logic and versions, which is IMO the most unstable thing about the
build right now.

This is done for now AFAIK.  I'll fix any problems which come up with
the current environment ASAP, and I'll work on floating patch levels
and other platforms at some point in the future.

Thanks,
-- Chad

From drbrain at segment7.net  Mon Feb  7 14:18:42 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Mon, 7 Feb 2011 11:18:42 -0800
Subject: [Rubygems-developers] Release coming,
	but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTimXwBwyRve9ZgUPPS3A1nnwZUp3LjdcUkiKHr0X@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
	<2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
	<A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>
	<AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>
	<AANLkTinL+QuNSCdQ0=zpyMK2J=1hSi7W3gzve2yNzobP@mail.gmail.com>
	<DD4545B3-4E0C-44EC-BCDC-302E2D184AF7@zenspider.com>
	<AANLkTikTCUxnO+mXD1KYqsx9=wYtT57cjeCaqwe_zbLR@mail.gmail.com>
	<AANLkTimXwBwyRve9ZgUPPS3A1nnwZUp3LjdcUkiKHr0X@mail.gmail.com>
Message-ID: <06F46F1C-A1A2-4E2D-8BE7-85AB6A64721C@segment7.net>

On Feb 4, 2011, at 5:51 PM, Chad Woolley wrote:
> On Fri, Feb 4, 2011 at 5:44 PM, Chad Woolley <thewoolleyman at gmail.com> wrote:
>> On Fri, Feb 4, 2011 at 4:01 PM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
>>> Not yet. I'm not willing to have it pointing at the list until it is more trustworthy.
>> 
>> Please elaborate on what you think is untrustworthy.  As well as
>> perhaps some make some effort to answer my detailed requests for
>> feedback which you have thusfar ignored.
>> 
>> Hugs,
>> -- Chad
> 
> If you ignore this too, I'm going to start sending notifications to
> the list again.

This is inappropriate, silence does not equate to success.

> I've responded to everything promptly, and indicated where I'm
> deferring things that I don't have time for right now.
> 
> AFAIK it is stable, running all the requested interpreters, and I've
> gone to extra effort to make it easy for any committer to turn off
> emails for selected builds if they go awry, as well as selectively
> opt-in to them.
> 
> The committers on this project asked for CI, and I have provided it.
> I don't have the time nor inclination to play whatever power trip
> games you are playing with your selective communication.  It is
> immature, disrespectful, and uncalled for.

If there's going to be this level of argument over the CI I don't think it's prudent to continue to use it.  When I make releases I don't bother to consult it, instead I run `rake multi`.

How many people have subscribed to the CI?  Going back to the beginning of December myself, Ryan and Luis have been the top committers.

If anything, our least-covered platform is Windows as Luis is our de-facto CI.  Running CI on linux isn't going to help us much.

From ryand-ruby at zenspider.com  Mon Feb  7 14:56:42 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Mon, 7 Feb 2011 11:56:42 -0800
Subject: [Rubygems-developers] Release coming,
	but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTimXwBwyRve9ZgUPPS3A1nnwZUp3LjdcUkiKHr0X@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
	<2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
	<A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>
	<AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>
	<AANLkTinL+QuNSCdQ0=zpyMK2J=1hSi7W3gzve2yNzobP@mail.gmail.com>
	<DD4545B3-4E0C-44EC-BCDC-302E2D184AF7@zenspider.com>
	<AANLkTikTCUxnO+mXD1KYqsx9=wYtT57cjeCaqwe_zbLR@mail.gmail.com>
	<AANLkTimXwBwyRve9ZgUPPS3A1nnwZUp3LjdcUkiKHr0X@mail.gmail.com>
Message-ID: <BCDD921B-7D7D-4780-B49E-E84A2C9E95F6@zenspider.com>


On Feb 4, 2011, at 17:51 , Chad Woolley wrote:

> I don't have the time nor inclination to play whatever power trip
> games you are playing with your selective communication.  It is
> immature, disrespectful, and uncalled for.

Strike one was in December with your temper tantrum. This is strike two. I don't do strike three.

I'm absolutely 100% done with you and your histrionics.

This is the last mail you'll ever get from me.


From thewoolleyman at gmail.com  Mon Feb  7 14:57:32 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Mon, 7 Feb 2011 12:57:32 -0700
Subject: [Rubygems-developers] Release coming,
 but still no response on broken 1.9.x CI builds
In-Reply-To: <06F46F1C-A1A2-4E2D-8BE7-85AB6A64721C@segment7.net>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
	<2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
	<A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>
	<AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>
	<AANLkTinL+QuNSCdQ0=zpyMK2J=1hSi7W3gzve2yNzobP@mail.gmail.com>
	<DD4545B3-4E0C-44EC-BCDC-302E2D184AF7@zenspider.com>
	<AANLkTikTCUxnO+mXD1KYqsx9=wYtT57cjeCaqwe_zbLR@mail.gmail.com>
	<AANLkTimXwBwyRve9ZgUPPS3A1nnwZUp3LjdcUkiKHr0X@mail.gmail.com>
	<06F46F1C-A1A2-4E2D-8BE7-85AB6A64721C@segment7.net>
Message-ID: <AANLkTin0P=qO8GN3B_QH61gh5hTFzpNU1Fm846+6S6Ua@mail.gmail.com>

On Mon, Feb 7, 2011 at 12:18 PM, Eric Hodel <drbrain at segment7.net> wrote:
>> If you ignore this too, I'm going to start sending notifications to
>> the list again.
>
> This is inappropriate, silence does not equate to success.

CI is running for the major linux platforms with failure notifications
going to this list.  It's done.

> If there's going to be this level of argument over the CI I don't think it's prudent to continue to use it.

I'm not arguing, I made it happen.  During the last developers
meeting, CI was one request that came out of it.  I made it happen for
the three currently supported interpreters (1.8.7/1.9.1/1.9.2) on the
most popular production platform (linux).  The only known drawback
with this environment is Hoe's incompatibility with sudo, which has an
unapplied fix, and which I've pointed out multiple times and you/Ryan
have ignored multiple times.  This is not just a problem for CI also a
problem for anyone who wants to run the rubygems build under RVM.
Repeatedly pointing out that this is still unfixed is not arguing.
Continuing to not just fixing the problem in Hoe IS increasing the
noise on this list by forcing me to repeatedly ask for it, and you
have incorrectly equated this noise to arguing.

>  When I make releases I don't bother to consult it, instead I run `rake multi`.

All RubyGems committers != You and Ryan

> How many people have subscribed to the CI?

Everyone on this list now.

> ?Going back to the beginning of December myself, Ryan and Luis have been the top committers.

I don't see your point.  All RubyGems committers != You and Ryan

> If anything, our least-covered platform is Windows as Luis is our de-facto CI. ?Running CI on linux isn't going to help us much.

Correct, it isn't going to help much with windows coverage.  It will
help tremendously with immediately identifying platform-independent
regressions (which are the majority, I would guess) where the
committer is not you or Ryan and does not run 'rake multi' before
checking in.  Do not confuse lack of windows CI coverage with lack of
value in Linux CI coverage, that is a non sequitur logical fallacy.

Bottom line:

* The RubyGems committers said they wanted CI.  I have done it on
linux, and will maintain it.
* It is stable as of now, with failure notifications going to this
list, which can easily be disabled by any committer if they go haywire
and I'm not around to fix it.
* A side benefit is that the build is standardized and locally
reproducible via the ci_build script included in the source.

Thanks,
-- Chad

From thewoolleyman at gmail.com  Mon Feb  7 15:01:54 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Mon, 7 Feb 2011 13:01:54 -0700
Subject: [Rubygems-developers] Release coming,
 but still no response on broken 1.9.x CI builds
In-Reply-To: <BCDD921B-7D7D-4780-B49E-E84A2C9E95F6@zenspider.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
	<2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
	<A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>
	<AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>
	<AANLkTinL+QuNSCdQ0=zpyMK2J=1hSi7W3gzve2yNzobP@mail.gmail.com>
	<DD4545B3-4E0C-44EC-BCDC-302E2D184AF7@zenspider.com>
	<AANLkTikTCUxnO+mXD1KYqsx9=wYtT57cjeCaqwe_zbLR@mail.gmail.com>
	<AANLkTimXwBwyRve9ZgUPPS3A1nnwZUp3LjdcUkiKHr0X@mail.gmail.com>
	<BCDD921B-7D7D-4780-B49E-E84A2C9E95F6@zenspider.com>
Message-ID: <AANLkTi=+CP_rdx95GiAF+jX+thLtMC_x1U62Gxa8TzRX@mail.gmail.com>

On Mon, Feb 7, 2011 at 12:56 PM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
>
> On Feb 4, 2011, at 17:51 , Chad Woolley wrote:
>
>> I don't have the time nor inclination to play whatever power trip
>> games you are playing with your selective communication. ?It is
>> immature, disrespectful, and uncalled for.
>
> Strike one was in December with your temper tantrum. This is strike two. I don't do strike three.
>
> I'm absolutely 100% done with you and your histrionics.

Review this thread objectively.  I have been verbose, and critical of
your selective unresponsiveness, but otherwise calm and fair.  I don't
believe 'histronics' can be applied to my behavior in this particular
thread. Please point out where I have done otherwise.

>
> This is the last mail you'll ever get from me.

Great!  As long as you don't interfere with my contributions to the
RubyGems community, that will work out great for us.

And you have still ignored my request to apply the Hoe patch to
disable usage of sudo.  That is irresponsible.

Thanks,
-- Chad

From thewoolleyman at gmail.com  Mon Feb  7 19:43:34 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Mon, 7 Feb 2011 17:43:34 -0700
Subject: [Rubygems-developers] Release coming,
 but still no response on broken 1.9.x CI builds
In-Reply-To: <AANLkTi=+CP_rdx95GiAF+jX+thLtMC_x1U62Gxa8TzRX@mail.gmail.com>
References: <AANLkTi=dye+Q9JYUtghGaiB-+rGDisV9xUZPt8sBOQMK@mail.gmail.com>
	<300AF5C3-C708-436E-86E5-F83000C61DC2@segment7.net>
	<2C5AB12B-5171-4A2B-BD80-85AA15CF877E@zenspider.com>
	<AANLkTikL-Py6+x3xgBpW=tSL3E8J1GgWTvByT8GWYmnW@mail.gmail.com>
	<AANLkTinA7Y3Vm2NxfPNoHMneS0fvfpEbepMetn9Ega2O@mail.gmail.com>
	<2007E31F-80D0-4808-BDCA-0D964F39F00C@zenspider.com>
	<A93F48C0-BD9D-46E0-975F-BD92E051F8CB@segment7.net>
	<AANLkTinieujTBO71mER3trRSR31d3y+_zopuCuyfzNeg@mail.gmail.com>
	<AANLkTinL+QuNSCdQ0=zpyMK2J=1hSi7W3gzve2yNzobP@mail.gmail.com>
	<DD4545B3-4E0C-44EC-BCDC-302E2D184AF7@zenspider.com>
	<AANLkTikTCUxnO+mXD1KYqsx9=wYtT57cjeCaqwe_zbLR@mail.gmail.com>
	<AANLkTimXwBwyRve9ZgUPPS3A1nnwZUp3LjdcUkiKHr0X@mail.gmail.com>
	<BCDD921B-7D7D-4780-B49E-E84A2C9E95F6@zenspider.com>
	<AANLkTi=+CP_rdx95GiAF+jX+thLtMC_x1U62Gxa8TzRX@mail.gmail.com>
Message-ID: <AANLkTinq=CfMKW4fTmBsi4rz7OZhb59ScBWta1RBy6Ym@mail.gmail.com>

On Mon, Feb 7, 2011 at 1:01 PM, Chad Woolley <thewoolleyman at gmail.com> wrote:
> And you have still ignored my request to apply the Hoe patch to
> disable usage of sudo.

Thank you for applying the patch, Ryan.  When it is in a released
version of Hoe which is used in Rubygems I'll try to replace the
redundant dev dependency code with hoe's check_dev_deps...

From noreply at rubyforge.org  Tue Feb  8 10:04:27 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue,  8 Feb 2011 10:04:27 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28806 ] Re-install of a gem
	can leave prior gem files remaining
Message-ID: <20110208150427.47E791858389@rubyforge.org>

Bugs item #28806, was opened at 2010-12-28 17:26
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28806&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: David Kellum (dekellum)
Assigned to: Ryan Davis (zenspider)
Summary: Re-install of a gem can leave prior gem files remaining

Initial Comment:
The problem arises when the contents of gem change over multiple builds with the same gem version, typically when a gem is under development and installed repeatedly to a local gem home.  There are several cases where gems load or otherwise use all files in a particular directory within the gem install dir.  When a file is removed or renamed over subsequent builds, old files from the prior "gem install" will remain after the new "gem install", leading to often unexpected behavior.

One specific example would be gem packaged ActiveRecord migrations directory, where all migrations in a gem installed "db/" directory are applied.

To avoid any chance of inconsistent behavior from prior installed gem files, it would be best if the gem Installer removed all old files from the gem_dir before installing the new files.

It looks like an easy change. I will offer a patch for this issue up on github.


----------------------------------------------------------------------

>Comment By: David Kellum (dekellum)
Date: 2011-02-08 07:04

Message:
New Pull Request with test case:

https://github.com/rubygems/rubygems/pull/29

----------------------------------------------------------------------

Comment By: David Kellum (dekellum)
Date: 2010-12-28 17:35

Message:
Pull request: 

https://github.com/rubygems/rubygems/pull/18

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28806&group_id=126

From noreply at rubyforge.org  Wed Feb  9 08:57:03 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed,  9 Feb 2011 08:57:03 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28906 ] Gems built with
	(rubygems 1.5.0 / ruby 1.9.2) do not install properly with
	(1.5.0 / 1.8.7)
Message-ID: <20110209135703.6249B185837F@rubyforge.org>

Bugs item #28906, was opened at 2011-02-03 11:42
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28906&group_id=126

Category: `gem install` command
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 3
Submitted By: Bernard Lambeau (blambeau)
Assigned to: Nobody (None)
Summary: Gems built with (rubygems 1.5.0 / ruby 1.9.2) do not install properly with (1.5.0 / 1.8.7)

Initial Comment:
The build/install scenario below fails. It seems that the metadata generated by 1.9.2 is not properly loaded by 1.8.7.  I've attached foo.gemspec. 

blambeau at yemana foo  % rvm use 1.9.2 && rm -rf pkg && gem build foo.gemspec 
  Successfully built RubyGem
  Name: foo
  Version: 1.0.0
  File: foo-1.0.0.gem
blambeau at yemana foo  % rvm use 1.8.7 && gem install foo-1.0.0.gem      
ERROR:  While executing gem ... (Gem::Exception)
    ruby_code case not handled: YAML::PrivateType

I've made some investgations and here is what I've found:

* expection raise in ruby_code, which receives a YAML::PrivateType object
* called in Specification#to_ruby
* that the first entry that fails is autorequire: !!null 
* I suspect !!null to behave differently in ruby 1.8.7 and 1.9.2, probably Syck <> Psych

See also http://help.rubygems.org/discussions/problems/483-gems-built-with-rubygems-150-ruby-192-do-not-install-properly-with-150-187

----------------------------------------------------------------------

>Comment By: Luis Lavena (luislavena)
Date: 2011-02-09 10:57

Message:
This is already fixed:
https://github.com/rubygems/rubygems/commit/6a896f356ef325d0357051fa962b6e3a835c04d2

Still things need to be wrapped for 1.5.1 release.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28906&group_id=126

From luislavena at gmail.com  Wed Feb  9 09:13:59 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 9 Feb 2011 11:13:59 -0300
Subject: [Rubygems-developers] Blockers for 1.5.1?
Message-ID: <AANLkTi=yYVXuuQPj5No0ex3bcw4fp0hiF3PGpHa_KD_j@mail.gmail.com>

Hello guys,

The YAML bug with gems generated under Ruby 1.9.2 is escalating in
priority more and more.

What are the blockers for 1.5.1 release?

Please let me know.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From drbrain at segment7.net  Wed Feb  9 16:49:03 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 9 Feb 2011 13:49:03 -0800
Subject: [Rubygems-developers] Blockers for 1.5.1?
In-Reply-To: <AANLkTi=yYVXuuQPj5No0ex3bcw4fp0hiF3PGpHa_KD_j@mail.gmail.com>
References: <AANLkTi=yYVXuuQPj5No0ex3bcw4fp0hiF3PGpHa_KD_j@mail.gmail.com>
Message-ID: <9439B157-7280-48E5-8912-70DBFB7B3D47@segment7.net>

On Feb 9, 2011, at 6:13 AM, Luis Lavena wrote:
> Hello guys,
> 
> The YAML bug with gems generated under Ruby 1.9.2 is escalating in
> priority more and more.
> 
> What are the blockers for 1.5.1 release?

No blockers, looks like trunk only has one new minor feature (gem update --system accepts a version) and is good-to-go for 1.5.1.

I will release 1.5.1 later today.

From ryand-ruby at zenspider.com  Wed Feb  9 17:40:29 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Wed, 9 Feb 2011 14:40:29 -0800
Subject: [Rubygems-developers] New Commit Convention
Message-ID: <23F3065F-201D-4D2C-97BD-9048175B7748@zenspider.com>

We're going to start using a convention I've been using in perforce and on my jobs for years now. Commit messages will have lines prefixed to convey what type of change they are:

    ! major change / enhancement
    + minor change / enhancement
    - bug fix
    not worth mentioning in the release

No wrapping lines in your commit message. If you have 2 changes they go on separate lines.

Couple examples:

    + Added the thingy to the stuff.
    fixed some rdoc

or:

    ! Changed the file format for X. Not backwards compatible.
    + Added X v1 to X v2 translator.
    - Fixed 

This will help us prep releases even faster and make it easier to see at a glance what changes  require more review.

My "original" writeup (written for work) is here:

    http://www.zenspider.com/~ryan/OnePagers/02_AutomatedChangelogs.pdf


From luislavena at gmail.com  Wed Feb  9 18:00:59 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 9 Feb 2011 20:00:59 -0300
Subject: [Rubygems-developers] Blockers for 1.5.1?
In-Reply-To: <9439B157-7280-48E5-8912-70DBFB7B3D47@segment7.net>
References: <AANLkTi=yYVXuuQPj5No0ex3bcw4fp0hiF3PGpHa_KD_j@mail.gmail.com>
	<9439B157-7280-48E5-8912-70DBFB7B3D47@segment7.net>
Message-ID: <AANLkTi=q97VV_ojALJdyL5xs+BdG7FNENf0MDASJRL4R@mail.gmail.com>

On Wed, Feb 9, 2011 at 6:49 PM, Eric Hodel <drbrain at segment7.net> wrote:
>
> No blockers, looks like trunk only has one new minor feature (gem update --system accepts a version) and is good-to-go for 1.5.1.
>
> I will release 1.5.1 later today.

Thank you.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From luislavena at gmail.com  Wed Feb  9 18:09:39 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 9 Feb 2011 20:09:39 -0300
Subject: [Rubygems-developers] New Commit Convention
In-Reply-To: <23F3065F-201D-4D2C-97BD-9048175B7748@zenspider.com>
References: <23F3065F-201D-4D2C-97BD-9048175B7748@zenspider.com>
Message-ID: <AANLkTi=fhyJ6kZuq1fk9OybmiwbgRseL0mYOQSiMUjaJ@mail.gmail.com>

On Wed, Feb 9, 2011 at 7:40 PM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
> We're going to start using a convention I've been using in perforce and on my jobs for years now. Commit messages will have lines prefixed to convey what type of change they are:
>
> ? ?! major change / enhancement
> ? ?+ minor change / enhancement
> ? ?- bug fix
> ? ?not worth mentioning in the release
>
> No wrapping lines in your commit message. If you have 2 changes they go on separate lines.
>

The problem I see with this approach are changes that span across
multiple commits and touch different files.

If we use the same description for each commit, it looses the a way
for doing quick log and see when things are introduced and what.

I personally prefer updating History.txt myself and include:

== (Not Released)

* Bugfixes:
  *

Etc. you get the idea.

Either by automated tools or not, parsing before a release still
remains something manual, so why not make it more easy for
contributors to work directly into that file?

In case of pull requests, after a merge I update the History to
reflect the changes taking part of the pull request description and
given the proper attribution.

If we enforce this, needs to be documented in a contribution document
so pull requests commits can follow these rules and is less work for
us.

Just my point of view.

Cheers,
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From erik at hollensbe.org  Wed Feb  9 18:29:47 2011
From: erik at hollensbe.org (Erik Hollensbe)
Date: Wed, 9 Feb 2011 18:29:47 -0500
Subject: [Rubygems-developers] Blockers for 1.5.1?
In-Reply-To: <AANLkTi=q97VV_ojALJdyL5xs+BdG7FNENf0MDASJRL4R@mail.gmail.com>
References: <AANLkTi=yYVXuuQPj5No0ex3bcw4fp0hiF3PGpHa_KD_j@mail.gmail.com>
	<9439B157-7280-48E5-8912-70DBFB7B3D47@segment7.net>
	<AANLkTi=q97VV_ojALJdyL5xs+BdG7FNENf0MDASJRL4R@mail.gmail.com>
Message-ID: <6369FDD1-020F-4C85-ABCE-B4B5A4B1FD49@hollensbe.org>


On Feb 9, 2011, at 6:00 PM, Luis Lavena wrote:

> On Wed, Feb 9, 2011 at 6:49 PM, Eric Hodel <drbrain at segment7.net> wrote:
>> 
>> No blockers, looks like trunk only has one new minor feature (gem update --system accepts a version) and is good-to-go for 1.5.1.
>> 
>> I will release 1.5.1 later today.
> 
> Thank you.

I am getting this failure on 1.9.2. It may just be related to my setup but I know eric only rolls with 1.8 so I figured it'd be worth double-checking (this failure does not occur on 1.8).

Apologies for the wall of text but this is the output raw. :)

test_to_ruby_fancy(TestGemSpecification) [/Users/erikh/repos/gems/rubygems/test/rubygems/test_gem_specification.rb:860]:
Expected "# -*- encoding: utf-8 -*-\n\nGem::Specification.new do |s|\n  s.name = %q{a}\n  s.version = \"1\"\n  s.platform = Gem::Platform.new([\"x86\", \"darwin\", \"8\"])\n\n  s.required_rubygems_version = Gem::Requirement.new(\">= 0\") if s.respond_to? :required_rubygems_version=\n  s.authors = [\"A User\"]\n  s.date = %q{2011-02-09}\n  s.default_executable = %q{exec}\n  s.description = %q{This is a test description}\n  s.email = %q{example at example.com}\n  s.executables = [\"exec\"]\n  s.extensions = [\"ext/a/extconf.rb\"]\n  s.files = [\"lib/code.rb\", \"test/suite.rb\", \"bin/exec\", \"ext/a/extconf.rb\"]\n  s.homepage = %q{http://example.com}\n  s.licenses = [\"MIT\"]\n  s.require_paths = [\"lib\"]\n  s.requirements = [\"A working computer\"]\n  s.rubyforge_project = %q{example}\n  s.rubygems_version = %q{1.5.0}\n  s.summary = %q{this is a summary}\n  s.test_files = [\"test/suite.rb\"]\n\n  if s.respond_to? :specification_version then\n    s.specification_version = 3\n\n    if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then\n      s.add_runtime_dependency(%q<rake>, [\"> 0.4\"])\n      s.add_runtime_dependency(%q<jabber4r>, [\"> 0.0.0\"])\n      s.add_runtime_dependency(%q<pqa>, [\"> 0.4\", \"<= 0.6\"])\n    else\n      s.add_dependency(%q<rake>, [\"> 0.4\"])\n      s.add_dependency(%q<jabber4r>, [\"> 0.0.0\"])\n      s.add_dependency(%q<pqa>, [\"> 0.4\", \"<= 0.6\"])\n    end\n  else\n    s.add_dependency(%q<rake>, [\"> 0.4\"])\n    s.add_dependency(%q<jabber4r>, [\"> 0.0.0\"])\n    s.add_dependency(%q<pqa>, [\"> 0.4\", \"<= 0.6\"])\n  end\nend\n", not "# -*- encoding: utf-8 -*-\n\nGem::Specification.new do |s|\n  s.name = %q{a}\n  s.version = \"1\"\n  s.platform = Gem::Platform.new([\"x86\", \"darwin\", \"8\"])\n\n  s.required_rubygems_version = Gem::Requirement.new(\">= 0\") if s.respond_to? :required_rubygems_version=\n  s.authors = [\"A User\"]\n  s.date = %q{2011-02-09}\n  s.default_executable = %q{exec}\n  s.description = %q{This is a test description}\n  s.email = %q{example at example.com}\n  s.executables = [\"exec\"]\n  s.extensions = [\"ext/a/extconf.rb\"]\n  s.files = [\"lib/code.rb\", \"test/suite.rb\", \"bin/exec\", \"ext/a/extconf.rb\"]\n  s.has_rdoc = %q{true}\n  s.homepage = %q{http://example.com}\n  s.licenses = [\"MIT\"]\n  s.require_paths = [\"lib\"]\n  s.requirements = [\"A working computer\"]\n  s.rubyforge_project = %q{example}\n  s.rubygems_version = %q{1.5.0}\n  s.summary = %q{this is a summary}\n  s.test_files = [\"test/suite.rb\"]\n\n  if s.respond_to? :specification_version then\n    s.specification_version = 3\n\n    if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then\n      s.add_runtime_dependency(%q<rake>, [\"> 0.4\"])\n      s.add_runtime_dependency(%q<jabber4r>, [\"> 0.0.0\"])\n      s.add_runtime_dependency(%q<pqa>, [\"> 0.4\", \"<= 0.6\"])\n    else\n      s.add_dependency(%q<rake>, [\"> 0.4\"])\n      s.add_dependency(%q<jabber4r>, [\"> 0.0.0\"])\n      s.add_dependency(%q<pqa>, [\"> 0.4\", \"<= 0.6\"])\n    end\n  else\n    s.add_dependency(%q<rake>, [\"> 0.4\"])\n    s.add_dependency(%q<jabber4r>, [\"> 0.0.0\"])\n    s.add_dependency(%q<pqa>, [\"> 0.4\", \"<= 0.6\"])\n  end\nend\n".

-Erik

From drbrain at segment7.net  Wed Feb  9 18:44:17 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 9 Feb 2011 15:44:17 -0800
Subject: [Rubygems-developers] New Commit Convention
In-Reply-To: <AANLkTi=fhyJ6kZuq1fk9OybmiwbgRseL0mYOQSiMUjaJ@mail.gmail.com>
References: <23F3065F-201D-4D2C-97BD-9048175B7748@zenspider.com>
	<AANLkTi=fhyJ6kZuq1fk9OybmiwbgRseL0mYOQSiMUjaJ@mail.gmail.com>
Message-ID: <6C043ABC-2353-47D4-86A5-D592070B097A@segment7.net>

On Feb 9, 2011, at 3:09 PM, Luis Lavena wrote:
> On Wed, Feb 9, 2011 at 7:40 PM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
>> We're going to start using a convention I've been using in perforce and on my jobs for years now. Commit messages will have lines prefixed to convey what type of change they are:
>> 
>>    ! major change / enhancement
>>    + minor change / enhancement
>>    - bug fix
>>    not worth mentioning in the release
>> 
>> No wrapping lines in your commit message. If you have 2 changes they go on separate lines.
>> 
> 
> The problem I see with this approach are changes that span across
> multiple commits and touch different files.
> 
> If we use the same description for each commit, it looses the a way
> for doing quick log and see when things are introduced and what.


I do the same, so I use a ! + - for one commit and omit the signifier for the rest.

> I personally prefer updating History.txt myself and include:
> 
> == (Not Released)
> 
> * Bugfixes:
>  *
> 
> Etc. you get the idea.
> 
> Either by automated tools or not, parsing before a release still
> remains something manual, so why not make it more easy for
> contributors to work directly into that file?
> 
> In case of pull requests, after a merge I update the History to
> reflect the changes taking part of the pull request description and
> given the proper attribution.

I think we can adjust the git history tool to separate direct commits from those applied through pull requests in order to figure out proper messages for commits from pull requests.

> If we enforce this, needs to be documented in a contribution document
> so pull requests commits can follow these rules and is less work for
> us.

Sure.

From thewoolleyman at gmail.com  Wed Feb  9 18:56:13 2011
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Wed, 9 Feb 2011 16:56:13 -0700
Subject: [Rubygems-developers] Blockers for 1.5.1?
In-Reply-To: <6369FDD1-020F-4C85-ABCE-B4B5A4B1FD49@hollensbe.org>
References: <AANLkTi=yYVXuuQPj5No0ex3bcw4fp0hiF3PGpHa_KD_j@mail.gmail.com>
	<9439B157-7280-48E5-8912-70DBFB7B3D47@segment7.net>
	<AANLkTi=q97VV_ojALJdyL5xs+BdG7FNENf0MDASJRL4R@mail.gmail.com>
	<6369FDD1-020F-4C85-ABCE-B4B5A4B1FD49@hollensbe.org>
Message-ID: <AANLkTikYdAfmCDO7iUzOeB093oDzbuwDPMUKY-Empg=m@mail.gmail.com>

On Wed, Feb 9, 2011 at 4:29 PM, Erik Hollensbe <erik at hollensbe.org> wrote:
> I am getting this failure on 1.9.2. It may just be related to my setup but I know eric only rolls with 1.8 so I figured it'd be worth double-checking (this failure does not occur on 1.8).

What patchlevel?  It is green on linux/1.9.2-p136

http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p136

> Apologies for the wall of text but this is the output raw. :)
>
> test_to_ruby_fancy(TestGemSpecification) [/Users/erikh/repos/gems/rubygems/test/rubygems/test_gem_specification.rb:860]:
> Expected "# -*- encoding: utf-8 -*-\n\nGem::Specification.new do |s|\n ?s.name = %q{a}\n ?s.version = \"1\"\n ?s.platform = Gem::Platform.new([\"x86\", \"darwin\", \"8\"])\n\n ?s.required_rubygems_version = Gem::Requirement.new(\">= 0\") if s.respond_to? :required_rubygems_version=\n ?s.authors = [\"A User\"]\n ?s.date = %q{2011-02-09}\n ?s.default_executable = %q{exec}\n ?s.description = %q{This is a test description}\n ?s.email = %q{example at example.com}\n ?s.executables = [\"exec\"]\n ?s.extensions = [\"ext/a/extconf.rb\"]\n ?s.files = [\"lib/code.rb\", \"test/suite.rb\", \"bin/exec\", \"ext/a/extconf.rb\"]\n ?s.homepage = %q{http://example.com}\n ?s.licenses = [\"MIT\"]\n ?s.require_paths = [\"lib\"]\n ?s.requirements = [\"A working computer\"]\n ?s.rubyforge_project = %q{example}\n ?s.rubygems_version = %q{1.5.0}\n ?s.summary = %q{this is a summary}\n ?s.test_files = [\"test/suite.rb\"]\n\n ?if s.respond_to? :specification_version then\n ? ?s.specification_version = 3\n\n
> ? ? if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then\n ? ? ?s.add_runtime_dependency(%q<rake>, [\"> 0.4\"])\n ? ? ?s.add_runtime_dependency(%q<jabber4r>, [\"> 0.0.0\"])\n ? ? ?s.add_runtime_dependency(%q<pqa>, [\"> 0.4\", \"<= 0.6\"])\n ? ?else\n ? ? ?s.add_dependency(%q<rake>, [\"> 0.4\"])\n ? ? ?s.add_dependency(%q<jabber4r>, [\"> 0.0.0\"])\n ? ? ?s.add_dependency(%q<pqa>, [\"> 0.4\", \"<= 0.6\"])\n ? ?end\n ?else\n ? ?s.add_dependency(%q<rake>, [\"> 0.4\"])\n ? ?s.add_dependency(%q<jabber4r>, [\"> 0.0.0\"])\n ? ?s.add_dependency(%q<pqa>, [\"> 0.4\", \"<= 0.6\"])\n ?end\nend\n", not "# -*- encoding: utf-8 -*-\n\nGem::Specification.new do |s|\n ?s.name = %q{a}\n ?s.version = \"1\"\n ?s.platform = Gem::Platform.new([\"x86\", \"darwin\", \"8\"])\n\n ?s.required_rubygems_version = Gem::Requirement.new(\">= 0\") if s.respond_to? :required_rubygems_version=\n ?s.authors = [\"A User\"]\n ?s.date = %q{2011-02-09}\n ?s.default_executable = %q{exec}\n ?s.descripti
> ?on = %q{This is a test description}\n ?s.email = %q{example at example.com}\n ?s.executables = [\"exec\"]\n ?s.extensions = [\"ext/a/extconf.rb\"]\n ?s.files = [\"lib/code.rb\", \"test/suite.rb\", \"bin/exec\", \"ext/a/extconf.rb\"]\n ?s.has_rdoc = %q{true}\n ?s.homepage = %q{http://example.com}\n ?s.licenses = [\"MIT\"]\n ?s.require_paths = [\"lib\"]\n ?s.requirements = [\"A working computer\"]\n ?s.rubyforge_project = %q{example}\n ?s.rubygems_version = %q{1.5.0}\n ?s.summary = %q{this is a summary}\n ?s.test_files = [\"test/suite.rb\"]\n\n ?if s.respond_to? :specification_version then\n ? ?s.specification_version = 3\n\n ? ?if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then\n ? ? ?s.add_runtime_dependency(%q<rake>, [\"> 0.4\"])\n ? ? ?s.add_runtime_dependency(%q<jabber4r>, [\"> 0.0.0\"])\n ? ? ?s.add_runtime_dependency(%q<pqa>, [\"> 0.4\", \"<= 0.6\"])\n ? ?else\n ? ? ?s.add_dependency(%q<rake>, [\"> 0.4\"])\n ? ? ?s.add_dependency(%q<jabber4r>, [\"> 0.0.0\"
> ?])\n ? ? ?s.add_dependency(%q<pqa>, [\"> 0.4\", \"<= 0.6\"])\n ? ?end\n ?else\n ? ?s.add_dependency(%q<rake>, [\"> 0.4\"])\n ? ?s.add_dependency(%q<jabber4r>, [\"> 0.0.0\"])\n ? ?s.add_dependency(%q<pqa>, [\"> 0.4\", \"<= 0.6\"])\n ?end\nend\n".
>
> -Erik
> _______________________________________________
> Rubygems-developers mailing list
> http://rubyforge.org/projects/rubygems
> Rubygems-developers at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubygems-developers
>

From erik at hollensbe.org  Wed Feb  9 19:08:32 2011
From: erik at hollensbe.org (Erik Hollensbe)
Date: Wed, 9 Feb 2011 19:08:32 -0500
Subject: [Rubygems-developers] Blockers for 1.5.1?
In-Reply-To: <AANLkTikYdAfmCDO7iUzOeB093oDzbuwDPMUKY-Empg=m@mail.gmail.com>
References: <AANLkTi=yYVXuuQPj5No0ex3bcw4fp0hiF3PGpHa_KD_j@mail.gmail.com>
	<9439B157-7280-48E5-8912-70DBFB7B3D47@segment7.net>
	<AANLkTi=q97VV_ojALJdyL5xs+BdG7FNENf0MDASJRL4R@mail.gmail.com>
	<6369FDD1-020F-4C85-ABCE-B4B5A4B1FD49@hollensbe.org>
	<AANLkTikYdAfmCDO7iUzOeB093oDzbuwDPMUKY-Empg=m@mail.gmail.com>
Message-ID: <5160F56E-EE75-463A-8CC0-11C273429810@hollensbe.org>


On Feb 9, 2011, at 6:56 PM, Chad Woolley wrote:

> On Wed, Feb 9, 2011 at 4:29 PM, Erik Hollensbe <erik at hollensbe.org> wrote:
>> I am getting this failure on 1.9.2. It may just be related to my setup but I know eric only rolls with 1.8 so I figured it'd be worth double-checking (this failure does not occur on 1.8).
> 
> What patchlevel?  It is green on linux/1.9.2-p136
> 
> http://cibuilder.pivotallabs.com:3333/builds/RubyGems-1_9_2-p136

YARD related; sorry for the smoke. :) Eric and I sorted it on IRC.

-Erik

From drbrain at segment7.net  Wed Feb  9 19:59:16 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 9 Feb 2011 16:59:16 -0800
Subject: [Rubygems-developers] [ANN] rubygems-update 1.5.1 Released
Message-ID: <A61C0722-7A4C-4B50-846C-57A5954DE7AB@segment7.net>

rubygems-update version 1.5.1 has been released!

* <http://rubygems.org>
* <http://docs.rubygems.org>
* <http://help.rubygems.org>
* <http://github.com/rubygems>
* <http://rubyforge.org/projects/rubygems>

RubyGems is a package management framework for Ruby.

This gem is an update for the RubyGems software. You must have an
installation of RubyGems before this update can be applied.

See Gem for information on RubyGems (or `ri Gem`)

To upgrade to the latest RubyGems, run:

  $ gem update --system  # you might need to be an administrator or root

See UPGRADING.rdoc for more details and alternative instructions.

-----

If you don't have any RubyGems install, there is still the pre-gem approach to
getting software, doing it manually:

* Download from: https://rubygems.org/pages/download
* Unpack into a directory and cd there
* Install with: ruby setup.rb  # you may need admin/root privilege

For more details and other options, see:

  ruby setup.rb --help

Changes:

### 1.5.1 / 2011-02-09

Minor Enhancement:

* Added ability to do gem update --system X.Y.Z.

Bug Fixes:

* Scrub !!null YAML from 1.9.2 (install and build).
* Added missing requires for user_interaction.
* Wrote option processing tests for gem update.
* Updated upgrading doco for new gem update --system option.
* Fixed SilentUI for cygwin; try /dev/null first then fall back to NUL.
* RubyGems now enforces ruby 1.8.7 or newer.


From ryand-ruby at zenspider.com  Wed Feb  9 20:00:39 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Wed, 9 Feb 2011 17:00:39 -0800
Subject: [Rubygems-developers] Blockers for 1.5.1?
In-Reply-To: <5160F56E-EE75-463A-8CC0-11C273429810@hollensbe.org>
References: <AANLkTi=yYVXuuQPj5No0ex3bcw4fp0hiF3PGpHa_KD_j@mail.gmail.com>
	<9439B157-7280-48E5-8912-70DBFB7B3D47@segment7.net>
	<AANLkTi=q97VV_ojALJdyL5xs+BdG7FNENf0MDASJRL4R@mail.gmail.com>
	<6369FDD1-020F-4C85-ABCE-B4B5A4B1FD49@hollensbe.org>
	<AANLkTikYdAfmCDO7iUzOeB093oDzbuwDPMUKY-Empg=m@mail.gmail.com>
	<5160F56E-EE75-463A-8CC0-11C273429810@hollensbe.org>
Message-ID: <E6043D8F-754D-403E-B775-7A08228ACD03@zenspider.com>


On Feb 9, 2011, at 16:08 , Erik Hollensbe wrote:

> YARD related; sorry for the smoke. :) Eric and I sorted it on IRC.

hah... you know what's coming next! :P


From drbrain at segment7.net  Wed Feb  9 21:24:19 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Wed, 9 Feb 2011 18:24:19 -0800
Subject: [Rubygems-developers] [ANN] rubygems-update 1.5.1 Released
In-Reply-To: <A61C0722-7A4C-4B50-846C-57A5954DE7AB@segment7.net>
References: <A61C0722-7A4C-4B50-846C-57A5954DE7AB@segment7.net>
Message-ID: <EE73FD47-D93E-429D-8FF8-2AF6B57D7732@segment7.net>


On Feb 9, 2011, at 4:59 PM, Eric Hodel wrote:

> rubygems-update version 1.5.1 has been released!

But then I pulled 1.5.1

It turns out that 1.5.0 and 1.5.1 have a bug wherein we broke `gem update --system`.  We have written some tests (the first test for the feature since forever) and will be releasing 1.5.2 tomorrow.


From noreply at rubyforge.org  Thu Feb 10 01:05:30 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 10 Feb 2011 01:05:30 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Patches-28919 ] [gem cleanup]
	automatically skip gems having dependants
Message-ID: <20110210060530.B10E9185836B@rubyforge.org>

Patches item #28919, was opened at 2011-02-10 06:05
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=577&aid=28919&group_id=126

Category: `gem` commands (other)
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: ryenus . (ryenus)
Assigned to: Nobody (None)
Summary: [gem cleanup] automatically skip gems having dependants

Initial Comment:
When running "gem cleanup", it feels tedious to keep entering 'N' to prevent some old gems from being removed, because they're still being depended on by other gems.

An option "-n" could be added to automatically skip those gems having dependants upon gem cleanup.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=577&aid=28919&group_id=126

From noreply at rubyforge.org  Thu Feb 10 02:37:12 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 10 Feb 2011 02:37:12 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28907 ] [RG 1.5.0/Ruby 1.9.x]
	source gem build error due to syck?
Message-ID: <20110210073712.965721678325@rubyforge.org>

Bugs item #28907, was opened at 2011-02-04 03:59
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

Category: `gem` commands (other)
Group: v1.5.x
Status: Closed
Resolution: Rejected
Priority: 3
Submitted By: Jon Forums (jonforums)
Assigned to: Eric Hodel (drbrain)
Summary: [RG 1.5.0/Ruby 1.9.x] source gem build error due to syck?

Initial Comment:
When building a source gem from http://github.com/oopsforge/oops-null using 'rake gem' I get the following error on Win7 with:

  * ruby 1.9.2p174 (2011-01-28 revision 30696) [i386-mingw32]
  * ruby 1.9.3dev (2011-02-04 trunk 30776) [i386-mingw32]

but no errors using "ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32]".  

Manually building via 'gem build oops-null.gemspec' work fine on all the Ruby versions including JRuby 1.6.0.RC1.  All versions have been upgraded to RG 1.5.0 via "gem update --system".

FWIW, the failure does not occur on "ruby 1.9.2 (2010-12-25 patchlevel 136) [i386-mingw32]" using RG 1.3.7

My "fix" was to add the following lines to the project Rakefile after the 3 require's:

require 'yaml'
YAML::ENGINE.yamler='psych' if defined?(YAML::ENGINE)

I will try to replicate on my Arch system later this afternoon.

Reproducible?

Jon


== ERROR ==

C:\projects\oops-null-git>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.2 (2011-01-28 patchlevel 174) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/Users/Jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", "http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org


C:\projects\oops-null-git>rake gem
(in C:/projects/oops-null-git)
mkdir -p pkg
mkdir -p pkg
mkdir -p pkg/oops-null-0.3.0/bin
rm -f pkg/oops-null-0.3.0/bin/nulloops
ln bin/nulloops pkg/oops-null-0.3.0/bin/nulloops
rm -f pkg/oops-null-0.3.0/Rakefile
ln Rakefile pkg/oops-null-0.3.0/Rakefile
rm -f pkg/oops-null-0.3.0/oops-null.gemspec
ln oops-null.gemspec pkg/oops-null-0.3.0/oops-null.gemspec
mkdir -p pkg/oops-null-0.3.0/ext/oops_null
rm -f pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
ln ext/oops_null/extconf.rb pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
ln ext/oops_null/oops_null.c pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
ln ext/oops_null/oops_null.h pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
mkdir -p pkg/oops-null-0.3.0/lib
rm -f pkg/oops-null-0.3.0/lib/oops-null.rb
ln lib/oops-null.rb pkg/oops-null-0.3.0/lib/oops-null.rb
cd pkg/oops-null-0.3.0
rake aborted!
undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
C:/ruby192/lib/ruby/1.9.1/psych.rb:166:in `dump'
C:/ruby192/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block (2 levels) in to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `map'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `block in to_yaml'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `call'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `emit'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:725:in `to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1157:in `when_writing'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1092:in `chdir'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `call'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `block in execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:595:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:605:in `block in invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:594:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:581:in `invoke'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2041:in `invoke_task'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block (2 levels) in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2013:in `top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1992:in `run'
C:/ruby192/bin/rake:31:in `<main>'

----------------------------------------------------------------------

Comment By: Leonard Chin (lchin)
Date: 2011-02-10 16:37

Message:
The same error occurs with hoe

Using RubyGems at commit 182bcaf7bd4f77493794 with Ruby 1.9.2-p136
https://github.com/rubygems/rubygems/tree/182bcaf7bd4f77493794d216ac37aa9935655943

rake package --trace
(in /Users/lchin/Downloads/buggy)
** Invoke package (first_time)
** Invoke pkg/buggy-1.0.0.tgz (first_time, not_needed)
** Invoke pkg/buggy-1.0.0 (first_time, not_needed)
** Invoke .autotest (first_time, not_needed)
** Invoke History.txt (first_time, not_needed)
** Invoke Manifest.txt (first_time, not_needed)
** Invoke README.txt (first_time, not_needed)
** Invoke Rakefile (first_time, not_needed)
** Invoke bin/buggy (first_time, not_needed)
** Invoke lib/buggy.rb (first_time, not_needed)
** Invoke test/test_buggy.rb (first_time, not_needed)
** Invoke .autotest (not_needed)
** Invoke History.txt (not_needed)
** Invoke Manifest.txt (not_needed)
** Invoke README.txt (not_needed)
** Invoke Rakefile (not_needed)
** Invoke bin/buggy (not_needed)
** Invoke lib/buggy.rb (not_needed)
** Invoke test/test_buggy.rb (not_needed)
** Invoke gem (first_time)
** Invoke pkg/buggy-1.0.0.gem (first_time)
** Invoke pkg (first_time, not_needed)
** Invoke pkg/buggy-1.0.0 (not_needed)
** Invoke .autotest (not_needed)
** Invoke History.txt (not_needed)
** Invoke Manifest.txt (not_needed)
** Invoke README.txt (not_needed)
** Invoke Rakefile (not_needed)
** Invoke bin/buggy (not_needed)
** Invoke lib/buggy.rb (not_needed)
** Invoke test/test_buggy.rb (not_needed)
** Execute pkg/buggy-1.0.0.gem
cd pkg/buggy-1.0.0
WARNING:  description and summary are identical
rake aborted!
undefined method `write' for #<Syck::Emitter:0x00000100919d48>
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych.rb:166:in `dump'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:728:in `block (2 levels) in to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `map'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block in to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/syck.rb:401:in `call'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/syck.rb:401:in `emit'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:1159:in `when_writing'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:1094:in `chdir'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:636:in `call'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:636:in `block in execute'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:631:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:597:in `block in invoke_with_call_chain'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:607:in `block in invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:596:in `block in invoke_with_call_chain'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:607:in `block in invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:596:in `block in invoke_with_call_chain'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2029:in `block (2 levels) in top_level'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2029:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2029:in `block in top_level'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2001:in `block in run'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/bin/rake:31:in `<top (required)>'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/bin/rake:19:in `load'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/bin/rake:19:in `<main>'

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-06 07:00

Message:
All OK now with the updated rake-compiler.

So I'm clear, this is the main commit to pay attention to?

https://github.com/rubygems/rubygems/commit/67f9f760c782142d9bfd8099750274ba498d6682

Given the simple tweak to rake-compiler, is your
recommendation that other gems requiring yaml also prefer
psych when running on 1.9.2+ and RG 1.5.0+

FWIW, I personally like the idea of preferring psych, but
would like to have first seen it mentioned in one of the
following rather than in a bt:

http://blog.segment7.net/2011/01/31/rubygems-1-5

https://github.com/rubygems/rubygems/blob/master/UPGRADING.rdoc 

Jon

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-05 08:37

Message:
Yes, you are loading syck (require 'yaml') before psych (require 'psych'):

https://github.com/luislavena/rake-compiler/blob/master/lib/rake/baseextensiontask.rb

This is not supported.

A patch will be sent to rake-compiler.

You can work around this by requiring psych before rake-compiler.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-05 06:01

Message:
That's not the issue, sorry I wasn't clear.  I'm not mixing 
syck or psyck in the same ruby in my code.

My original Rakefile https://github.com/oopsforge/oops-
null/blob/master/Rakefile that worked pre-1.5.0 didn't 
explicitly require 'yaml' or the YAML::ENGINE.yamler= 
nonsense.

I added these lines to get the gem to build when I saw the 
error message

undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in 
`end_document'
...

..as I guessed that explicitly setting the YAML engine to 
psych would prevent syck from being visited/wrapped by 
psych.

I think something's changed in RG 1.5.0 and/or ruby_1_9_2 or 
trunk that's causing the problem. I wanted to dig into how 
psych was visiting/wrapping syck but ran out of time. I also 
did a quick look through rake-compiler and don't think it's 
to blame.

Given that my original Rakefile fails on Win7 MRI 1.9.2-
p174, 1.9.2-p136, 1.9.3dev and Arch 1.9.3dev when using RG 
1.5.0 I still think the problem is in RG.

Hopefully I explained it more clearly this time.

Would you take one more look at that long back trace and see 
if you change your mind on the issue?

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-05 05:33

Message:
Do not mix syck (require 'yaml') and psych (require 'psych') in the same ruby.

RubyGems uses psych on ruby 1.9.2 and newer as syck is deprecated and will be removed at a future date.  Please update your Rakefile to match.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 23:53

Message:
same failure on "ruby 1.9.2p136 (2010-12-25) [i386-mingw32]" 
upgraded from RG 1.3.7 to RG 1.5.0

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 04:13

Message:
similar failure and working "fix" on Arch using:

ruby 1.9.3dev (2011-02-04 trunk 30776) [i686-linux]

RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.3 (2011-02-04 patchlevel -1) [i686-
linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.9.1
     - /home/jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", 
"http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

From drbrain at segment7.net  Thu Feb 10 18:58:47 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Thu, 10 Feb 2011 15:58:47 -0800
Subject: [Rubygems-developers] [ANN] rubygems-update 1.5.2 Released
Message-ID: <6F83C937-6021-4869-B059-E890011D0DE9@segment7.net>

rubygems-update version 1.5.2 has been released!

* <http://rubygems.org>
* <http://docs.rubygems.org>
* <http://help.rubygems.org>
* <http://github.com/rubygems>
* <http://rubyforge.org/projects/rubygems>

RubyGems is a package management framework for Ruby.

This gem is an update for the RubyGems software. You must have an
installation of RubyGems before this update can be applied.

See Gem for information on RubyGems (or `ri Gem`)

NOTE:  RubyGems 1.5.0 and 1.5.1 have a broken `gem update --system`.

To upgrade you'll need to use the manual upgrade recipe.  Using sudo/su as
appropriate:

  $ gem install rubygems-update
  $ update_rubygems

If you are upgrading from versions of RubyGems earlier than 1.5.0 run:

  $ gem update --system  # you might need to be an administrator or root

See UPGRADING.rdoc for more details and alternative instructions.

-----

If you don't have any RubyGems install, there is still the pre-gem approach to
getting software, doing it manually:

* Download from: https://rubygems.org/pages/download
* Unpack into a directory and cd there
* Install with: ruby setup.rb  # you may need admin/root privilege

For more details and other options, see:

  ruby setup.rb --help

Changes:

### 1.5.2 / 2011-02-10

Bug Fixes:

* Fixed `gem update --system`.  RubyGems can now update itself again.


From noreply at rubyforge.org  Fri Feb 11 07:36:50 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 11 Feb 2011 07:36:50 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28922 ] Get `undefined
	class/module YAML::PrivateType` when installing a gem in 1.9.2
Message-ID: <20110211123650.7A16B1858346@rubyforge.org>

Bugs item #28922, was opened at 2011-02-12 01:36
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: John Mair (banister)
Assigned to: Nobody (None)
Summary: Get `undefined class/module YAML::PrivateType` when installing a gem in 1.9.2 

Initial Comment:
Here is the output when i try to `gem install pry` in ruby 1.9.2 in windows 7:

c:\>gem install pry
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType


And the output from `gem env`:

c:\>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.2
  - RUBY VERSION: 1.9.2 (2010-08-18 patchlevel 0) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/emacs/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

From noreply at rubyforge.org  Fri Feb 11 08:29:12 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 11 Feb 2011 08:29:12 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28922 ] Get `undefined
	class/module YAML::PrivateType` when installing a gem in 1.9.2
Message-ID: <20110211132914.18DAF1858344@rubyforge.org>

Bugs item #28922, was opened at 2011-02-11 04:36
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: John Mair (banister)
Assigned to: Nobody (None)
Summary: Get `undefined class/module YAML::PrivateType` when installing a gem in 1.9.2 

Initial Comment:
Here is the output when i try to `gem install pry` in ruby 1.9.2 in windows 7:

c:\>gem install pry
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType


And the output from `gem env`:

c:\>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.2
  - RUBY VERSION: 1.9.2 (2010-08-18 patchlevel 0) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/emacs/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

Comment By: Erik Hollensbe (erikh)
Date: 2011-02-11 05:29

Message:
Took a peek at this; it's not happening on my OS X 1.9.2 install with 1.5.2, and I do not have Psych installed. It is reproducible for me on 1.9.2 mingw.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

From noreply at rubyforge.org  Fri Feb 11 09:54:13 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 11 Feb 2011 09:54:13 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28922 ] Get `undefined
	class/module YAML::PrivateType` when installing a gem in 1.9.2
Message-ID: <20110211145413.654E118582E2@rubyforge.org>

Bugs item #28922, was opened at 2011-02-11 12:36
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: John Mair (banister)
Assigned to: Nobody (None)
Summary: Get `undefined class/module YAML::PrivateType` when installing a gem in 1.9.2 

Initial Comment:
Here is the output when i try to `gem install pry` in ruby 1.9.2 in windows 7:

c:\>gem install pry
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType


And the output from `gem env`:

c:\>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.2
  - RUBY VERSION: 1.9.2 (2010-08-18 patchlevel 0) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/emacs/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-11 14:54

Message:
Took a quick look through pry and didn't see yaml required, but do any of pry's deps use yaml (syck) and conflict with rg's psych preference?

----------------------------------------------------------------------

Comment By: Erik Hollensbe (erikh)
Date: 2011-02-11 13:29

Message:
Took a peek at this; it's not happening on my OS X 1.9.2 install with 1.5.2, and I do not have Psych installed. It is reproducible for me on 1.9.2 mingw.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

From noreply at rubyforge.org  Fri Feb 11 09:59:33 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 11 Feb 2011 09:59:33 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28922 ] Get `undefined
	class/module YAML::PrivateType` when installing a gem in 1.9.2
Message-ID: <20110211145933.6B78218582E2@rubyforge.org>

Bugs item #28922, was opened at 2011-02-11 04:36
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: John Mair (banister)
Assigned to: Nobody (None)
Summary: Get `undefined class/module YAML::PrivateType` when installing a gem in 1.9.2 

Initial Comment:
Here is the output when i try to `gem install pry` in ruby 1.9.2 in windows 7:

c:\>gem install pry
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType


And the output from `gem env`:

c:\>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.2
  - RUBY VERSION: 1.9.2 (2010-08-18 patchlevel 0) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/emacs/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

Comment By: Erik Hollensbe (erikh)
Date: 2011-02-11 06:59

Message:
This happens at install time, not runtime.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-11 06:54

Message:
Took a quick look through pry and didn't see yaml required, but do any of pry's deps use yaml (syck) and conflict with rg's psych preference?

----------------------------------------------------------------------

Comment By: Erik Hollensbe (erikh)
Date: 2011-02-11 05:29

Message:
Took a peek at this; it's not happening on my OS X 1.9.2 install with 1.5.2, and I do not have Psych installed. It is reproducible for me on 1.9.2 mingw.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

From noreply at rubyforge.org  Fri Feb 11 10:26:08 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 11 Feb 2011 10:26:08 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28922 ] Get `undefined
	class/module YAML::PrivateType` when installing a gem in 1.9.2
Message-ID: <20110211152608.65FBF1858300@rubyforge.org>

Bugs item #28922, was opened at 2011-02-11 09:36
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
>Priority: 5
Submitted By: John Mair (banister)
>Assigned to: Nick Quaranto (qrush)
Summary: Get `undefined class/module YAML::PrivateType` when installing a gem in 1.9.2 

Initial Comment:
Here is the output when i try to `gem install pry` in ruby 1.9.2 in windows 7:

c:\>gem install pry
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType


And the output from `gem env`:

c:\>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.2
  - RUBY VERSION: 1.9.2 (2010-08-18 patchlevel 0) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/emacs/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

>Comment By: Luis Lavena (luislavena)
Date: 2011-02-11 12:26

Message:
Correct, this is install time issue and is generated by this:

  def self._load(str)
    array = Marshal.load str

https://gist.github.com/822477

If the marshaled specs were already broken (due !!null issues from 1.5.0) then it will fail.

Seems this is the generated Marshal.

This seems something for rubygems.org hosting as this is coming from quick specs returned by rubygems.org

The gem itself do not contain the !!null part.


----------------------------------------------------------------------

Comment By: Erik Hollensbe (erikh)
Date: 2011-02-11 11:59

Message:
This happens at install time, not runtime.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-11 11:54

Message:
Took a quick look through pry and didn't see yaml required, but do any of pry's deps use yaml (syck) and conflict with rg's psych preference?

----------------------------------------------------------------------

Comment By: Erik Hollensbe (erikh)
Date: 2011-02-11 10:29

Message:
Took a peek at this; it's not happening on my OS X 1.9.2 install with 1.5.2, and I do not have Psych installed. It is reproducible for me on 1.9.2 mingw.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

From noreply at rubyforge.org  Fri Feb 11 13:53:51 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 11 Feb 2011 13:53:51 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28922 ] Get `undefined
	class/module YAML::PrivateType` when installing a gem in 1.9.2
Message-ID: <20110211185351.D90721858317@rubyforge.org>

Bugs item #28922, was opened at 2011-02-11 04:36
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

Category: `gem install` command
Group: None
Status: Open
>Resolution: Accepted
Priority: 5
Submitted By: John Mair (banister)
Assigned to: Nick Quaranto (qrush)
Summary: Get `undefined class/module YAML::PrivateType` when installing a gem in 1.9.2 

Initial Comment:
Here is the output when i try to `gem install pry` in ruby 1.9.2 in windows 7:

c:\>gem install pry
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType


And the output from `gem env`:

c:\>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.2
  - RUBY VERSION: 1.9.2 (2010-08-18 patchlevel 0) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/emacs/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-11 10:53

Message:
I think the best solution is to have this gem be re-released.

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2011-02-11 07:26

Message:
Correct, this is install time issue and is generated by this:

  def self._load(str)
    array = Marshal.load str

https://gist.github.com/822477

If the marshaled specs were already broken (due !!null issues from 1.5.0) then it will fail.

Seems this is the generated Marshal.

This seems something for rubygems.org hosting as this is coming from quick specs returned by rubygems.org

The gem itself do not contain the !!null part.


----------------------------------------------------------------------

Comment By: Erik Hollensbe (erikh)
Date: 2011-02-11 06:59

Message:
This happens at install time, not runtime.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-11 06:54

Message:
Took a quick look through pry and didn't see yaml required, but do any of pry's deps use yaml (syck) and conflict with rg's psych preference?

----------------------------------------------------------------------

Comment By: Erik Hollensbe (erikh)
Date: 2011-02-11 05:29

Message:
Took a peek at this; it's not happening on my OS X 1.9.2 install with 1.5.2, and I do not have Psych installed. It is reproducible for me on 1.9.2 mingw.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

From noreply at rubyforge.org  Fri Feb 11 19:04:25 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 11 Feb 2011 19:04:25 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28922 ] Get `undefined
	class/module YAML::PrivateType` when installing a gem in 1.9.2
Message-ID: <20110212000425.4083E1858346@rubyforge.org>

Bugs item #28922, was opened at 2011-02-11 04:36
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

Category: `gem install` command
Group: None
>Status: Closed
Resolution: Accepted
Priority: 5
Submitted By: John Mair (banister)
Assigned to: Nick Quaranto (qrush)
Summary: Get `undefined class/module YAML::PrivateType` when installing a gem in 1.9.2 

Initial Comment:
Here is the output when i try to `gem install pry` in ruby 1.9.2 in windows 7:

c:\>gem install pry
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType


And the output from `gem env`:

c:\>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.2
  - RUBY VERSION: 1.9.2 (2010-08-18 patchlevel 0) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/emacs/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-11 16:04

Message:
I contacted the author and 0.4.8 has been released.

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-11 10:53

Message:
I think the best solution is to have this gem be re-released.

----------------------------------------------------------------------

Comment By: Luis Lavena (luislavena)
Date: 2011-02-11 07:26

Message:
Correct, this is install time issue and is generated by this:

  def self._load(str)
    array = Marshal.load str

https://gist.github.com/822477

If the marshaled specs were already broken (due !!null issues from 1.5.0) then it will fail.

Seems this is the generated Marshal.

This seems something for rubygems.org hosting as this is coming from quick specs returned by rubygems.org

The gem itself do not contain the !!null part.


----------------------------------------------------------------------

Comment By: Erik Hollensbe (erikh)
Date: 2011-02-11 06:59

Message:
This happens at install time, not runtime.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-11 06:54

Message:
Took a quick look through pry and didn't see yaml required, but do any of pry's deps use yaml (syck) and conflict with rg's psych preference?

----------------------------------------------------------------------

Comment By: Erik Hollensbe (erikh)
Date: 2011-02-11 05:29

Message:
Took a peek at this; it's not happening on my OS X 1.9.2 install with 1.5.2, and I do not have Psych installed. It is reproducible for me on 1.9.2 mingw.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28922&group_id=126

From noreply at rubyforge.org  Fri Feb 11 19:46:16 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 11 Feb 2011 19:46:16 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28924 ] gem update_rubygems
	Fails on JRuby 1.5
Message-ID: <20110212004616.82A9F1858346@rubyforge.org>

Bugs item #28924, was opened at 2011-02-12 11:46
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

Category: RubyGems installer (setup.rb)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: William Mason (william)
Assigned to: Nobody (None)
Summary: gem update_rubygems Fails on JRuby 1.5

Initial Comment:
Hi there,

I get a 'NoMethodError' when I try to execute update_rubygems from the command line after loading rubygems-update-1.5.2.gem (downloaded from RubyForge).

Incidentally the rubygems-update-1.5.2.gem that is on GemCutter (rubygem.org) is corrupt.  It won't even open as a valid zip archive.  The zip file was OK.

I successfully ran the complete rubygems-update process with ruby 1.8.7 including the: update_rubygems, script.  Worked fine.

Using jRuby 1.5, the:

   gem install rubygems-update-1.5.2.gem

Worked great (apparently).  However the 

    update_rubygems

Script falls over with a: 'NoMethodError' for: 'load_plugins' (see below).

Normally gems work find with jruby.  I tried this process with jRuby v1.3 and received a similar fail.  I'm wondering if there's not a supporting gem missing on the Java side?  If so it is definitely worth noting in the read-me.

Please advise of how to get the gems working with jRuby.  Also, what was the last version of rubygems known to be ok on jRuby (on window).

Many thanks

  Will

--------------------
W:...> ruby c:\bin\ruby\j1.5\bin\update_rubygems
C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:84: undefined method `load_plugins' for Gem:Module (NoMethodError)
        from C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:31:in `require'
        from c:/bin/ruby/j1.5/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
        from setup.rb:25


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

From luislavena at gmail.com  Fri Feb 11 20:52:38 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 11 Feb 2011 22:52:38 -0300
Subject: [Rubygems-developers] Gem::SilentUI is blocking test execution on
	Windows
Message-ID: <AANLkTin4tDWMu=+j+2Foxux=X93jKp7jmD+_i=Dk54yT@mail.gmail.com>

Hello,

Just had the time to get back to RubyGems, and found that "rake test"
do not complete due the way Gem::SilentUI is now interacting with nul
device

test_ask_for_password(TestGemSilentUI) [test/rubygems/test_gem_silent_ui.rb:34]:

expected empty result but got "\n" because I pressed 'enter' to continue

NUL: is retuning tty? as true, leading to _getch from console be required.

Seems that isatty implementation of Ruby uses _isatty MSVCRT usage,
which is broken:

http://stackoverflow.com/questions/3648711/detect-nul-file-descriptor-isatty-is-bogus

Will take a look and see if Ruby can be fixed, also investigating for
a proper workaround for RubyGems in the meantime.

-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From erik at hollensbe.org  Fri Feb 11 21:27:14 2011
From: erik at hollensbe.org (Erik Hollensbe)
Date: Fri, 11 Feb 2011 21:27:14 -0500
Subject: [Rubygems-developers] Gem::SilentUI is blocking test execution
	on Windows
In-Reply-To: <AANLkTin4tDWMu=+j+2Foxux=X93jKp7jmD+_i=Dk54yT@mail.gmail.com>
References: <AANLkTin4tDWMu=+j+2Foxux=X93jKp7jmD+_i=Dk54yT@mail.gmail.com>
Message-ID: <AA56D2E1-F7B8-4BD5-8EEF-82FB306456F9@hollensbe.org>


On Feb 11, 2011, at 8:52 PM, Luis Lavena wrote:

> Hello,
> 
> Just had the time to get back to RubyGems, and found that "rake test"
> do not complete due the way Gem::SilentUI is now interacting with nul
> device
> 
> test_ask_for_password(TestGemSilentUI) [test/rubygems/test_gem_silent_ui.rb:34]:
> 
> expected empty result but got "\n" because I pressed 'enter' to continue
> 
> NUL: is retuning tty? as true, leading to _getch from console be required.
> 
> Seems that isatty implementation of Ruby uses _isatty MSVCRT usage,
> which is broken:
> 
> http://stackoverflow.com/questions/3648711/detect-nul-file-descriptor-isatty-is-bogus
> 
> Will take a look and see if Ruby can be fixed, also investigating for
> a proper workaround for RubyGems in the meantime.

I can look into this tomorrow morning if you want, I'm responsible for those patches.

-Erik

From luislavena at gmail.com  Fri Feb 11 21:49:06 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 11 Feb 2011 23:49:06 -0300
Subject: [Rubygems-developers] Gem::SilentUI is blocking test execution
	on Windows
In-Reply-To: <AA56D2E1-F7B8-4BD5-8EEF-82FB306456F9@hollensbe.org>
References: <AANLkTin4tDWMu=+j+2Foxux=X93jKp7jmD+_i=Dk54yT@mail.gmail.com>
	<AA56D2E1-F7B8-4BD5-8EEF-82FB306456F9@hollensbe.org>
Message-ID: <AANLkTimzbg050V2G779Wt73RgMBxE80-+wgc_+A_U04v@mail.gmail.com>

On Fri, Feb 11, 2011 at 11:27 PM, Erik Hollensbe <erik at hollensbe.org> wrote:
>
> I can look into this tomorrow morning if you want, I'm responsible for those patches.
>

Not a problem, 1.8.7 and 1.9.2 suffer from this, 1.9.3dev is already fixed:

ruby -v -e "puts STDIN.tty?" < NUL

ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32]
true

ruby 1.9.2p136 (2010-12-25) [i386-mingw32]
true

ruby 1.9.3dev (2011-02-02 trunk 30760) [i386-mingw32]
false

The only workaround I can think of is compare additionally is instead
of doing tty? on the stream, do something like this?

return nil if not isarealtty?(@ins)

where you evaluate if @ins.fileno is not 3 (0 = STDIN, 1 = STDOUT, 2 =
STDERR, 3 = NUL:)

That is the only thing I can think of right now, but dunno what cygwin
is going to say about it (and is friday night, brain is really burnt
by now)

Will think on another approach during the weekend.

Cheers,
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From erik at hollensbe.org  Sat Feb 12 11:01:37 2011
From: erik at hollensbe.org (Erik Hollensbe)
Date: Sat, 12 Feb 2011 11:01:37 -0500
Subject: [Rubygems-developers] Gem::SilentUI is blocking test execution
	on Windows
In-Reply-To: <AANLkTimzbg050V2G779Wt73RgMBxE80-+wgc_+A_U04v@mail.gmail.com>
References: <AANLkTin4tDWMu=+j+2Foxux=X93jKp7jmD+_i=Dk54yT@mail.gmail.com>
	<AA56D2E1-F7B8-4BD5-8EEF-82FB306456F9@hollensbe.org>
	<AANLkTimzbg050V2G779Wt73RgMBxE80-+wgc_+A_U04v@mail.gmail.com>
Message-ID: <3347FA41-64D6-4FD2-9234-CAD13B9D0CA9@hollensbe.org>


On Feb 11, 2011, at 9:49 PM, Luis Lavena wrote:

> On Fri, Feb 11, 2011 at 11:27 PM, Erik Hollensbe <erik at hollensbe.org> wrote:
>> 
>> I can look into this tomorrow morning if you want, I'm responsible for those patches.
>> 
> 
> The only workaround I can think of is compare additionally is instead
> of doing tty? on the stream, do something like this?
> 
> return nil if not isarealtty?(@ins)
> 
> where you evaluate if @ins.fileno is not 3 (0 = STDIN, 1 = STDOUT, 2 =
> STDERR, 3 = NUL:)

This is actually a consequence of increasing file descriptors, if you:

File.open('foo', 'w')
File.open('NUL', 'r').fileno

You should get 4 or 5 back depending on how you do it (e.g., IRB)

So this is not reliable.

> That is the only thing I can think of right now, but dunno what cygwin
> is going to say about it (and is friday night, brain is really burnt
> by now)
> 
> Will think on another approach during the weekend.

I should have a patch for your RSN to consider, but I think a part of the consequence here is that more than a few tests will have to be skipped in the UI portion; my solution maintains state independently of the filehandle information and that really breaks some things in the test suite.

Anyhow, pull request should be in soon.

-Erik

From noreply at rubyforge.org  Sat Feb 12 11:22:38 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 12 Feb 2011 11:22:38 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Patches-28925 ] [gem uninstall]
	executables are removed before dependants checked
Message-ID: <20110212162238.742501858267@rubyforge.org>

Patches item #28925, was opened at 2011-02-12 16:22
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=577&aid=28925&group_id=126

Category: other
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: ryenus . (ryenus)
Assigned to: Nobody (None)
Summary: [gem uninstall] executables are removed before dependants checked

Initial Comment:
in Gem::Uninstaller#uninstall_gem,

# problematic code
    remove_executables @spec
    remove @spec, specs

remove_executables is called before the call to remove, and the dependency list is checked only in the latter, the problem? the user may have deleted the gem executables then only afterward find the gem cannot be removed.

patch uninst_chk.patch attached.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=577&aid=28925&group_id=126

From noreply at rubyforge.org  Tue Feb 15 16:55:09 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 15 Feb 2011 16:55:09 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28931 ] RubyGems
	documentation is incomplete
Message-ID: <20110215215510.15F781678332@rubyforge.org>

Bugs item #28931, was opened at 2011-02-15 22:55
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28931&group_id=126

Category: documentation
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: V?t Ondruch (voxik)
Assigned to: Nobody (None)
Summary: RubyGems documentation is incomplete

Initial Comment:
Although Kernel#gem method is well documented in source code, its documentation does not appear neither in RDoc.info nor Rubygems official documentation. I tried to raise this issue in YARD's issue tracker (https://github.com/lsegal/yard/issues/closed/#issue/252) but I had been redirected here. Could you please fix this matter? I consider it very unfortunate when documentation cannot be read using appropriate tools.


Vit

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28931&group_id=126

From noreply at rubyforge.org  Tue Feb 15 19:43:01 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 15 Feb 2011 19:43:01 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28924 ] gem update_rubygems
	Fails on JRuby 1.5
Message-ID: <20110216004301.120481858300@rubyforge.org>

Bugs item #28924, was opened at 2011-02-12 11:46
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

Category: RubyGems installer (setup.rb)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: William Mason (william)
Assigned to: Nobody (None)
Summary: gem update_rubygems Fails on JRuby 1.5

Initial Comment:
Hi there,

I get a 'NoMethodError' when I try to execute update_rubygems from the command line after loading rubygems-update-1.5.2.gem (downloaded from RubyForge).

Incidentally the rubygems-update-1.5.2.gem that is on GemCutter (rubygem.org) is corrupt.  It won't even open as a valid zip archive.  The zip file was OK.

I successfully ran the complete rubygems-update process with ruby 1.8.7 including the: update_rubygems, script.  Worked fine.

Using jRuby 1.5, the:

   gem install rubygems-update-1.5.2.gem

Worked great (apparently).  However the 

    update_rubygems

Script falls over with a: 'NoMethodError' for: 'load_plugins' (see below).

Normally gems work find with jruby.  I tried this process with jRuby v1.3 and received a similar fail.  I'm wondering if there's not a supporting gem missing on the Java side?  If so it is definitely worth noting in the read-me.

Please advise of how to get the gems working with jRuby.  Also, what was the last version of rubygems known to be ok on jRuby (on window).

Many thanks

  Will

--------------------
W:...> ruby c:\bin\ruby\j1.5\bin\update_rubygems
C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:84: undefined method `load_plugins' for Gem:Module (NoMethodError)
        from C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:31:in `require'
        from c:/bin/ruby/j1.5/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
        from setup.rb:25


----------------------------------------------------------------------

>Comment By: William Mason (william)
Date: 2011-02-16 11:43

Message:
Hi,

Addition - This bug has turned out to be quite serious
because any gem operation can now can my windows command
shell. And the JVM /jruby process can't be killed, can't
logout, and can't restart.  That means the only way out is
to power-down.

As I see it I can only clobber jruby and reinstall it with
the installation gem version. That will get attended to
eventually I'm thinking.

I think the hang is probably a JRuby issue.  But it is
instigated by the rubygem incompatibility.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

From ryand-ruby at zenspider.com  Wed Feb 16 06:44:25 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Wed, 16 Feb 2011 03:44:25 -0800
Subject: [Rubygems-developers] The 1.6 plan
Message-ID: <5CE1A407-F44D-4851-BEB6-5FD97B8FAB70@zenspider.com>

With 1.4 our focus was on cleaning up our house and getting a long overdue release out.

With 1.5 our focus was on cleaning up the mess in mri 1.9.

And 12 days from now I plan on releasing 1.6.

I've focused on revamping dependency resolution to make it more accurate. I just got our last failing test to pass. This probably just means that we're missing failing tests. We need as many eyeballs on these changes as possible.

Please poke at it and report any bugs you find. The easiest way to do this would be to install from git by running setup.rb. DO NOT DO THIS if you plan on releasing any gems between now and the actual release. Package them. Poke at them. But don't release them.

Thank you.


From luislavena at gmail.com  Wed Feb 16 09:27:16 2011
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 16 Feb 2011 11:27:16 -0300
Subject: [Rubygems-developers] The 1.6 plan
In-Reply-To: <5CE1A407-F44D-4851-BEB6-5FD97B8FAB70@zenspider.com>
References: <5CE1A407-F44D-4851-BEB6-5FD97B8FAB70@zenspider.com>
Message-ID: <AANLkTin4zE-OH_QcXB=TK2A44dFnwUv6X6__YakJZqs5@mail.gmail.com>

On Wed, Feb 16, 2011 at 8:44 AM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
> With 1.4 our focus was on cleaning up our house and getting a long overdue release out.
>
> With 1.5 our focus was on cleaning up the mess in mri 1.9.
>
> And 12 days from now I plan on releasing 1.6.
>
> I've focused on revamping dependency resolution to make it more accurate. I just got our last failing test to pass. This probably just means that we're missing failing tests. We need as many eyeballs on these changes as possible.
>

With this new dependency resolution tests, are we considering the "use
cases" of Bundler?

I've tried to look at Bundler gem activation specs (or the reason
bundler exist) and couldn't find a single one.

Ideally would like RubyGems is a bit smarter in relation to dependency
resolution, like not pulling the latest version of a gem unless
needed...

> Please poke at it and report any bugs you find. The easiest way to do this would be to install from git by running setup.rb. DO NOT DO THIS if you plan on releasing any gems between now and the actual release. Package them. Poke at them. But don't release them.
>

Will merge first the fixes for test complete on Windows and will start
using it daily and see what happens.

> Thank you.

Thanks to you for the refreshed attention to RubyGems, really appreciate it.

-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry

From noreply at rubyforge.org  Wed Feb 16 14:36:28 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 16 Feb 2011 14:36:28 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28924 ] gem update_rubygems
	Fails on JRuby 1.5
Message-ID: <20110216193628.BAC4F1858357@rubyforge.org>

Bugs item #28924, was opened at 2011-02-11 18:46
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

Category: RubyGems installer (setup.rb)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: William Mason (william)
Assigned to: Nobody (None)
Summary: gem update_rubygems Fails on JRuby 1.5

Initial Comment:
Hi there,

I get a 'NoMethodError' when I try to execute update_rubygems from the command line after loading rubygems-update-1.5.2.gem (downloaded from RubyForge).

Incidentally the rubygems-update-1.5.2.gem that is on GemCutter (rubygem.org) is corrupt.  It won't even open as a valid zip archive.  The zip file was OK.

I successfully ran the complete rubygems-update process with ruby 1.8.7 including the: update_rubygems, script.  Worked fine.

Using jRuby 1.5, the:

   gem install rubygems-update-1.5.2.gem

Worked great (apparently).  However the 

    update_rubygems

Script falls over with a: 'NoMethodError' for: 'load_plugins' (see below).

Normally gems work find with jruby.  I tried this process with jRuby v1.3 and received a similar fail.  I'm wondering if there's not a supporting gem missing on the Java side?  If so it is definitely worth noting in the read-me.

Please advise of how to get the gems working with jRuby.  Also, what was the last version of rubygems known to be ok on jRuby (on window).

Many thanks

  Will

--------------------
W:...> ruby c:\bin\ruby\j1.5\bin\update_rubygems
C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:84: undefined method `load_plugins' for Gem:Module (NoMethodError)
        from C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:31:in `require'
        from c:/bin/ruby/j1.5/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
        from setup.rb:25


----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 13:36

Message:
Others have been able to get around this by clearing RUBYOPT, which most people had set to -rubygems or similar. There appears to be a problem with the order in which things get activated under JRuby that we have not sorted out.

I believe this is probably a JRuby issue, perhaps caused by having our openssl support in a gem.

----------------------------------------------------------------------

Comment By: William Mason (william)
Date: 2011-02-15 18:43

Message:
Hi,

Addition - This bug has turned out to be quite serious
because any gem operation can now can my windows command
shell. And the JVM /jruby process can't be killed, can't
logout, and can't restart.  That means the only way out is
to power-down.

As I see it I can only clobber jruby and reinstall it with
the installation gem version. That will get attended to
eventually I'm thinking.

I think the hang is probably a JRuby issue.  But it is
instigated by the rubygem incompatibility.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

From noreply at rubyforge.org  Wed Feb 16 15:24:53 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 16 Feb 2011 15:24:53 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28924 ] gem update_rubygems
	Fails on JRuby 1.5
Message-ID: <20110216202453.6537B1858346@rubyforge.org>

Bugs item #28924, was opened at 2011-02-11 18:46
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

Category: RubyGems installer (setup.rb)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: William Mason (william)
Assigned to: Nobody (None)
Summary: gem update_rubygems Fails on JRuby 1.5

Initial Comment:
Hi there,

I get a 'NoMethodError' when I try to execute update_rubygems from the command line after loading rubygems-update-1.5.2.gem (downloaded from RubyForge).

Incidentally the rubygems-update-1.5.2.gem that is on GemCutter (rubygem.org) is corrupt.  It won't even open as a valid zip archive.  The zip file was OK.

I successfully ran the complete rubygems-update process with ruby 1.8.7 including the: update_rubygems, script.  Worked fine.

Using jRuby 1.5, the:

   gem install rubygems-update-1.5.2.gem

Worked great (apparently).  However the 

    update_rubygems

Script falls over with a: 'NoMethodError' for: 'load_plugins' (see below).

Normally gems work find with jruby.  I tried this process with jRuby v1.3 and received a similar fail.  I'm wondering if there's not a supporting gem missing on the Java side?  If so it is definitely worth noting in the read-me.

Please advise of how to get the gems working with jRuby.  Also, what was the last version of rubygems known to be ok on jRuby (on window).

Many thanks

  Will

--------------------
W:...> ruby c:\bin\ruby\j1.5\bin\update_rubygems
C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:84: undefined method `load_plugins' for Gem:Module (NoMethodError)
        from C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:31:in `require'
        from c:/bin/ruby/j1.5/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
        from setup.rb:25


----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 14:24

Message:
I was able to do update_rubygems with JRuby 1.6 master today without any problems. Of course that's just RG 1.5.0 to RG 1.5.2. Updating from an earlier version seems to be where the problems come up...

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 13:36

Message:
Others have been able to get around this by clearing RUBYOPT, which most people had set to -rubygems or similar. There appears to be a problem with the order in which things get activated under JRuby that we have not sorted out.

I believe this is probably a JRuby issue, perhaps caused by having our openssl support in a gem.

----------------------------------------------------------------------

Comment By: William Mason (william)
Date: 2011-02-15 18:43

Message:
Hi,

Addition - This bug has turned out to be quite serious
because any gem operation can now can my windows command
shell. And the JVM /jruby process can't be killed, can't
logout, and can't restart.  That means the only way out is
to power-down.

As I see it I can only clobber jruby and reinstall it with
the installation gem version. That will get attended to
eventually I'm thinking.

I think the hang is probably a JRuby issue.  But it is
instigated by the rubygem incompatibility.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

From noreply at rubyforge.org  Wed Feb 16 15:26:14 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 16 Feb 2011 15:26:14 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28924 ] gem update_rubygems
	Fails on JRuby 1.5
Message-ID: <20110216202614.E79761858346@rubyforge.org>

Bugs item #28924, was opened at 2011-02-11 18:46
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

Category: RubyGems installer (setup.rb)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: William Mason (william)
Assigned to: Nobody (None)
Summary: gem update_rubygems Fails on JRuby 1.5

Initial Comment:
Hi there,

I get a 'NoMethodError' when I try to execute update_rubygems from the command line after loading rubygems-update-1.5.2.gem (downloaded from RubyForge).

Incidentally the rubygems-update-1.5.2.gem that is on GemCutter (rubygem.org) is corrupt.  It won't even open as a valid zip archive.  The zip file was OK.

I successfully ran the complete rubygems-update process with ruby 1.8.7 including the: update_rubygems, script.  Worked fine.

Using jRuby 1.5, the:

   gem install rubygems-update-1.5.2.gem

Worked great (apparently).  However the 

    update_rubygems

Script falls over with a: 'NoMethodError' for: 'load_plugins' (see below).

Normally gems work find with jruby.  I tried this process with jRuby v1.3 and received a similar fail.  I'm wondering if there's not a supporting gem missing on the Java side?  If so it is definitely worth noting in the read-me.

Please advise of how to get the gems working with jRuby.  Also, what was the last version of rubygems known to be ok on jRuby (on window).

Many thanks

  Will

--------------------
W:...> ruby c:\bin\ruby\j1.5\bin\update_rubygems
C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:84: undefined method `load_plugins' for Gem:Module (NoMethodError)
        from C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:31:in `require'
        from c:/bin/ruby/j1.5/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
        from setup.rb:25


----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 14:26

Message:
Hmm, I was also able to update a 1.5.6 install.

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 14:24

Message:
I was able to do update_rubygems with JRuby 1.6 master today without any problems. Of course that's just RG 1.5.0 to RG 1.5.2. Updating from an earlier version seems to be where the problems come up...

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 13:36

Message:
Others have been able to get around this by clearing RUBYOPT, which most people had set to -rubygems or similar. There appears to be a problem with the order in which things get activated under JRuby that we have not sorted out.

I believe this is probably a JRuby issue, perhaps caused by having our openssl support in a gem.

----------------------------------------------------------------------

Comment By: William Mason (william)
Date: 2011-02-15 18:43

Message:
Hi,

Addition - This bug has turned out to be quite serious
because any gem operation can now can my windows command
shell. And the JVM /jruby process can't be killed, can't
logout, and can't restart.  That means the only way out is
to power-down.

As I see it I can only clobber jruby and reinstall it with
the installation gem version. That will get attended to
eventually I'm thinking.

I think the hang is probably a JRuby issue.  But it is
instigated by the rubygem incompatibility.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

From noreply at rubyforge.org  Wed Feb 16 15:30:23 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 16 Feb 2011 15:30:23 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28924 ] gem update_rubygems
	Fails on JRuby 1.5
Message-ID: <20110216203024.438371678326@rubyforge.org>

Bugs item #28924, was opened at 2011-02-11 18:46
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

Category: RubyGems installer (setup.rb)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: William Mason (william)
Assigned to: Nobody (None)
Summary: gem update_rubygems Fails on JRuby 1.5

Initial Comment:
Hi there,

I get a 'NoMethodError' when I try to execute update_rubygems from the command line after loading rubygems-update-1.5.2.gem (downloaded from RubyForge).

Incidentally the rubygems-update-1.5.2.gem that is on GemCutter (rubygem.org) is corrupt.  It won't even open as a valid zip archive.  The zip file was OK.

I successfully ran the complete rubygems-update process with ruby 1.8.7 including the: update_rubygems, script.  Worked fine.

Using jRuby 1.5, the:

   gem install rubygems-update-1.5.2.gem

Worked great (apparently).  However the 

    update_rubygems

Script falls over with a: 'NoMethodError' for: 'load_plugins' (see below).

Normally gems work find with jruby.  I tried this process with jRuby v1.3 and received a similar fail.  I'm wondering if there's not a supporting gem missing on the Java side?  If so it is definitely worth noting in the read-me.

Please advise of how to get the gems working with jRuby.  Also, what was the last version of rubygems known to be ok on jRuby (on window).

Many thanks

  Will

--------------------
W:...> ruby c:\bin\ruby\j1.5\bin\update_rubygems
C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:84: undefined method `load_plugins' for Gem:Module (NoMethodError)
        from C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:31:in `require'
        from c:/bin/ruby/j1.5/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
        from setup.rb:25


----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 14:30

Message:
Ok, reproduced by setting RUBYOPT=rubygems.

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 14:26

Message:
Hmm, I was also able to update a 1.5.6 install.

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 14:24

Message:
I was able to do update_rubygems with JRuby 1.6 master today without any problems. Of course that's just RG 1.5.0 to RG 1.5.2. Updating from an earlier version seems to be where the problems come up...

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 13:36

Message:
Others have been able to get around this by clearing RUBYOPT, which most people had set to -rubygems or similar. There appears to be a problem with the order in which things get activated under JRuby that we have not sorted out.

I believe this is probably a JRuby issue, perhaps caused by having our openssl support in a gem.

----------------------------------------------------------------------

Comment By: William Mason (william)
Date: 2011-02-15 18:43

Message:
Hi,

Addition - This bug has turned out to be quite serious
because any gem operation can now can my windows command
shell. And the JVM /jruby process can't be killed, can't
logout, and can't restart.  That means the only way out is
to power-down.

As I see it I can only clobber jruby and reinstall it with
the installation gem version. That will get attended to
eventually I'm thinking.

I think the hang is probably a JRuby issue.  But it is
instigated by the rubygem incompatibility.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

From noreply at rubyforge.org  Wed Feb 16 16:01:46 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 16 Feb 2011 16:01:46 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28924 ] gem update_rubygems
	Fails on JRuby 1.5
Message-ID: <20110216210146.8EAB81858346@rubyforge.org>

Bugs item #28924, was opened at 2011-02-11 18:46
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

Category: RubyGems installer (setup.rb)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: William Mason (william)
Assigned to: Nobody (None)
Summary: gem update_rubygems Fails on JRuby 1.5

Initial Comment:
Hi there,

I get a 'NoMethodError' when I try to execute update_rubygems from the command line after loading rubygems-update-1.5.2.gem (downloaded from RubyForge).

Incidentally the rubygems-update-1.5.2.gem that is on GemCutter (rubygem.org) is corrupt.  It won't even open as a valid zip archive.  The zip file was OK.

I successfully ran the complete rubygems-update process with ruby 1.8.7 including the: update_rubygems, script.  Worked fine.

Using jRuby 1.5, the:

   gem install rubygems-update-1.5.2.gem

Worked great (apparently).  However the 

    update_rubygems

Script falls over with a: 'NoMethodError' for: 'load_plugins' (see below).

Normally gems work find with jruby.  I tried this process with jRuby v1.3 and received a similar fail.  I'm wondering if there's not a supporting gem missing on the Java side?  If so it is definitely worth noting in the read-me.

Please advise of how to get the gems working with jRuby.  Also, what was the last version of rubygems known to be ok on jRuby (on window).

Many thanks

  Will

--------------------
W:...> ruby c:\bin\ruby\j1.5\bin\update_rubygems
C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:84: undefined method `load_plugins' for Gem:Module (NoMethodError)
        from C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:31:in `require'
        from c:/bin/ruby/j1.5/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
        from setup.rb:25


----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 15:01

Message:
I think I've found the problem.

JRuby usually tries to launch subprocess execution like "exec" or "system" in the same JVM, if they start with "ruby" or "jruby". In order to have the in-process child get an accurate environment, we pass along the modified env hash to it. Unfortunately, RUBYOPT logic is looking at the real process system env all the time, if the provided env does not have RUBYOPT set.

As a result, RUBYOPT=rubygems is *still* processed when setup.rb execs itself again, but *appears* to have been cleared since we inherit the correct ENV. That results in parts of the old rubygems being loaded first and then new rubygems pieces load and fail.

I will track this in a JRuby bug.

There are two workarounds:

For users: unset RUBYOPT before updating.

In RubyGems 1.5.x: There are ways to force the command to run in an external process always. The easiest is probably to insert "sh -c" or "cmd -c" at the beginning. Whether you (RubyGems folks) want to patch around this JRuby issue is up to you, but I don't see us putting out a 1.5.7 with just this simple fix since 1.6 is almost finished.

To reproduce:

* Download JRuby 1.5.6
* Install rubygems-update gem
* Set RUBYOPT=rubygems
* Attempt to run bin/update_rubygems

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 14:30

Message:
Ok, reproduced by setting RUBYOPT=rubygems.

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 14:26

Message:
Hmm, I was also able to update a 1.5.6 install.

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 14:24

Message:
I was able to do update_rubygems with JRuby 1.6 master today without any problems. Of course that's just RG 1.5.0 to RG 1.5.2. Updating from an earlier version seems to be where the problems come up...

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 13:36

Message:
Others have been able to get around this by clearing RUBYOPT, which most people had set to -rubygems or similar. There appears to be a problem with the order in which things get activated under JRuby that we have not sorted out.

I believe this is probably a JRuby issue, perhaps caused by having our openssl support in a gem.

----------------------------------------------------------------------

Comment By: William Mason (william)
Date: 2011-02-15 18:43

Message:
Hi,

Addition - This bug has turned out to be quite serious
because any gem operation can now can my windows command
shell. And the JVM /jruby process can't be killed, can't
logout, and can't restart.  That means the only way out is
to power-down.

As I see it I can only clobber jruby and reinstall it with
the installation gem version. That will get attended to
eventually I'm thinking.

I think the hang is probably a JRuby issue.  But it is
instigated by the rubygem incompatibility.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

From noreply at rubyforge.org  Wed Feb 16 16:32:52 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 16 Feb 2011 16:32:52 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28924 ] gem update_rubygems
	Fails on JRuby 1.5
Message-ID: <20110216213252.825631858346@rubyforge.org>

Bugs item #28924, was opened at 2011-02-11 16:46
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

Category: RubyGems installer (setup.rb)
Group: v1.5.x
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: William Mason (william)
>Assigned to: Eric Hodel (drbrain)
Summary: gem update_rubygems Fails on JRuby 1.5

Initial Comment:
Hi there,

I get a 'NoMethodError' when I try to execute update_rubygems from the command line after loading rubygems-update-1.5.2.gem (downloaded from RubyForge).

Incidentally the rubygems-update-1.5.2.gem that is on GemCutter (rubygem.org) is corrupt.  It won't even open as a valid zip archive.  The zip file was OK.

I successfully ran the complete rubygems-update process with ruby 1.8.7 including the: update_rubygems, script.  Worked fine.

Using jRuby 1.5, the:

   gem install rubygems-update-1.5.2.gem

Worked great (apparently).  However the 

    update_rubygems

Script falls over with a: 'NoMethodError' for: 'load_plugins' (see below).

Normally gems work find with jruby.  I tried this process with jRuby v1.3 and received a similar fail.  I'm wondering if there's not a supporting gem missing on the Java side?  If so it is definitely worth noting in the read-me.

Please advise of how to get the gems working with jRuby.  Also, what was the last version of rubygems known to be ok on jRuby (on window).

Many thanks

  Will

--------------------
W:...> ruby c:\bin\ruby\j1.5\bin\update_rubygems
C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:84: undefined method `load_plugins' for Gem:Module (NoMethodError)
        from C:/bin/ruby/j1.5/lib/ruby/gems/1.8/gems/rubygems-update-1.5.2/lib/rubygems/gem_runner.rb:31:in `require'
        from c:/bin/ruby/j1.5/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
        from setup.rb:25


----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-16 13:32

Message:
Closing due to third-party issue.

http://jira.codehaus.org/browse/JRUBY-5517

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 13:01

Message:
I think I've found the problem.

JRuby usually tries to launch subprocess execution like "exec" or "system" in the same JVM, if they start with "ruby" or "jruby". In order to have the in-process child get an accurate environment, we pass along the modified env hash to it. Unfortunately, RUBYOPT logic is looking at the real process system env all the time, if the provided env does not have RUBYOPT set.

As a result, RUBYOPT=rubygems is *still* processed when setup.rb execs itself again, but *appears* to have been cleared since we inherit the correct ENV. That results in parts of the old rubygems being loaded first and then new rubygems pieces load and fail.

I will track this in a JRuby bug.

There are two workarounds:

For users: unset RUBYOPT before updating.

In RubyGems 1.5.x: There are ways to force the command to run in an external process always. The easiest is probably to insert "sh -c" or "cmd -c" at the beginning. Whether you (RubyGems folks) want to patch around this JRuby issue is up to you, but I don't see us putting out a 1.5.7 with just this simple fix since 1.6 is almost finished.

To reproduce:

* Download JRuby 1.5.6
* Install rubygems-update gem
* Set RUBYOPT=rubygems
* Attempt to run bin/update_rubygems

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 12:30

Message:
Ok, reproduced by setting RUBYOPT=rubygems.

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 12:26

Message:
Hmm, I was also able to update a 1.5.6 install.

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 12:24

Message:
I was able to do update_rubygems with JRuby 1.6 master today without any problems. Of course that's just RG 1.5.0 to RG 1.5.2. Updating from an earlier version seems to be where the problems come up...

----------------------------------------------------------------------

Comment By: Charles Nutter (headius)
Date: 2011-02-16 11:36

Message:
Others have been able to get around this by clearing RUBYOPT, which most people had set to -rubygems or similar. There appears to be a problem with the order in which things get activated under JRuby that we have not sorted out.

I believe this is probably a JRuby issue, perhaps caused by having our openssl support in a gem.

----------------------------------------------------------------------

Comment By: William Mason (william)
Date: 2011-02-15 16:43

Message:
Hi,

Addition - This bug has turned out to be quite serious
because any gem operation can now can my windows command
shell. And the JVM /jruby process can't be killed, can't
logout, and can't restart.  That means the only way out is
to power-down.

As I see it I can only clobber jruby and reinstall it with
the installation gem version. That will get attended to
eventually I'm thinking.

I think the hang is probably a JRuby issue.  But it is
instigated by the rubygem incompatibility.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28924&group_id=126

From ryand-ruby at zenspider.com  Wed Feb 16 19:17:05 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Wed, 16 Feb 2011 16:17:05 -0800
Subject: [Rubygems-developers] The 1.6 plan
In-Reply-To: <5CE1A407-F44D-4851-BEB6-5FD97B8FAB70@zenspider.com>
References: <5CE1A407-F44D-4851-BEB6-5FD97B8FAB70@zenspider.com>
Message-ID: <74DACAC3-7B3E-4841-A65E-AB7332C4FCC2@zenspider.com>


On Feb 16, 2011, at 03:44 , Ryan Davis wrote:

> Please poke at it and report any bugs you find. The easiest way to do this would be to install from git by running setup.rb. DO NOT DO THIS if you plan on releasing any gems between now and the actual release. Package them. Poke at them. But don't release them.

I just pushed a change that'll make it so that beta/unreleased versions won't be able to push.

From noreply at rubyforge.org  Thu Feb 17 05:18:40 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 17 Feb 2011 05:18:40 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Feature Requests-28934 ] Rubygems
	should create whole binpath
Message-ID: <20110217101840.B27361858267@rubyforge.org>

Feature Requests item #28934, was opened at 2011-02-17 11:18
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=28934&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: V?t Ondruch (voxik)
Assigned to: Nobody (None)
Summary: Rubygems should create whole binpath

Initial Comment:
Currently, only topmost folder is created using mkdir:

https://github.com/rubygems/rubygems/blob/master/lib/rubygems/installer.rb#L268

Is there any reason why it should not be replaced by FileUtils.mkdir_p?

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=28934&group_id=126

From noreply at rubyforge.org  Thu Feb 17 14:16:30 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 17 Feb 2011 14:16:30 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28935 ] Failing rdoc
	generation doesnt fail the installation since 1.5
Message-ID: <20110217191630.90187185834E@rubyforge.org>

Bugs item #28935, was opened at 2011-02-17 20:16
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28935&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Marcus Rueckert (darix)
Assigned to: Nobody (None)
Summary: Failing rdoc generation doesnt fail the installation since 1.5

Initial Comment:
it seems gem install returns 0, even though the rdoc generation failed. in 1.3.7 it still returned the a non zero return code. as shown here http://bit.ly/f8vfi7 e.g.

important part:
[[[
1 gem installed
Installing ri documentation for ci_reporter-1.6.4...
rdoc --ri --op /var/tmp/rubygem-ci_reporter-1.6.4-build/usr/lib64/ruby/gems/1.8/doc/ci_reporter-1.6.4/ri --main README.txt -SHN -f darkfish --quiet lib History.txt Manifest.txt README.txt LICENSE.txt --title ci_reporter-1.6.4 Documentation
Installing RDoc documentation for ci_reporter-1.6.4...
rdoc --op /var/tmp/rubygem-ci_reporter-1.6.4-build/usr/lib64/ruby/gems/1.8/doc/ci_reporter-1.6.4/rdoc --main README.txt -SHN -f darkfish --quiet lib History.txt Manifest.txt README.txt LICENSE.txt --title ci_reporter-1.6.4 Doc
Invalid output formatter

For help on options, try 'rdoc --help'

ERROR:  While generating documentation for ci_reporter-1.6.4
... MESSAGE:   exit
... RDOC args: --op /var/tmp/rubygem-ci_reporter-1.6.4-build/usr/lib64/ruby/gems/1.8/doc/ci_reporter-1.6.4/rdoc --main README.txt -SHN -f darkfish --quiet lib History.txt Manifest.txt README.txt LICENSE.txt --title ci_reporter-1.6.4 Documentation
(continuing with the rest of the installation)
]]]

the problem in the build was that the ruby version didnt ship the darkfish template, but the gemspec specifies 's.rdoc_options = ["--main", "README.txt", "-SHN", "-f", "darkfish"]'.



----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28935&group_id=126

From jftucker at gmail.com  Thu Feb 17 15:48:13 2011
From: jftucker at gmail.com (James Tucker)
Date: Thu, 17 Feb 2011 12:48:13 -0800
Subject: [Rubygems-developers] The 1.6 plan
In-Reply-To: <AANLkTin4zE-OH_QcXB=TK2A44dFnwUv6X6__YakJZqs5@mail.gmail.com>
References: <5CE1A407-F44D-4851-BEB6-5FD97B8FAB70@zenspider.com>
	<AANLkTin4zE-OH_QcXB=TK2A44dFnwUv6X6__YakJZqs5@mail.gmail.com>
Message-ID: <8A3F82E5-E40C-45BA-B0F7-04DDD97B2509@gmail.com>


On Feb 16, 2011, at 6:27 AM, Luis Lavena wrote:

> On Wed, Feb 16, 2011 at 8:44 AM, Ryan Davis <ryand-ruby at zenspider.com> wrote:
>> With 1.4 our focus was on cleaning up our house and getting a long overdue release out.
>> 
>> With 1.5 our focus was on cleaning up the mess in mri 1.9.
>> 
>> And 12 days from now I plan on releasing 1.6.
>> 
>> I've focused on revamping dependency resolution to make it more accurate. I just got our last failing test to pass. This probably just means that we're missing failing tests. We need as many eyeballs on these changes as possible.
>> 
> 
> With this new dependency resolution tests, are we considering the "use
> cases" of Bundler?

Well, it's sort of what the resolver does, only the resolver takes multiple requirements and merges down, in this case, we start from a single head. The two approaches can be proven equivalent, as you'd just need to create a virtual-head with the same requirements as the multiple requirements you would give to bundlers resolver.

> I've tried to look at Bundler gem activation specs (or the reason
> bundler exist) and couldn't find a single one.

This is a common misconception. Bundler addresses more than just resolution. When I discussed this with some of their team, they said that the failure cases are actually encoded in other tests, and there's good example sets in the gem repository that is setup in the test support. That is build_repo* from here: https://github.com/carlhuda/bundler/blob/1-0-stable/spec/support/builders.rb

> Ideally would like RubyGems is a bit smarter in relation to dependency
> resolution, like not pulling the latest version of a gem unless
> needed...

I'm not sure how you can do that. This idea seems to have been floating around for a while, but it's actually invalid. You can't lazy activate dependencies without breaking code. When someone requires a file which is discovered to be in an unactivated gem, you must first activate that gem (and it's dependencies) before you require the file. The reason for this is that otherwise subsequent requires or Kernel#load calls may do the wrong thing.

This is why a manifest is absolutely required in order to do correct deep-conflict resolution. The good thing will be however, that rubygems will no longer fail to do this correctly with heads that have complex dependency trees that conflict.

>> Please poke at it and report any bugs you find. The easiest way to do this would be to install from git by running setup.rb. DO NOT DO THIS if you plan on releasing any gems between now and the actual release. Package them. Poke at them. But don't release them.

I'm pretty sure there are more cases that I wasn't able to cover in my drunken state at Rubyconf. I'm not sure I'll have time this week, if/when I do, I'll provide more cases.

From ryand-ruby at zenspider.com  Thu Feb 17 20:48:50 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Thu, 17 Feb 2011 17:48:50 -0800
Subject: [Rubygems-developers] The 1.6 plan
In-Reply-To: <8A3F82E5-E40C-45BA-B0F7-04DDD97B2509@gmail.com>
References: <5CE1A407-F44D-4851-BEB6-5FD97B8FAB70@zenspider.com>
	<AANLkTin4zE-OH_QcXB=TK2A44dFnwUv6X6__YakJZqs5@mail.gmail.com>
	<8A3F82E5-E40C-45BA-B0F7-04DDD97B2509@gmail.com>
Message-ID: <EE123990-6E46-4489-A799-823297B6DD53@zenspider.com>


On Feb 17, 2011, at 12:48 , James Tucker wrote:

> I'm not sure how you can do that. This idea seems to have been floating around for a while, but it's actually invalid. You can't lazy activate dependencies without breaking code. When someone requires a file which is discovered to be in an unactivated gem, you must first activate that gem (and it's dependencies) before you require the file. The reason for this is that otherwise subsequent requires or Kernel#load calls may do the wrong thing.

I don't believe this is true and need a test case that proves it to be so. Specifically, I don't think you need to activate the dependencies when you activate a gem. By activating dependencies, you're expecting resolution to be done all at once for the transitive closure of that part of the dep tree and that locks in versions that might not otherwise be locked in.

The biggest problem that we had with our dependency resolution (install and gem activation) was that it was eager and single pass. For the installer it was easy to make it 2 phase but for gem activation it was nearly impossible to do such a thing. Instead, I made it lazy by not activating the full transitive closure.

This seems to have fixed most, if not all, of the problems we've had in the past... But given that we didn't have a single activation test when I started on this quest, I'm sure we're missing stuff.

More tests are very very welcome.


From jftucker at gmail.com  Fri Feb 18 02:04:00 2011
From: jftucker at gmail.com (James Tucker)
Date: Thu, 17 Feb 2011 23:04:00 -0800
Subject: [Rubygems-developers] The 1.6 plan
In-Reply-To: <EE123990-6E46-4489-A799-823297B6DD53@zenspider.com>
References: <5CE1A407-F44D-4851-BEB6-5FD97B8FAB70@zenspider.com>
	<AANLkTin4zE-OH_QcXB=TK2A44dFnwUv6X6__YakJZqs5@mail.gmail.com>
	<8A3F82E5-E40C-45BA-B0F7-04DDD97B2509@gmail.com>
	<EE123990-6E46-4489-A799-823297B6DD53@zenspider.com>
Message-ID: <2018909A-2A3C-4D48-8F4B-6BEBAE81EF3A@gmail.com>


On Feb 17, 2011, at 5:48 PM, Ryan Davis wrote:

> 
> On Feb 17, 2011, at 12:48 , James Tucker wrote:
> 
>> I'm not sure how you can do that. This idea seems to have been floating around for a while, but it's actually invalid. You can't lazy activate dependencies without breaking code. When someone requires a file which is discovered to be in an unactivated gem, you must first activate that gem (and it's dependencies) before you require the file. The reason for this is that otherwise subsequent requires or Kernel#load calls may do the wrong thing.
> 
> I don't believe this is true and need a test case that proves it to be so. Specifically, I don't think you need to activate the dependencies when you activate a gem. By activating dependencies, you're expecting resolution to be done all at once for the transitive closure of that part of the dep tree and that locks in versions that might not otherwise be locked in.
> 
> The biggest problem that we had with our dependency resolution (install and gem activation) was that it was eager and single pass. For the installer it was easy to make it 2 phase but for gem activation it was nearly impossible to do such a thing. Instead, I made it lazy by not activating the full transitive closure.

Ok, I thought about it, and stand corrected, providing the semantics are presumably that the requirements set forth by a parent dependent affect any future activation of dependencies. I'm not sure how well this will play out with top-level require-happy libraries, but I could see cases where it might work.

If I remember the code order correctly, it wouldn't solve the rack, thin and sinatra issue, or the datamapper issues. Those would still conflict using lazy activation, because the libraries are actually Kernel#require'd prior to the conflict arising. An ahead of time resolution can still solve those cases. I think we did cover one of those examples in discussions at Rubyconf, I'm not sure if we made a test. A specific example is available in the 'gem lock' discussion on this ML.

> This seems to have fixed most, if not all, of the problems we've had in the past... But given that we didn't have a single activation test when I started on this quest, I'm sure we're missing stuff.
> 
> More tests are very very welcome.

I'll see if I can make the time.


From ryand-ruby at zenspider.com  Fri Feb 18 03:03:34 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Fri, 18 Feb 2011 00:03:34 -0800
Subject: [Rubygems-developers] The 1.6 plan
In-Reply-To: <2018909A-2A3C-4D48-8F4B-6BEBAE81EF3A@gmail.com>
References: <5CE1A407-F44D-4851-BEB6-5FD97B8FAB70@zenspider.com>
	<AANLkTin4zE-OH_QcXB=TK2A44dFnwUv6X6__YakJZqs5@mail.gmail.com>
	<8A3F82E5-E40C-45BA-B0F7-04DDD97B2509@gmail.com>
	<EE123990-6E46-4489-A799-823297B6DD53@zenspider.com>
	<2018909A-2A3C-4D48-8F4B-6BEBAE81EF3A@gmail.com>
Message-ID: <D50A0E30-D068-468E-885A-7085AC6938DA@zenspider.com>


On Feb 17, 2011, at 23:04 , James Tucker wrote:

> If I remember the code order correctly, it wouldn't solve the rack, thin and sinatra issue, or the datamapper issues. Those would still conflict using lazy activation, because the libraries are actually Kernel#require'd prior to the conflict arising. An ahead of time resolution can still solve those cases. I think we did cover one of those examples in discussions at Rubyconf, I'm not sure if we made a test. A specific example is available in the 'gem lock' discussion on this ML.

$ GEM_HOME=~/tmp/gems GEM_PATH=~/tmp/gems ruby ~/tmp/gems/bin/thin start
>> Using rails adapter
Missing the Rails 2.3.5 gem. Please `gem install -v=2.3.5 rails`, update your RAILS_GEM_VERSION setting in config/environment.rb for the Rails version you do have installed, or comment out RAILS_GEM_VERSION to use the latest version installed.

versus:

$ GEM_HOME=~/tmp/gems GEM_PATH=~/tmp/gems ruby -I ~/Work/git/rubygems/lib ~/tmp/gems/bin/thin start
>> Using rails adapter
>> Thin web server (v1.2.5 codename This Is Not A Web Server)
>> Maximum connections set to 1024
>> Listening on 0.0.0.0:3000, CTRL+C to stop


From noreply at rubyforge.org  Fri Feb 18 07:17:24 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 18 Feb 2011 07:17:24 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Feature Requests-28937 ] plugin
	handling with rubygems_plugin.rb
Message-ID: <20110218121724.32FFE1858300@rubyforge.org>

Feature Requests item #28937, was opened at 2011-02-18 13:17
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=28937&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Henrio Thierry (thenrio)
Assigned to: Nobody (None)
Summary: plugin handling with rubygems_plugin.rb

Initial Comment:
problem
=====
guard gem rely on open_gem to find templates provided in gems

On runtime, it uses `gem open` with options

Now open command is provided by 2 gems

* [gem-open](https://github.com/fnando/gem-open)
* [open_gem](https://github.com/adamsanderson/open_gem)

To find that gem-open was providing open command, I used ... find with hint of command

  find .rvm -name '*.rb' | xargs grep -Hn 'Open a gem into your favorite editor'

reflecting on this, here is what could have helped me

feature : know what gem provide a command
=====
It could be to augment gem help command ...

$ gem help open
...
  Provided by : open_gem-1.4.2

feature : install fails upon registration of an existing command
=====
gem install open_gem

gem install gem-open
fail : open command is already provided by open_gem-1.4.2

What do you think ?

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=28937&group_id=126

From noreply at rubyforge.org  Mon Feb 21 16:19:37 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 21 Feb 2011 16:19:37 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Feature Requests-28943 ] GEMRC
	environment variable
Message-ID: <20110221211937.99B701858300@rubyforge.org>

Feature Requests item #28943, was opened at 2011-02-21 22:19
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=28943&group_id=126

Category: `gem` commands
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Sven Schwyn (svoop)
Assigned to: Nobody (None)
Summary: GEMRC environment variable

Initial Comment:
There are now three ways to alter the gem configuration, I'd like to suggest adding one more as follows (by order of precedence):

- gem --config-file
+ GEMRC 
- ~/.gemrc
- /etc/gemrc

To make the case, here's what I'd use this feature for:

On a production server, different Rubies (e.g. MRI 1.8 and 1.9) are installed and thus the global /etc/gemrc has --format-executable set to prevent conflicts. However, every Rack application has it's own gemset (similar to how RVM does) and for these gems --no-format-executable should be used. When you cd into the context of the application, the GEMRC environment variable is automatically set (again, much like RVM does) which points to an application specific gemrc file.

GEMRC="/var/www/www.myapp.com/config/gemrc"

This feature might also come in handy on shared servers or to overrule ~/.gemrc. Or tools like RVM could use this feature to pass gem configurations. (The system Ruby reads /etc/gemrc with --ri --rdoc whereas the RVM Rubies read the gemrc from GEMRC with --no-ri --no-rdoc.)

I can give it a shot and submit an implementation, but it'd prefer to discuss whether this feature is desirable and would be included before I do so.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=578&aid=28943&group_id=126

From jftucker at gmail.com  Tue Feb 22 15:33:11 2011
From: jftucker at gmail.com (James Tucker)
Date: Tue, 22 Feb 2011 12:33:11 -0800
Subject: [Rubygems-developers] New resolver infinite loop
Message-ID: <D4C2F61F-9442-40B7-8170-02E8196D89D0@gmail.com>

Hey all, Ryan in particular,

I think this is endemic to some other issue, but I have limited time right now to debug.

The following works fine:

raggi at mbk: ~ * irb
>> require 'rubygems'
=> true
>> Gem.activate('rails', '< 3.0.0.beta')
=> true

The following goes into an infinite loop:

raggi at mbk: ~ * irb
>> require 'rubygems'
=> true
>> Gem.activate('rails', '< 3.0.0.b')


Replication environment:

% g log -n 1 --oneline
9144463  Add missing require of RemoteFetcher to the unpack command
% ruby -v
ruby 1.8.7 (2010-12-23 patchlevel 330) [i686-darwin10]
% gem list rails

*** LOCAL GEMS ***

rails (3.0.4, 3.0.3, 3.0.1, 3.0.0.rc, 3.0.0.beta4, 2.3.9.pre)


It's probably related to prerelease version but I'm not certain. I'll dump out all the active* and action* if necessary too, just let me know.

Cheers,

James

From jftucker at gmail.com  Tue Feb 22 15:41:02 2011
From: jftucker at gmail.com (James Tucker)
Date: Tue, 22 Feb 2011 12:41:02 -0800
Subject: [Rubygems-developers] Further issues with lazy activation
Message-ID: <0D2AB05A-5BAA-4262-88BC-9E5B9450A33E@gmail.com>

The following must be considered a bug:

>> require 'rubygems'
=> true
>> Gem.activate('rails', '< 3.0.0.beta')
=> true
>> require 'active_support/ordered_hash'
Gem::LoadError: Unable to activate activesupport-3.0.4, but rails-2.3.9.pre depends on activesupport (= 2.3.9.pre, runtime)
	from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:265:in `activate'
	from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:198:in `try_activate'
	from /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
	from (irb):3
>> Gem.activate('activesupport', '2.3.9.pre')
=> true
>> require 'active_support/ordered_hash'
=> true

Replication environment is the same as my last.

Thanks,

James

From ryand-ruby at zenspider.com  Tue Feb 22 16:52:41 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Tue, 22 Feb 2011 13:52:41 -0800
Subject: [Rubygems-developers] New resolver infinite loop
In-Reply-To: <D4C2F61F-9442-40B7-8170-02E8196D89D0@gmail.com>
References: <D4C2F61F-9442-40B7-8170-02E8196D89D0@gmail.com>
Message-ID: <5539C580-F463-44EA-AFA0-94060570FDB7@zenspider.com>


On Feb 22, 2011, at 12:33 , James Tucker wrote:

> Hey all, Ryan in particular,
> 
> I think this is endemic to some other issue, but I have limited time right now to debug.
> 
> The following works fine:
> 
> raggi at mbk: ~ * irb
>>> require 'rubygems'
> => true
>>> Gem.activate('rails', '< 3.0.0.beta')
> => true
> 
> The following goes into an infinite loop:
> 
> raggi at mbk: ~ * irb
>>> require 'rubygems'
> => true
>>> Gem.activate('rails', '< 3.0.0.b')
> 
> 
> Replication environment:
> 
> % g log -n 1 --oneline
> 9144463  Add missing require of RemoteFetcher to the unpack command
> % ruby -v
> ruby 1.8.7 (2010-12-23 patchlevel 330) [i686-darwin10]
> % gem list rails
> 
> *** LOCAL GEMS ***
> 
> rails (3.0.4, 3.0.3, 3.0.1, 3.0.0.rc, 3.0.0.beta4, 2.3.9.pre)
> 
> 
> It's probably related to prerelease version but I'm not certain. I'll dump out all the active* and action* if necessary too, just let me know.

I can't repro. I installed all the above versions and get:

10016 % git log -n 1 --oneline
615a5cf Add failing test for the try_activate failure case of lazy activation. Test is currently non-working I think due to util methodology
10017 % gitx
10018 % git log  C-c C-c
10018 % ruby -Ilib -rubygems -e 'Gem.activate("rails", "< 3.0.0.b"); p Gem.loaded_specs.keys.sort'
["rails"]
10019 % ruby -Ilib -rubygems -e 'Gem.activate("rails", "< 3.0.0.beta"); p Gem.loaded_specs.keys.sort'
["rails"]

I don't even see how an infinite loop is possible given that the real change I made to Gem.activate was to remove the recursion.


From ryand-ruby at zenspider.com  Tue Feb 22 16:54:09 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Tue, 22 Feb 2011 13:54:09 -0800
Subject: [Rubygems-developers] Further issues with lazy activation
In-Reply-To: <0D2AB05A-5BAA-4262-88BC-9E5B9450A33E@gmail.com>
References: <0D2AB05A-5BAA-4262-88BC-9E5B9450A33E@gmail.com>
Message-ID: <FCDD2752-BCB7-4C31-804A-674BE0624E84@zenspider.com>


On Feb 22, 2011, at 12:41 , James Tucker wrote:

> The following must be considered a bug:
> 
>>> require 'rubygems'
> => true
>>> Gem.activate('rails', '< 3.0.0.beta')
> => true
>>> require 'active_support/ordered_hash'
> Gem::LoadError: Unable to activate activesupport-3.0.4, but rails-2.3.9.pre depends on activesupport (= 2.3.9.pre, runtime)
> 	from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:265:in `activate'
> 	from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:198:in `try_activate'
> 	from /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
> 	from (irb):3
>>> Gem.activate('activesupport', '2.3.9.pre')
> => true
>>> require 'active_support/ordered_hash'
> => true
> 
> Replication environment is the same as my last.

This I can repro:

10020 % ruby -Ilib -rubygems -e 'Gem.activate("rails", "< 3.0.0.beta"); require "active_support/ordered_hash"'
./lib/rubygems.rb:265:in `activate': Unable to activate activesupport-3.0.4, but rails-2.3.9.pre depends on activesupport (= 2.3.9.pre, runtime) (Gem::LoadError)
	from ./lib/rubygems.rb:198:in `try_activate'
	from ./lib/rubygems/custom_require.rb:31:in `require'
	from -e:1

and I'm looking into it now...


From noreply at rubyforge.org  Tue Feb 22 17:56:54 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 22 Feb 2011 17:56:54 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28945 ] When I request to
	install 8 gems, it installs 12
Message-ID: <20110222225654.2E8731678326@rubyforge.org>

Bugs item #28945, was opened at 2011-02-22 14:56
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28945&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Aaron Patterson (aaronp)
Assigned to: Nobody (None)
Summary: When I request to install 8 gems, it installs 12

Initial Comment:
here is a video:

http://www.youtube.com/watch?v=sgWr7lax9G8

Here is the output from my console:


[aaron at YPCMC09458 dist (3-0-5-rc)]$ ls
actionmailer-3.0.5.rc1.gem   activeresource-3.0.5.rc1.gem
actionpack-3.0.5.rc1.gem     activesupport-3.0.5.rc1.gem
activemodel-3.0.5.rc1.gem    rails-3.0.5.rc1.gem
activerecord-3.0.5.rc1.gem   railties-3.0.5.rc1.gem
[aaron at YPCMC09458 dist (3-0-5-rc)]$ ls | wc -l
       8
[aaron at YPCMC09458 dist (3-0-5-rc)]$ gem list | grep 3.0.5
[aaron at YPCMC09458 dist (3-0-5-rc)]$ sudo gem install *
Successfully installed activesupport-3.0.5.rc1
Successfully installed activemodel-3.0.5.rc1
Successfully installed actionpack-3.0.5.rc1
Successfully installed actionmailer-3.0.5.rc1
Successfully installed actionpack-3.0.5.rc1
Successfully installed activemodel-3.0.5.rc1
Successfully installed activerecord-3.0.5.rc1
Successfully installed activeresource-3.0.5.rc1
Successfully installed activesupport-3.0.5.rc1
Successfully installed railties-3.0.5.rc1
Successfully installed rails-3.0.5.rc1
Successfully installed railties-3.0.5.rc1
12 gems installed
Installing ri documentation for activesupport-3.0.5.rc1...
Installing ri documentation for activemodel-3.0.5.rc1...
Installing ri documentation for actionpack-3.0.5.rc1...
Installing ri documentation for actionmailer-3.0.5.rc1...
Installing ri documentation for actionpack-3.0.5.rc1...
Installing ri documentation for activemodel-3.0.5.rc1...
Installing ri documentation for activerecord-3.0.5.rc1...
Installing ri documentation for activeresource-3.0.5.rc1...
Installing ri documentation for activesupport-3.0.5.rc1...
Installing ri documentation for railties-3.0.5.rc1...
Installing ri documentation for rails-3.0.5.rc1...
file 'lib' not found
Installing ri documentation for railties-3.0.5.rc1...
Installing RDoc documentation for activesupport-3.0.5.rc1...
^[Installing RDoc documentation for activemodel-3.0.5.rc1...
Installing RDoc documentation for actionpack-3.0.5.rc1...
Installing RDoc documentation for actionmailer-3.0.5.rc1...
Installing RDoc documentation for actionpack-3.0.5.rc1...
Installing RDoc documentation for activemodel-3.0.5.rc1...
Installing RDoc documentation for activerecord-3.0.5.rc1...
Installing RDoc documentation for activeresource-3.0.5.rc1...
Installing RDoc documentation for activesupport-3.0.5.rc1...
Installing RDoc documentation for railties-3.0.5.rc1...
Installing RDoc documentation for rails-3.0.5.rc1...
file 'lib' not found
Installing RDoc documentation for railties-3.0.5.rc1...
[aaron at YPCMC09458 dist (3-0-5-rc)]$ 


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28945&group_id=126

From jftucker at gmail.com  Wed Feb 23 03:46:42 2011
From: jftucker at gmail.com (James Tucker)
Date: Wed, 23 Feb 2011 00:46:42 -0800
Subject: [Rubygems-developers] New resolver infinite loop
In-Reply-To: <5539C580-F463-44EA-AFA0-94060570FDB7@zenspider.com>
References: <D4C2F61F-9442-40B7-8170-02E8196D89D0@gmail.com>
	<5539C580-F463-44EA-AFA0-94060570FDB7@zenspider.com>
Message-ID: <6BC53566-A5B6-4AE6-8D53-BB34FACA52E0@gmail.com>


On Feb 22, 2011, at 1:52 PM, Ryan Davis wrote:
> I can't repro. I installed all the above versions and get:
> 
> 10016 % git log -n 1 --oneline
> 615a5cf Add failing test for the try_activate failure case of lazy activation. Test is currently non-working I think due to util methodology
> 10017 % gitx
> 10018 % git log  C-c C-c
> 10018 % ruby -Ilib -rubygems -e 'Gem.activate("rails", "< 3.0.0.b"); p Gem.loaded_specs.keys.sort'
> ["rails"]
> 10019 % ruby -Ilib -rubygems -e 'Gem.activate("rails", "< 3.0.0.beta"); p Gem.loaded_specs.keys.sort'
> ["rails"]
> 
> I don't even see how an infinite loop is possible given that the real change I made to Gem.activate was to remove the recursion.

Unknown, I can't repro either. I did this several times this morning. I am since running the latest master. Maybe it was an outlier or related to my irbrc. I'll keep an eye, but don't worry. Thanks for having a look.

From jftucker at gmail.com  Wed Feb 23 03:47:17 2011
From: jftucker at gmail.com (James Tucker)
Date: Wed, 23 Feb 2011 00:47:17 -0800
Subject: [Rubygems-developers] Further issues with lazy activation
In-Reply-To: <FCDD2752-BCB7-4C31-804A-674BE0624E84@zenspider.com>
References: <0D2AB05A-5BAA-4262-88BC-9E5B9450A33E@gmail.com>
	<FCDD2752-BCB7-4C31-804A-674BE0624E84@zenspider.com>
Message-ID: <E8AFDF76-6488-464E-86DD-AC3C721562C0@gmail.com>


On Feb 22, 2011, at 1:54 PM, Ryan Davis wrote:

> 
> On Feb 22, 2011, at 12:41 , James Tucker wrote:
> 
>> The following must be considered a bug:
>> 
>>>> require 'rubygems'
>> => true
>>>> Gem.activate('rails', '< 3.0.0.beta')
>> => true
>>>> require 'active_support/ordered_hash'
>> Gem::LoadError: Unable to activate activesupport-3.0.4, but rails-2.3.9.pre depends on activesupport (= 2.3.9.pre, runtime)
>> 	from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:265:in `activate'
>> 	from /opt/local/lib/ruby/site_ruby/1.8/rubygems.rb:198:in `try_activate'
>> 	from /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
>> 	from (irb):3
>>>> Gem.activate('activesupport', '2.3.9.pre')
>> => true
>>>> require 'active_support/ordered_hash'
>> => true
>> 
>> Replication environment is the same as my last.
> 
> This I can repro:
> 
> 10020 % ruby -Ilib -rubygems -e 'Gem.activate("rails", "< 3.0.0.beta"); require "active_support/ordered_hash"'
> ./lib/rubygems.rb:265:in `activate': Unable to activate activesupport-3.0.4, but rails-2.3.9.pre depends on activesupport (= 2.3.9.pre, runtime) (Gem::LoadError)
> 	from ./lib/rubygems.rb:198:in `try_activate'
> 	from ./lib/rubygems/custom_require.rb:31:in `require'
> 	from -e:1
> 
> and I'm looking into it now...

Verified against the real use case and you got my test passing.

Many thanks!

From ryand-ruby at zenspider.com  Wed Feb 23 05:17:46 2011
From: ryand-ruby at zenspider.com (Ryan Davis)
Date: Wed, 23 Feb 2011 02:17:46 -0800
Subject: [Rubygems-developers] Further issues with lazy activation
In-Reply-To: <E8AFDF76-6488-464E-86DD-AC3C721562C0@gmail.com>
References: <0D2AB05A-5BAA-4262-88BC-9E5B9450A33E@gmail.com>
	<FCDD2752-BCB7-4C31-804A-674BE0624E84@zenspider.com>
	<E8AFDF76-6488-464E-86DD-AC3C721562C0@gmail.com>
Message-ID: <AD6B047B-3E13-4673-82D7-F1F905D1191C@zenspider.com>


On Feb 23, 2011, at 00:47 , James Tucker wrote:

>> This I can repro:
>> 
>> 10020 % ruby -Ilib -rubygems -e 'Gem.activate("rails", "< 3.0.0.beta"); require "active_support/ordered_hash"'
>> ./lib/rubygems.rb:265:in `activate': Unable to activate activesupport-3.0.4, but rails-2.3.9.pre depends on activesupport (= 2.3.9.pre, runtime) (Gem::LoadError)
>> 	from ./lib/rubygems.rb:198:in `try_activate'
>> 	from ./lib/rubygems/custom_require.rb:31:in `require'
>> 	from -e:1
>> 
>> and I'm looking into it now...
> 
> Verified against the real use case and you got my test passing.
> 
> Many thanks!

No. I never got your test passing. I verified that the test would never pass on 1.5 or 1.6 and removed it. I think a majority of the fault lies with the test infrastructure. We apparently don't have a good/clean way of setting up this type of test very well... tho I don't see why we don't by this time.

We should revisit this deficiency for 1.7.


From noreply at rubyforge.org  Wed Feb 23 16:47:52 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 23 Feb 2011 16:47:52 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28965 ] Gems packaged with
	`=` version requirements on 1.9.2 will not install on 1.8.7.
Message-ID: <20110223214752.26A8A1858346@rubyforge.org>

Bugs item #28965, was opened at 2011-02-23 13:47
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28965&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Aaron Patterson (aaronp)
Assigned to: Nobody (None)
Summary: Gems packaged with `=` version requirements on 1.9.2 will not install on 1.8.7.

Initial Comment:
If you create a gem with a hard version dependency (using an "=" in the version requirement), on ruby 1.9.2, that gem cannot be installed on 1.8.7.

The reason is because of a bug in the Syck YAML parser.  When Psych emits an "=", it does not include quotes (which is valid).  Syck does not parse that correctly, and when the gemspec is read on 1.8, an error occurs.

Consider the following irb session:

irb(main):001:0> require 'yaml'
=> true
irb(main):002:0> require 'psych'
=> true
irb(main):003:0> Psych.load("--- =")
=> "="
irb(main):004:0> Psych.load("--- '='")
=> "="
irb(main):006:0> YAML.load("--- =")
=> #<Syck::DefaultKey:0x00000100b203a8>
irb(main):007:0> YAML.load("--- '='")
=> "="
irb(main):008:0> Psych.dump "="
=> "--- =\n...\n"
irb(main):009:0> YAML.dump "="
=> "--- \=\\n"
irb(main):010:0> YAML.load Psych.dump '='
=> #<Syck::DefaultKey:0x00000100b03848>
irb(main):011:0>

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28965&group_id=126

From noreply at rubyforge.org  Wed Feb 23 19:07:32 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 23 Feb 2011 19:07:32 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28965 ] Gems packaged with
	`=` version requirements on 1.9.2 will not install on 1.8.7.
Message-ID: <20110224000732.625DC1858344@rubyforge.org>

Bugs item #28965, was opened at 2011-02-23 13:47
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28965&group_id=126

Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Aaron Patterson (aaronp)
>Assigned to: Ryan Davis (zenspider)
Summary: Gems packaged with `=` version requirements on 1.9.2 will not install on 1.8.7.

Initial Comment:
If you create a gem with a hard version dependency (using an "=" in the version requirement), on ruby 1.9.2, that gem cannot be installed on 1.8.7.

The reason is because of a bug in the Syck YAML parser.  When Psych emits an "=", it does not include quotes (which is valid).  Syck does not parse that correctly, and when the gemspec is read on 1.8, an error occurs.

Consider the following irb session:

irb(main):001:0> require 'yaml'
=> true
irb(main):002:0> require 'psych'
=> true
irb(main):003:0> Psych.load("--- =")
=> "="
irb(main):004:0> Psych.load("--- '='")
=> "="
irb(main):006:0> YAML.load("--- =")
=> #<Syck::DefaultKey:0x00000100b203a8>
irb(main):007:0> YAML.load("--- '='")
=> "="
irb(main):008:0> Psych.dump "="
=> "--- =\n...\n"
irb(main):009:0> YAML.dump "="
=> "--- \=\\n"
irb(main):010:0> YAML.load Psych.dump '='
=> #<Syck::DefaultKey:0x00000100b03848>
irb(main):011:0>

----------------------------------------------------------------------

>Comment By: Ryan Davis (zenspider)
Date: 2011-02-23 16:07

Message:
This is really a bug in syck... but we have a workaround in place now.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28965&group_id=126

From noreply at rubyforge.org  Wed Feb 23 19:15:05 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 23 Feb 2011 19:15:05 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28931 ] RubyGems
	documentation is incomplete
Message-ID: <20110224001505.E17BE1858344@rubyforge.org>

Bugs item #28931, was opened at 2011-02-15 13:55
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28931&group_id=126

Category: documentation
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: V?t Ondruch (voxik)
>Assigned to: Eric Hodel (drbrain)
Summary: RubyGems documentation is incomplete

Initial Comment:
Although Kernel#gem method is well documented in source code, its documentation does not appear neither in RDoc.info nor Rubygems official documentation. I tried to raise this issue in YARD's issue tracker (https://github.com/lsegal/yard/issues/closed/#issue/252) but I had been redirected here. Could you please fix this matter? I consider it very unfortunate when documentation cannot be read using appropriate tools.


Vit

----------------------------------------------------------------------

>Comment By: Ryan Davis (zenspider)
Date: 2011-02-23 16:15

Message:
This is a bug in rdoc

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28931&group_id=126

From noreply at rubyforge.org  Wed Feb 23 19:17:20 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 23 Feb 2011 19:17:20 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28945 ] When I request to
	install 8 gems, it installs 12
Message-ID: <20110224001720.A2875185834E@rubyforge.org>

Bugs item #28945, was opened at 2011-02-22 14:56
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28945&group_id=126

Category: `gem install` command
Group: None
Status: Open
>Resolution: Accepted
>Priority: 1
Submitted By: Aaron Patterson (aaronp)
>Assigned to: Ryan Davis (zenspider)
Summary: When I request to install 8 gems, it installs 12

Initial Comment:
here is a video:

http://www.youtube.com/watch?v=sgWr7lax9G8

Here is the output from my console:


[aaron at YPCMC09458 dist (3-0-5-rc)]$ ls
actionmailer-3.0.5.rc1.gem   activeresource-3.0.5.rc1.gem
actionpack-3.0.5.rc1.gem     activesupport-3.0.5.rc1.gem
activemodel-3.0.5.rc1.gem    rails-3.0.5.rc1.gem
activerecord-3.0.5.rc1.gem   railties-3.0.5.rc1.gem
[aaron at YPCMC09458 dist (3-0-5-rc)]$ ls | wc -l
       8
[aaron at YPCMC09458 dist (3-0-5-rc)]$ gem list | grep 3.0.5
[aaron at YPCMC09458 dist (3-0-5-rc)]$ sudo gem install *
Successfully installed activesupport-3.0.5.rc1
Successfully installed activemodel-3.0.5.rc1
Successfully installed actionpack-3.0.5.rc1
Successfully installed actionmailer-3.0.5.rc1
Successfully installed actionpack-3.0.5.rc1
Successfully installed activemodel-3.0.5.rc1
Successfully installed activerecord-3.0.5.rc1
Successfully installed activeresource-3.0.5.rc1
Successfully installed activesupport-3.0.5.rc1
Successfully installed railties-3.0.5.rc1
Successfully installed rails-3.0.5.rc1
Successfully installed railties-3.0.5.rc1
12 gems installed
Installing ri documentation for activesupport-3.0.5.rc1...
Installing ri documentation for activemodel-3.0.5.rc1...
Installing ri documentation for actionpack-3.0.5.rc1...
Installing ri documentation for actionmailer-3.0.5.rc1...
Installing ri documentation for actionpack-3.0.5.rc1...
Installing ri documentation for activemodel-3.0.5.rc1...
Installing ri documentation for activerecord-3.0.5.rc1...
Installing ri documentation for activeresource-3.0.5.rc1...
Installing ri documentation for activesupport-3.0.5.rc1...
Installing ri documentation for railties-3.0.5.rc1...
Installing ri documentation for rails-3.0.5.rc1...
file 'lib' not found
Installing ri documentation for railties-3.0.5.rc1...
Installing RDoc documentation for activesupport-3.0.5.rc1...
^[Installing RDoc documentation for activemodel-3.0.5.rc1...
Installing RDoc documentation for actionpack-3.0.5.rc1...
Installing RDoc documentation for actionmailer-3.0.5.rc1...
Installing RDoc documentation for actionpack-3.0.5.rc1...
Installing RDoc documentation for activemodel-3.0.5.rc1...
Installing RDoc documentation for activerecord-3.0.5.rc1...
Installing RDoc documentation for activeresource-3.0.5.rc1...
Installing RDoc documentation for activesupport-3.0.5.rc1...
Installing RDoc documentation for railties-3.0.5.rc1...
Installing RDoc documentation for rails-3.0.5.rc1...
file 'lib' not found
Installing RDoc documentation for railties-3.0.5.rc1...
[aaron at YPCMC09458 dist (3-0-5-rc)]$ 


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28945&group_id=126

From noreply at rubyforge.org  Wed Feb 23 19:49:49 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed, 23 Feb 2011 19:49:49 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28935 ] Failing rdoc
	generation doesnt fail the installation since 1.5
Message-ID: <20110224004949.D487E185834E@rubyforge.org>

Bugs item #28935, was opened at 2011-02-17 11:16
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28935&group_id=126

Category: `gem install` command
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Marcus Rueckert (darix)
Assigned to: Nobody (None)
Summary: Failing rdoc generation doesnt fail the installation since 1.5

Initial Comment:
it seems gem install returns 0, even though the rdoc generation failed. in 1.3.7 it still returned the a non zero return code. as shown here http://bit.ly/f8vfi7 e.g.

important part:
[[[
1 gem installed
Installing ri documentation for ci_reporter-1.6.4...
rdoc --ri --op /var/tmp/rubygem-ci_reporter-1.6.4-build/usr/lib64/ruby/gems/1.8/doc/ci_reporter-1.6.4/ri --main README.txt -SHN -f darkfish --quiet lib History.txt Manifest.txt README.txt LICENSE.txt --title ci_reporter-1.6.4 Documentation
Installing RDoc documentation for ci_reporter-1.6.4...
rdoc --op /var/tmp/rubygem-ci_reporter-1.6.4-build/usr/lib64/ruby/gems/1.8/doc/ci_reporter-1.6.4/rdoc --main README.txt -SHN -f darkfish --quiet lib History.txt Manifest.txt README.txt LICENSE.txt --title ci_reporter-1.6.4 Doc
Invalid output formatter

For help on options, try 'rdoc --help'

ERROR:  While generating documentation for ci_reporter-1.6.4
... MESSAGE:   exit
... RDOC args: --op /var/tmp/rubygem-ci_reporter-1.6.4-build/usr/lib64/ruby/gems/1.8/doc/ci_reporter-1.6.4/rdoc --main README.txt -SHN -f darkfish --quiet lib History.txt Manifest.txt README.txt LICENSE.txt --title ci_reporter-1.6.4 Documentation
(continuing with the rest of the installation)
]]]

the problem in the build was that the ruby version didnt ship the darkfish template, but the gemspec specifies 's.rdoc_options = ["--main", "README.txt", "-SHN", "-f", "darkfish"]'.



----------------------------------------------------------------------

>Comment By: Ryan Davis (zenspider)
Date: 2011-02-23 16:49

Message:
DocManager was passing in --quiet which does a lot more than just "don't output stuff". I've removed that and forced the exit to be 1 if it borks.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28935&group_id=126

From noreply at rubyforge.org  Thu Feb 24 12:57:05 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu, 24 Feb 2011 12:57:05 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28993 ] "gem uninstall" and
	--format-executable
Message-ID: <20110224175705.8D6141858267@rubyforge.org>

Bugs item #28993, was opened at 2011-02-24 18:57
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28993&group_id=126

Category: `gem install` command
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Sven Schwyn (svoop)
Assigned to: Nobody (None)
Summary: "gem uninstall" and --format-executable

Initial Comment:
I'm observing the following issue on my Gentoo box with several Rubies (MRI 1.8 and 1.9) installed:

cat /etc/gemrc
  ---
  gem: --format-executable

gem19 install rake

ls /usr/local/bin
  rake19           # executable installed by Rubygems
  rake -> rake19   # convenience symlink is created by Gentoo

gem uninstall rake

ls /usr/local/bin
  rake19

Apparently, the "gem uninstall" command does not honor --format-executable.

Wouldn't it be a more consistent behavior if the versioned (or formatted) executable were uninstalled? (Gentoo would then take care of the dead symlink.)


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28993&group_id=126

From noreply at rubyforge.org  Fri Feb 25 11:17:15 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 25 Feb 2011 11:17:15 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-29034 ] undefined
	class/module YAML::PrivateType
Message-ID: <20110225161715.EF2651858357@rubyforge.org>

Bugs item #29034, was opened at 2011-02-25 10:17
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

Category: `gem install` command (extensions)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Adri?n De la Cruz (lobo_tuerto)
Assigned to: Nobody (None)
Summary: undefined class/module YAML::PrivateType

Initial Comment:
I'm on Ubuntu 10.10, using rvm and just upgraded (yesterday) rubygems from 1.5.0 to 1.5.2.

Now I'm getting this strange error whenever I try to install my recently released gems (with Jeweler).

I have two cases: missile-command-ruby and lotu.


========= missile-command-ruby =========

$ gem install missile-command-ruby
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

Even a local rake install gives:

$ rake install
(in /home/oewolf/development/gamedev/github/missile-command-ruby)
  Successfully built RubyGem
  Name: missile-command-ruby
  Version: 0.0.6
  File: missile-command-ruby-0.0.6.gem
Executing "ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem":
ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType
rake aborted!
Command failed with status (1): [ruby -S gem install ./pkg/missile-command-...]


========= lotu =========

$ gem install lotu
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

$ rake install
(in /home/oewolf/development/gamedev/github/lotu)
  Successfully built RubyGem
  Name: lotu
  Version: 0.1.17
  File: lotu-0.1.17.gem
Executing "ruby -S gem install ./pkg/lotu-0.1.17.gem":
ruby -S gem install ./pkg/lotu-0.1.17.gem
Successfully installed lotu-0.1.17
1 gem installed
Installing ri documentation for lotu-0.1.17...
Installing RDoc documentation for lotu-0.1.17...



The last one install successfully via rake install... weird.

Any help regarding this? if you need more info just post it in a follow up.


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

From noreply at rubyforge.org  Fri Feb 25 11:38:28 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 25 Feb 2011 11:38:28 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-29034 ] undefined
	class/module YAML::PrivateType
Message-ID: <20110225163828.6E0B91858357@rubyforge.org>

Bugs item #29034, was opened at 2011-02-25 10:17
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

Category: `gem install` command (extensions)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Adri?n De la Cruz (lobo_tuerto)
Assigned to: Nobody (None)
Summary: undefined class/module YAML::PrivateType

Initial Comment:
I'm on Ubuntu 10.10, using rvm and just upgraded (yesterday) rubygems from 1.5.0 to 1.5.2.

Now I'm getting this strange error whenever I try to install my recently released gems (with Jeweler).

I have two cases: missile-command-ruby and lotu.


========= missile-command-ruby =========

$ gem install missile-command-ruby
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

Even a local rake install gives:

$ rake install
(in /home/oewolf/development/gamedev/github/missile-command-ruby)
  Successfully built RubyGem
  Name: missile-command-ruby
  Version: 0.0.6
  File: missile-command-ruby-0.0.6.gem
Executing "ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem":
ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType
rake aborted!
Command failed with status (1): [ruby -S gem install ./pkg/missile-command-...]


========= lotu =========

$ gem install lotu
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

$ rake install
(in /home/oewolf/development/gamedev/github/lotu)
  Successfully built RubyGem
  Name: lotu
  Version: 0.1.17
  File: lotu-0.1.17.gem
Executing "ruby -S gem install ./pkg/lotu-0.1.17.gem":
ruby -S gem install ./pkg/lotu-0.1.17.gem
Successfully installed lotu-0.1.17
1 gem installed
Installing ri documentation for lotu-0.1.17...
Installing RDoc documentation for lotu-0.1.17...



The last one install successfully via rake install... weird.

Any help regarding this? if you need more info just post it in a follow up.


----------------------------------------------------------------------

>Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 10:38

Message:
Ruby version: ruby-1.9.2-p136 (managed with rvm)

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

From noreply at rubyforge.org  Fri Feb 25 11:56:51 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 25 Feb 2011 11:56:51 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-29034 ] undefined
	class/module YAML::PrivateType
Message-ID: <20110225165651.600061858356@rubyforge.org>

Bugs item #29034, was opened at 2011-02-25 10:17
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

Category: `gem install` command (extensions)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Adri?n De la Cruz (lobo_tuerto)
Assigned to: Nobody (None)
Summary: undefined class/module YAML::PrivateType

Initial Comment:
I'm on Ubuntu 10.10, using rvm and just upgraded (yesterday) rubygems from 1.5.0 to 1.5.2.

Now I'm getting this strange error whenever I try to install my recently released gems (with Jeweler).

I have two cases: missile-command-ruby and lotu.


========= missile-command-ruby =========

$ gem install missile-command-ruby
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

Even a local rake install gives:

$ rake install
(in /home/oewolf/development/gamedev/github/missile-command-ruby)
  Successfully built RubyGem
  Name: missile-command-ruby
  Version: 0.0.6
  File: missile-command-ruby-0.0.6.gem
Executing "ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem":
ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType
rake aborted!
Command failed with status (1): [ruby -S gem install ./pkg/missile-command-...]


========= lotu =========

$ gem install lotu
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

$ rake install
(in /home/oewolf/development/gamedev/github/lotu)
  Successfully built RubyGem
  Name: lotu
  Version: 0.1.17
  File: lotu-0.1.17.gem
Executing "ruby -S gem install ./pkg/lotu-0.1.17.gem":
ruby -S gem install ./pkg/lotu-0.1.17.gem
Successfully installed lotu-0.1.17
1 gem installed
Installing ri documentation for lotu-0.1.17...
Installing RDoc documentation for lotu-0.1.17...



The last one install successfully via rake install... weird.

Any help regarding this? if you need more info just post it in a follow up.


----------------------------------------------------------------------

>Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 10:56

Message:
Related info:

http://www.mail-archive.com/rubygems-
developers at rubyforge.org/msg04392.html

http://comments.gmane.org/gmane.comp.lang.ruby.general/33536
9

http://help.rubygems.org/discussions/problems/483-gems-
built-with-rubygems-150-ruby-192-do-not-install-properly-
with-150-187

=======================================
Here is my gem env:

$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.2
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-
linux]
  - INSTALLATION DIRECTORY: /home/oewolf/.rvm/gems/ruby-
1.9.2-p136
  - RUBY EXECUTABLE: /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/oewolf/.rvm/gems/ruby-1.9.2-
p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-linux
  - GEM PATHS:
     - /home/oewolf/.rvm/gems/ruby-1.9.2-p136
     - /home/oewolf/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 10:38

Message:
Ruby version: ruby-1.9.2-p136 (managed with rvm)

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

From noreply at rubyforge.org  Fri Feb 25 11:59:37 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 25 Feb 2011 11:59:37 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-29034 ] undefined
	class/module YAML::PrivateType
Message-ID: <20110225165937.CF1301678325@rubyforge.org>

Bugs item #29034, was opened at 2011-02-25 10:17
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

Category: `gem install` command (extensions)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Adri?n De la Cruz (lobo_tuerto)
Assigned to: Nobody (None)
Summary: undefined class/module YAML::PrivateType

Initial Comment:
I'm on Ubuntu 10.10, using rvm and just upgraded (yesterday) rubygems from 1.5.0 to 1.5.2.

Now I'm getting this strange error whenever I try to install my recently released gems (with Jeweler).

I have two cases: missile-command-ruby and lotu.


========= missile-command-ruby =========

$ gem install missile-command-ruby
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

Even a local rake install gives:

$ rake install
(in /home/oewolf/development/gamedev/github/missile-command-ruby)
  Successfully built RubyGem
  Name: missile-command-ruby
  Version: 0.0.6
  File: missile-command-ruby-0.0.6.gem
Executing "ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem":
ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType
rake aborted!
Command failed with status (1): [ruby -S gem install ./pkg/missile-command-...]


========= lotu =========

$ gem install lotu
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

$ rake install
(in /home/oewolf/development/gamedev/github/lotu)
  Successfully built RubyGem
  Name: lotu
  Version: 0.1.17
  File: lotu-0.1.17.gem
Executing "ruby -S gem install ./pkg/lotu-0.1.17.gem":
ruby -S gem install ./pkg/lotu-0.1.17.gem
Successfully installed lotu-0.1.17
1 gem installed
Installing ri documentation for lotu-0.1.17...
Installing RDoc documentation for lotu-0.1.17...



The last one install successfully via rake install... weird.

Any help regarding this? if you need more info just post it in a follow up.


----------------------------------------------------------------------

>Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 10:59

Message:
Output of gem install with debug info:


$ gem install lotu --debug
Exception `NameError' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:16
3 - uninitialized constant Gem::Commands::InstallCommand
Exception `Gem::LoadError' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems.rb:861 - Could 
not find RubyGem sources (> 0.0.1)

Exception `Errno::EAGAIN' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-p136/lib/ruby/1.9.1/net/protocol.rb:135 - Resource 
temporarily unavailable - read would block
Exception `Errno::EAGAIN' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-p136/lib/ruby/1.9.1/net/protocol.rb:135 - Resource 
temporarily unavailable - read would block
Exception `ArgumentError' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:289 
- undefined class/module YAML::PrivateType
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:289:
in `load'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:289:
in `_load'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:124:i
n `load'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:124:i
n `fetch_spec'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:86:in 
`block in fetch_with_errors'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:85:in 
`map'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:85:in 
`fetch_with_errors'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.
rb:108:in `find_gems_with_sources'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.
rb:212:in `find_spec_by_name_and_version'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.
rb:244:in `install'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/commands/install_comm
and.rb:120:in `block in execute'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/commands/install_comm
and.rb:115:in `each'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/commands/install_comm
and.rb:115:in `execute'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command.rb:278:in 
`invoke'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:13
3:in `process_args'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:10
3:in `run'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/gem_runner.rb:63:in 
`run'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/bin/gem:21:in `<main>'


----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 10:56

Message:
Related info:

http://www.mail-archive.com/rubygems-
developers at rubyforge.org/msg04392.html

http://comments.gmane.org/gmane.comp.lang.ruby.general/33536
9

http://help.rubygems.org/discussions/problems/483-gems-
built-with-rubygems-150-ruby-192-do-not-install-properly-
with-150-187

=======================================
Here is my gem env:

$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.2
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-
linux]
  - INSTALLATION DIRECTORY: /home/oewolf/.rvm/gems/ruby-
1.9.2-p136
  - RUBY EXECUTABLE: /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/oewolf/.rvm/gems/ruby-1.9.2-
p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-linux
  - GEM PATHS:
     - /home/oewolf/.rvm/gems/ruby-1.9.2-p136
     - /home/oewolf/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 10:38

Message:
Ruby version: ruby-1.9.2-p136 (managed with rvm)

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

From noreply at rubyforge.org  Fri Feb 25 12:30:44 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 25 Feb 2011 12:30:44 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-29034 ] undefined
	class/module YAML::PrivateType
Message-ID: <20110225173044.D09CB1858356@rubyforge.org>

Bugs item #29034, was opened at 2011-02-25 10:17
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

Category: `gem install` command (extensions)
Group: v1.5.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Adri?n De la Cruz (lobo_tuerto)
Assigned to: Nobody (None)
Summary: undefined class/module YAML::PrivateType

Initial Comment:
I'm on Ubuntu 10.10, using rvm and just upgraded (yesterday) rubygems from 1.5.0 to 1.5.2.

Now I'm getting this strange error whenever I try to install my recently released gems (with Jeweler).

I have two cases: missile-command-ruby and lotu.


========= missile-command-ruby =========

$ gem install missile-command-ruby
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

Even a local rake install gives:

$ rake install
(in /home/oewolf/development/gamedev/github/missile-command-ruby)
  Successfully built RubyGem
  Name: missile-command-ruby
  Version: 0.0.6
  File: missile-command-ruby-0.0.6.gem
Executing "ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem":
ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType
rake aborted!
Command failed with status (1): [ruby -S gem install ./pkg/missile-command-...]


========= lotu =========

$ gem install lotu
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

$ rake install
(in /home/oewolf/development/gamedev/github/lotu)
  Successfully built RubyGem
  Name: lotu
  Version: 0.1.17
  File: lotu-0.1.17.gem
Executing "ruby -S gem install ./pkg/lotu-0.1.17.gem":
ruby -S gem install ./pkg/lotu-0.1.17.gem
Successfully installed lotu-0.1.17
1 gem installed
Installing ri documentation for lotu-0.1.17...
Installing RDoc documentation for lotu-0.1.17...



The last one install successfully via rake install... weird.

Any help regarding this? if you need more info just post it in a follow up.


----------------------------------------------------------------------

>Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 11:30

Message:
UPDATE

It's all working now after re-releasing the gems.
Seems like the last release was done with 1.5.0, then 
upgraded to 1.5.2 and that's when the problems appeared.

They are gone now, thank you. ;)

----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 10:59

Message:
Output of gem install with debug info:


$ gem install lotu --debug
Exception `NameError' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:16
3 - uninitialized constant Gem::Commands::InstallCommand
Exception `Gem::LoadError' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems.rb:861 - Could 
not find RubyGem sources (> 0.0.1)

Exception `Errno::EAGAIN' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-p136/lib/ruby/1.9.1/net/protocol.rb:135 - Resource 
temporarily unavailable - read would block
Exception `Errno::EAGAIN' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-p136/lib/ruby/1.9.1/net/protocol.rb:135 - Resource 
temporarily unavailable - read would block
Exception `ArgumentError' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:289 
- undefined class/module YAML::PrivateType
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:289:
in `load'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:289:
in `_load'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:124:i
n `load'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:124:i
n `fetch_spec'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:86:in 
`block in fetch_with_errors'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:85:in 
`map'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:85:in 
`fetch_with_errors'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.
rb:108:in `find_gems_with_sources'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.
rb:212:in `find_spec_by_name_and_version'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.
rb:244:in `install'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/commands/install_comm
and.rb:120:in `block in execute'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/commands/install_comm
and.rb:115:in `each'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/commands/install_comm
and.rb:115:in `execute'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command.rb:278:in 
`invoke'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:13
3:in `process_args'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:10
3:in `run'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/gem_runner.rb:63:in 
`run'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/bin/gem:21:in `<main>'


----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 10:56

Message:
Related info:

http://www.mail-archive.com/rubygems-
developers at rubyforge.org/msg04392.html

http://comments.gmane.org/gmane.comp.lang.ruby.general/33536
9

http://help.rubygems.org/discussions/problems/483-gems-
built-with-rubygems-150-ruby-192-do-not-install-properly-
with-150-187

=======================================
Here is my gem env:

$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.2
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-
linux]
  - INSTALLATION DIRECTORY: /home/oewolf/.rvm/gems/ruby-
1.9.2-p136
  - RUBY EXECUTABLE: /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/oewolf/.rvm/gems/ruby-1.9.2-
p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-linux
  - GEM PATHS:
     - /home/oewolf/.rvm/gems/ruby-1.9.2-p136
     - /home/oewolf/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 10:38

Message:
Ruby version: ruby-1.9.2-p136 (managed with rvm)

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

From noreply at rubyforge.org  Fri Feb 25 13:24:52 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 25 Feb 2011 13:24:52 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28907 ] [RG 1.5.0/Ruby 1.9.x]
	source gem build error due to syck?
Message-ID: <20110225182452.EBB581678329@rubyforge.org>

Bugs item #28907, was opened at 2011-02-03 18:59
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

Category: `gem` commands (other)
Group: v1.5.x
Status: Closed
Resolution: Rejected
Priority: 3
Submitted By: Jon Forums (jonforums)
Assigned to: Eric Hodel (drbrain)
Summary: [RG 1.5.0/Ruby 1.9.x] source gem build error due to syck?

Initial Comment:
When building a source gem from http://github.com/oopsforge/oops-null using 'rake gem' I get the following error on Win7 with:

  * ruby 1.9.2p174 (2011-01-28 revision 30696) [i386-mingw32]
  * ruby 1.9.3dev (2011-02-04 trunk 30776) [i386-mingw32]

but no errors using "ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32]".  

Manually building via 'gem build oops-null.gemspec' work fine on all the Ruby versions including JRuby 1.6.0.RC1.  All versions have been upgraded to RG 1.5.0 via "gem update --system".

FWIW, the failure does not occur on "ruby 1.9.2 (2010-12-25 patchlevel 136) [i386-mingw32]" using RG 1.3.7

My "fix" was to add the following lines to the project Rakefile after the 3 require's:

require 'yaml'
YAML::ENGINE.yamler='psych' if defined?(YAML::ENGINE)

I will try to replicate on my Arch system later this afternoon.

Reproducible?

Jon


== ERROR ==

C:\projects\oops-null-git>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.2 (2011-01-28 patchlevel 174) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/Users/Jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", "http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org


C:\projects\oops-null-git>rake gem
(in C:/projects/oops-null-git)
mkdir -p pkg
mkdir -p pkg
mkdir -p pkg/oops-null-0.3.0/bin
rm -f pkg/oops-null-0.3.0/bin/nulloops
ln bin/nulloops pkg/oops-null-0.3.0/bin/nulloops
rm -f pkg/oops-null-0.3.0/Rakefile
ln Rakefile pkg/oops-null-0.3.0/Rakefile
rm -f pkg/oops-null-0.3.0/oops-null.gemspec
ln oops-null.gemspec pkg/oops-null-0.3.0/oops-null.gemspec
mkdir -p pkg/oops-null-0.3.0/ext/oops_null
rm -f pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
ln ext/oops_null/extconf.rb pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
ln ext/oops_null/oops_null.c pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
ln ext/oops_null/oops_null.h pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
mkdir -p pkg/oops-null-0.3.0/lib
rm -f pkg/oops-null-0.3.0/lib/oops-null.rb
ln lib/oops-null.rb pkg/oops-null-0.3.0/lib/oops-null.rb
cd pkg/oops-null-0.3.0
rake aborted!
undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
C:/ruby192/lib/ruby/1.9.1/psych.rb:166:in `dump'
C:/ruby192/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block (2 levels) in to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `map'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `block in to_yaml'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `call'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `emit'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:725:in `to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1157:in `when_writing'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1092:in `chdir'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `call'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `block in execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:595:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:605:in `block in invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:594:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:581:in `invoke'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2041:in `invoke_task'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block (2 levels) in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2013:in `top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1992:in `run'
C:/ruby192/bin/rake:31:in `<main>'

----------------------------------------------------------------------

Comment By: Roger Pack (rogerdpack)
Date: 2011-02-25 18:24

Message:
Just got this with jeweler, too, FYI.

https://gist.github.com/844237

----------------------------------------------------------------------

Comment By: Leonard Chin (lchin)
Date: 2011-02-10 07:37

Message:
The same error occurs with hoe

Using RubyGems at commit 182bcaf7bd4f77493794 with Ruby 1.9.2-p136
https://github.com/rubygems/rubygems/tree/182bcaf7bd4f77493794d216ac37aa9935655943

rake package --trace
(in /Users/lchin/Downloads/buggy)
** Invoke package (first_time)
** Invoke pkg/buggy-1.0.0.tgz (first_time, not_needed)
** Invoke pkg/buggy-1.0.0 (first_time, not_needed)
** Invoke .autotest (first_time, not_needed)
** Invoke History.txt (first_time, not_needed)
** Invoke Manifest.txt (first_time, not_needed)
** Invoke README.txt (first_time, not_needed)
** Invoke Rakefile (first_time, not_needed)
** Invoke bin/buggy (first_time, not_needed)
** Invoke lib/buggy.rb (first_time, not_needed)
** Invoke test/test_buggy.rb (first_time, not_needed)
** Invoke .autotest (not_needed)
** Invoke History.txt (not_needed)
** Invoke Manifest.txt (not_needed)
** Invoke README.txt (not_needed)
** Invoke Rakefile (not_needed)
** Invoke bin/buggy (not_needed)
** Invoke lib/buggy.rb (not_needed)
** Invoke test/test_buggy.rb (not_needed)
** Invoke gem (first_time)
** Invoke pkg/buggy-1.0.0.gem (first_time)
** Invoke pkg (first_time, not_needed)
** Invoke pkg/buggy-1.0.0 (not_needed)
** Invoke .autotest (not_needed)
** Invoke History.txt (not_needed)
** Invoke Manifest.txt (not_needed)
** Invoke README.txt (not_needed)
** Invoke Rakefile (not_needed)
** Invoke bin/buggy (not_needed)
** Invoke lib/buggy.rb (not_needed)
** Invoke test/test_buggy.rb (not_needed)
** Execute pkg/buggy-1.0.0.gem
cd pkg/buggy-1.0.0
WARNING:  description and summary are identical
rake aborted!
undefined method `write' for #<Syck::Emitter:0x00000100919d48>
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych.rb:166:in `dump'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:728:in `block (2 levels) in to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `map'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block in to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/syck.rb:401:in `call'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/syck.rb:401:in `emit'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:1159:in `when_writing'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:1094:in `chdir'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:636:in `call'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:636:in `block in execute'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:631:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:597:in `block in invoke_with_call_chain'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:607:in `block in invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:596:in `block in invoke_with_call_chain'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:607:in `block in invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:596:in `block in invoke_with_call_chain'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2029:in `block (2 levels) in top_level'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2029:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2029:in `block in top_level'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2001:in `block in run'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/bin/rake:31:in `<top (required)>'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/bin/rake:19:in `load'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/bin/rake:19:in `<main>'

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-05 22:00

Message:
All OK now with the updated rake-compiler.

So I'm clear, this is the main commit to pay attention to?

https://github.com/rubygems/rubygems/commit/67f9f760c782142d9bfd8099750274ba498d6682

Given the simple tweak to rake-compiler, is your
recommendation that other gems requiring yaml also prefer
psych when running on 1.9.2+ and RG 1.5.0+

FWIW, I personally like the idea of preferring psych, but
would like to have first seen it mentioned in one of the
following rather than in a bt:

http://blog.segment7.net/2011/01/31/rubygems-1-5

https://github.com/rubygems/rubygems/blob/master/UPGRADING.rdoc 

Jon

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 23:37

Message:
Yes, you are loading syck (require 'yaml') before psych (require 'psych'):

https://github.com/luislavena/rake-compiler/blob/master/lib/rake/baseextensiontask.rb

This is not supported.

A patch will be sent to rake-compiler.

You can work around this by requiring psych before rake-compiler.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 21:01

Message:
That's not the issue, sorry I wasn't clear.  I'm not mixing 
syck or psyck in the same ruby in my code.

My original Rakefile https://github.com/oopsforge/oops-
null/blob/master/Rakefile that worked pre-1.5.0 didn't 
explicitly require 'yaml' or the YAML::ENGINE.yamler= 
nonsense.

I added these lines to get the gem to build when I saw the 
error message

undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in 
`end_document'
...

..as I guessed that explicitly setting the YAML engine to 
psych would prevent syck from being visited/wrapped by 
psych.

I think something's changed in RG 1.5.0 and/or ruby_1_9_2 or 
trunk that's causing the problem. I wanted to dig into how 
psych was visiting/wrapping syck but ran out of time. I also 
did a quick look through rake-compiler and don't think it's 
to blame.

Given that my original Rakefile fails on Win7 MRI 1.9.2-
p174, 1.9.2-p136, 1.9.3dev and Arch 1.9.3dev when using RG 
1.5.0 I still think the problem is in RG.

Hopefully I explained it more clearly this time.

Would you take one more look at that long back trace and see 
if you change your mind on the issue?

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 20:33

Message:
Do not mix syck (require 'yaml') and psych (require 'psych') in the same ruby.

RubyGems uses psych on ruby 1.9.2 and newer as syck is deprecated and will be removed at a future date.  Please update your Rakefile to match.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 14:53

Message:
same failure on "ruby 1.9.2p136 (2010-12-25) [i386-mingw32]" 
upgraded from RG 1.3.7 to RG 1.5.0

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-03 19:13

Message:
similar failure and working "fix" on Arch using:

ruby 1.9.3dev (2011-02-04 trunk 30776) [i686-linux]

RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.3 (2011-02-04 patchlevel -1) [i686-
linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.9.1
     - /home/jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", 
"http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

From noreply at rubyforge.org  Fri Feb 25 14:14:04 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 25 Feb 2011 14:14:04 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-29034 ] undefined
	class/module YAML::PrivateType
Message-ID: <20110225191404.C6D531678329@rubyforge.org>

Bugs item #29034, was opened at 2011-02-25 10:17
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

Category: `gem install` command (extensions)
Group: v1.5.x
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Adri?n De la Cruz (lobo_tuerto)
Assigned to: Nobody (None)
Summary: undefined class/module YAML::PrivateType

Initial Comment:
I'm on Ubuntu 10.10, using rvm and just upgraded (yesterday) rubygems from 1.5.0 to 1.5.2.

Now I'm getting this strange error whenever I try to install my recently released gems (with Jeweler).

I have two cases: missile-command-ruby and lotu.


========= missile-command-ruby =========

$ gem install missile-command-ruby
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

Even a local rake install gives:

$ rake install
(in /home/oewolf/development/gamedev/github/missile-command-ruby)
  Successfully built RubyGem
  Name: missile-command-ruby
  Version: 0.0.6
  File: missile-command-ruby-0.0.6.gem
Executing "ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem":
ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType
rake aborted!
Command failed with status (1): [ruby -S gem install ./pkg/missile-command-...]


========= lotu =========

$ gem install lotu
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

$ rake install
(in /home/oewolf/development/gamedev/github/lotu)
  Successfully built RubyGem
  Name: lotu
  Version: 0.1.17
  File: lotu-0.1.17.gem
Executing "ruby -S gem install ./pkg/lotu-0.1.17.gem":
ruby -S gem install ./pkg/lotu-0.1.17.gem
Successfully installed lotu-0.1.17
1 gem installed
Installing ri documentation for lotu-0.1.17...
Installing RDoc documentation for lotu-0.1.17...



The last one install successfully via rake install... weird.

Any help regarding this? if you need more info just post it in a follow up.


----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 11:30

Message:
UPDATE

It's all working now after re-releasing the gems.
Seems like the last release was done with 1.5.0, then 
upgraded to 1.5.2 and that's when the problems appeared.

They are gone now, thank you. ;)

----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 10:59

Message:
Output of gem install with debug info:


$ gem install lotu --debug
Exception `NameError' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:16
3 - uninitialized constant Gem::Commands::InstallCommand
Exception `Gem::LoadError' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems.rb:861 - Could 
not find RubyGem sources (> 0.0.1)

Exception `Errno::EAGAIN' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-p136/lib/ruby/1.9.1/net/protocol.rb:135 - Resource 
temporarily unavailable - read would block
Exception `Errno::EAGAIN' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-p136/lib/ruby/1.9.1/net/protocol.rb:135 - Resource 
temporarily unavailable - read would block
Exception `ArgumentError' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:289 
- undefined class/module YAML::PrivateType
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:289:
in `load'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:289:
in `_load'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:124:i
n `load'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:124:i
n `fetch_spec'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:86:in 
`block in fetch_with_errors'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:85:in 
`map'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:85:in 
`fetch_with_errors'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.
rb:108:in `find_gems_with_sources'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.
rb:212:in `find_spec_by_name_and_version'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.
rb:244:in `install'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/commands/install_comm
and.rb:120:in `block in execute'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/commands/install_comm
and.rb:115:in `each'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/commands/install_comm
and.rb:115:in `execute'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command.rb:278:in 
`invoke'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:13
3:in `process_args'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:10
3:in `run'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/gem_runner.rb:63:in 
`run'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/bin/gem:21:in `<main>'


----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 10:56

Message:
Related info:

http://www.mail-archive.com/rubygems-
developers at rubyforge.org/msg04392.html

http://comments.gmane.org/gmane.comp.lang.ruby.general/33536
9

http://help.rubygems.org/discussions/problems/483-gems-
built-with-rubygems-150-ruby-192-do-not-install-properly-
with-150-187

=======================================
Here is my gem env:

$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.2
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-
linux]
  - INSTALLATION DIRECTORY: /home/oewolf/.rvm/gems/ruby-
1.9.2-p136
  - RUBY EXECUTABLE: /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/oewolf/.rvm/gems/ruby-1.9.2-
p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-linux
  - GEM PATHS:
     - /home/oewolf/.rvm/gems/ruby-1.9.2-p136
     - /home/oewolf/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 10:38

Message:
Ruby version: ruby-1.9.2-p136 (managed with rvm)

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

From noreply at rubyforge.org  Fri Feb 25 14:38:01 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 25 Feb 2011 14:38:01 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28907 ] [RG 1.5.0/Ruby 1.9.x]
	source gem build error due to syck?
Message-ID: <20110225193801.BE67D1678329@rubyforge.org>

Bugs item #28907, was opened at 2011-02-03 10:59
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

Category: `gem` commands (other)
Group: v1.5.x
>Status: Open
>Resolution: Accepted
Priority: 3
Submitted By: Jon Forums (jonforums)
Assigned to: Eric Hodel (drbrain)
Summary: [RG 1.5.0/Ruby 1.9.x] source gem build error due to syck?

Initial Comment:
When building a source gem from http://github.com/oopsforge/oops-null using 'rake gem' I get the following error on Win7 with:

  * ruby 1.9.2p174 (2011-01-28 revision 30696) [i386-mingw32]
  * ruby 1.9.3dev (2011-02-04 trunk 30776) [i386-mingw32]

but no errors using "ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32]".  

Manually building via 'gem build oops-null.gemspec' work fine on all the Ruby versions including JRuby 1.6.0.RC1.  All versions have been upgraded to RG 1.5.0 via "gem update --system".

FWIW, the failure does not occur on "ruby 1.9.2 (2010-12-25 patchlevel 136) [i386-mingw32]" using RG 1.3.7

My "fix" was to add the following lines to the project Rakefile after the 3 require's:

require 'yaml'
YAML::ENGINE.yamler='psych' if defined?(YAML::ENGINE)

I will try to replicate on my Arch system later this afternoon.

Reproducible?

Jon


== ERROR ==

C:\projects\oops-null-git>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.2 (2011-01-28 patchlevel 174) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/Users/Jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", "http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org


C:\projects\oops-null-git>rake gem
(in C:/projects/oops-null-git)
mkdir -p pkg
mkdir -p pkg
mkdir -p pkg/oops-null-0.3.0/bin
rm -f pkg/oops-null-0.3.0/bin/nulloops
ln bin/nulloops pkg/oops-null-0.3.0/bin/nulloops
rm -f pkg/oops-null-0.3.0/Rakefile
ln Rakefile pkg/oops-null-0.3.0/Rakefile
rm -f pkg/oops-null-0.3.0/oops-null.gemspec
ln oops-null.gemspec pkg/oops-null-0.3.0/oops-null.gemspec
mkdir -p pkg/oops-null-0.3.0/ext/oops_null
rm -f pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
ln ext/oops_null/extconf.rb pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
ln ext/oops_null/oops_null.c pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
ln ext/oops_null/oops_null.h pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
mkdir -p pkg/oops-null-0.3.0/lib
rm -f pkg/oops-null-0.3.0/lib/oops-null.rb
ln lib/oops-null.rb pkg/oops-null-0.3.0/lib/oops-null.rb
cd pkg/oops-null-0.3.0
rake aborted!
undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
C:/ruby192/lib/ruby/1.9.1/psych.rb:166:in `dump'
C:/ruby192/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block (2 levels) in to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `map'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `block in to_yaml'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `call'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `emit'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:725:in `to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1157:in `when_writing'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1092:in `chdir'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `call'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `block in execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:595:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:605:in `block in invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:594:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:581:in `invoke'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2041:in `invoke_task'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block (2 levels) in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2013:in `top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1992:in `run'
C:/ruby192/bin/rake:31:in `<main>'

----------------------------------------------------------------------

>Comment By: Ryan Davis (zenspider)
Date: 2011-02-25 11:38

Message:
So, to be clear, if psych is used to create a gemspec with a version specifier using "=", and the gem is subsequently loaded using syck, this error will occur.

This is a bug in syck.

Our workaround is to look up the parsed value and if it looks up nil, fall back on a manual "=". We should backport this fix into the 1.5 line.

Eric. I'll leave the backport to you.

----------------------------------------------------------------------

Comment By: Roger Pack (rogerdpack)
Date: 2011-02-25 10:24

Message:
Just got this with jeweler, too, FYI.

https://gist.github.com/844237

----------------------------------------------------------------------

Comment By: Leonard Chin (lchin)
Date: 2011-02-09 23:37

Message:
The same error occurs with hoe

Using RubyGems at commit 182bcaf7bd4f77493794 with Ruby 1.9.2-p136
https://github.com/rubygems/rubygems/tree/182bcaf7bd4f77493794d216ac37aa9935655943

rake package --trace
(in /Users/lchin/Downloads/buggy)
** Invoke package (first_time)
** Invoke pkg/buggy-1.0.0.tgz (first_time, not_needed)
** Invoke pkg/buggy-1.0.0 (first_time, not_needed)
** Invoke .autotest (first_time, not_needed)
** Invoke History.txt (first_time, not_needed)
** Invoke Manifest.txt (first_time, not_needed)
** Invoke README.txt (first_time, not_needed)
** Invoke Rakefile (first_time, not_needed)
** Invoke bin/buggy (first_time, not_needed)
** Invoke lib/buggy.rb (first_time, not_needed)
** Invoke test/test_buggy.rb (first_time, not_needed)
** Invoke .autotest (not_needed)
** Invoke History.txt (not_needed)
** Invoke Manifest.txt (not_needed)
** Invoke README.txt (not_needed)
** Invoke Rakefile (not_needed)
** Invoke bin/buggy (not_needed)
** Invoke lib/buggy.rb (not_needed)
** Invoke test/test_buggy.rb (not_needed)
** Invoke gem (first_time)
** Invoke pkg/buggy-1.0.0.gem (first_time)
** Invoke pkg (first_time, not_needed)
** Invoke pkg/buggy-1.0.0 (not_needed)
** Invoke .autotest (not_needed)
** Invoke History.txt (not_needed)
** Invoke Manifest.txt (not_needed)
** Invoke README.txt (not_needed)
** Invoke Rakefile (not_needed)
** Invoke bin/buggy (not_needed)
** Invoke lib/buggy.rb (not_needed)
** Invoke test/test_buggy.rb (not_needed)
** Execute pkg/buggy-1.0.0.gem
cd pkg/buggy-1.0.0
WARNING:  description and summary are identical
rake aborted!
undefined method `write' for #<Syck::Emitter:0x00000100919d48>
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych.rb:166:in `dump'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:728:in `block (2 levels) in to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `map'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block in to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/syck.rb:401:in `call'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/syck.rb:401:in `emit'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:1159:in `when_writing'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:1094:in `chdir'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:636:in `call'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:636:in `block in execute'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:631:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:597:in `block in invoke_with_call_chain'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:607:in `block in invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:596:in `block in invoke_with_call_chain'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:607:in `block in invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:596:in `block in invoke_with_call_chain'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2029:in `block (2 levels) in top_level'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2029:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2029:in `block in top_level'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2001:in `block in run'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/bin/rake:31:in `<top (required)>'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/bin/rake:19:in `load'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/bin/rake:19:in `<main>'

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-05 14:00

Message:
All OK now with the updated rake-compiler.

So I'm clear, this is the main commit to pay attention to?

https://github.com/rubygems/rubygems/commit/67f9f760c782142d9bfd8099750274ba498d6682

Given the simple tweak to rake-compiler, is your
recommendation that other gems requiring yaml also prefer
psych when running on 1.9.2+ and RG 1.5.0+

FWIW, I personally like the idea of preferring psych, but
would like to have first seen it mentioned in one of the
following rather than in a bt:

http://blog.segment7.net/2011/01/31/rubygems-1-5

https://github.com/rubygems/rubygems/blob/master/UPGRADING.rdoc 

Jon

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 15:37

Message:
Yes, you are loading syck (require 'yaml') before psych (require 'psych'):

https://github.com/luislavena/rake-compiler/blob/master/lib/rake/baseextensiontask.rb

This is not supported.

A patch will be sent to rake-compiler.

You can work around this by requiring psych before rake-compiler.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 13:01

Message:
That's not the issue, sorry I wasn't clear.  I'm not mixing 
syck or psyck in the same ruby in my code.

My original Rakefile https://github.com/oopsforge/oops-
null/blob/master/Rakefile that worked pre-1.5.0 didn't 
explicitly require 'yaml' or the YAML::ENGINE.yamler= 
nonsense.

I added these lines to get the gem to build when I saw the 
error message

undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in 
`end_document'
...

..as I guessed that explicitly setting the YAML engine to 
psych would prevent syck from being visited/wrapped by 
psych.

I think something's changed in RG 1.5.0 and/or ruby_1_9_2 or 
trunk that's causing the problem. I wanted to dig into how 
psych was visiting/wrapping syck but ran out of time. I also 
did a quick look through rake-compiler and don't think it's 
to blame.

Given that my original Rakefile fails on Win7 MRI 1.9.2-
p174, 1.9.2-p136, 1.9.3dev and Arch 1.9.3dev when using RG 
1.5.0 I still think the problem is in RG.

Hopefully I explained it more clearly this time.

Would you take one more look at that long back trace and see 
if you change your mind on the issue?

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 12:33

Message:
Do not mix syck (require 'yaml') and psych (require 'psych') in the same ruby.

RubyGems uses psych on ruby 1.9.2 and newer as syck is deprecated and will be removed at a future date.  Please update your Rakefile to match.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 06:53

Message:
same failure on "ruby 1.9.2p136 (2010-12-25) [i386-mingw32]" 
upgraded from RG 1.3.7 to RG 1.5.0

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-03 11:13

Message:
similar failure and working "fix" on Arch using:

ruby 1.9.3dev (2011-02-04 trunk 30776) [i686-linux]

RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.3 (2011-02-04 patchlevel -1) [i686-
linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.9.1
     - /home/jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", 
"http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

From noreply at rubyforge.org  Fri Feb 25 14:44:11 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 25 Feb 2011 14:44:11 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-29034 ] undefined
	class/module YAML::PrivateType
Message-ID: <20110225194412.02BE81858357@rubyforge.org>

Bugs item #29034, was opened at 2011-02-25 08:17
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

Category: `gem install` command (extensions)
Group: v1.5.x
Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: Adri?n De la Cruz (lobo_tuerto)
Assigned to: Nobody (None)
Summary: undefined class/module YAML::PrivateType

Initial Comment:
I'm on Ubuntu 10.10, using rvm and just upgraded (yesterday) rubygems from 1.5.0 to 1.5.2.

Now I'm getting this strange error whenever I try to install my recently released gems (with Jeweler).

I have two cases: missile-command-ruby and lotu.


========= missile-command-ruby =========

$ gem install missile-command-ruby
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

Even a local rake install gives:

$ rake install
(in /home/oewolf/development/gamedev/github/missile-command-ruby)
  Successfully built RubyGem
  Name: missile-command-ruby
  Version: 0.0.6
  File: missile-command-ruby-0.0.6.gem
Executing "ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem":
ruby -S gem install ./pkg/missile-command-ruby-0.0.6.gem
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType
rake aborted!
Command failed with status (1): [ruby -S gem install ./pkg/missile-command-...]


========= lotu =========

$ gem install lotu
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType

$ rake install
(in /home/oewolf/development/gamedev/github/lotu)
  Successfully built RubyGem
  Name: lotu
  Version: 0.1.17
  File: lotu-0.1.17.gem
Executing "ruby -S gem install ./pkg/lotu-0.1.17.gem":
ruby -S gem install ./pkg/lotu-0.1.17.gem
Successfully installed lotu-0.1.17
1 gem installed
Installing ri documentation for lotu-0.1.17...
Installing RDoc documentation for lotu-0.1.17...



The last one install successfully via rake install... weird.

Any help regarding this? if you need more info just post it in a follow up.


----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-25 11:44

Message:
YAML compatibility between psych and syck is not perfect.  1.5.2 had fixes to address this issue.

----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 09:30

Message:
UPDATE

It's all working now after re-releasing the gems.
Seems like the last release was done with 1.5.0, then 
upgraded to 1.5.2 and that's when the problems appeared.

They are gone now, thank you. ;)

----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 08:59

Message:
Output of gem install with debug info:


$ gem install lotu --debug
Exception `NameError' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:16
3 - uninitialized constant Gem::Commands::InstallCommand
Exception `Gem::LoadError' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems.rb:861 - Could 
not find RubyGem sources (> 0.0.1)

Exception `Errno::EAGAIN' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-p136/lib/ruby/1.9.1/net/protocol.rb:135 - Resource 
temporarily unavailable - read would block
Exception `Errno::EAGAIN' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-p136/lib/ruby/1.9.1/net/protocol.rb:135 - Resource 
temporarily unavailable - read would block
Exception `ArgumentError' at /home/oewolf/.rvm/rubies/ruby-
1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:289 
- undefined class/module YAML::PrivateType
ERROR:  While executing gem ... (ArgumentError)
    undefined class/module YAML::PrivateType
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:289:
in `load'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:289:
in `_load'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:124:i
n `load'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:124:i
n `fetch_spec'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:86:in 
`block in fetch_with_errors'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:85:in 
`map'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb:85:in 
`fetch_with_errors'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.
rb:108:in `find_gems_with_sources'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.
rb:212:in `find_spec_by_name_and_version'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/dependency_installer.
rb:244:in `install'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/commands/install_comm
and.rb:120:in `block in execute'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/commands/install_comm
and.rb:115:in `each'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/commands/install_comm
and.rb:115:in `execute'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command.rb:278:in 
`invoke'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:13
3:in `process_args'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:10
3:in `run'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/lib/ruby/site_ruby/1.9.1/rubygems/gem_runner.rb:63:in 
`run'
        /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/bin/gem:21:in `<main>'


----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 08:56

Message:
Related info:

http://www.mail-archive.com/rubygems-
developers at rubyforge.org/msg04392.html

http://comments.gmane.org/gmane.comp.lang.ruby.general/33536
9

http://help.rubygems.org/discussions/problems/483-gems-
built-with-rubygems-150-ruby-192-do-not-install-properly-
with-150-187

=======================================
Here is my gem env:

$ gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.2
  - RUBY VERSION: 1.9.2 (2010-12-25 patchlevel 136) [x86_64-
linux]
  - INSTALLATION DIRECTORY: /home/oewolf/.rvm/gems/ruby-
1.9.2-p136
  - RUBY EXECUTABLE: /home/oewolf/.rvm/rubies/ruby-1.9.2-
p136/bin/ruby
  - EXECUTABLE DIRECTORY: /home/oewolf/.rvm/gems/ruby-1.9.2-
p136/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-linux
  - GEM PATHS:
     - /home/oewolf/.rvm/gems/ruby-1.9.2-p136
     - /home/oewolf/.rvm/gems/ruby-1.9.2-p136 at global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/


----------------------------------------------------------------------

Comment By: Adri?n De la Cruz (lobo_tuerto)
Date: 2011-02-25 08:38

Message:
Ruby version: ruby-1.9.2-p136 (managed with rvm)

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29034&group_id=126

From drbrain at segment7.net  Sat Feb 26 15:47:30 2011
From: drbrain at segment7.net (Eric Hodel)
Date: Sat, 26 Feb 2011 12:47:30 -0800
Subject: [Rubygems-developers] [ANN] RubyGems 1.5.3
Message-ID: <2BA4991C-1822-4CCB-A088-8B8A5C2D6D05@segment7.net>

rubygems-update version 1.5.3 has been released!

* <http://rubygems.org>
* <http://docs.rubygems.org>
* <http://help.rubygems.org>
* <http://github.com/rubygems>
* <http://rubyforge.org/projects/rubygems>

RubyGems is a package management framework for Ruby.

This gem is an update for the RubyGems software. You must have an
installation of RubyGems before this update can be applied.

See Gem for information on RubyGems (or `ri Gem`)

To upgrade to the latest RubyGems, run:

  $ gem update --system  # you might need to be an administrator or root

See UPGRADING.rdoc for more details and alternative instructions.

-----

If you don't have any RubyGems install, there is still the pre-gem approach to
getting software, doing it manually:

* Download from: https://rubygems.org/pages/download
* Unpack into a directory and cd there
* Install with: ruby setup.rb  # you may need admin/root privilege

For more details and other options, see:

  ruby setup.rb --help

Changes:

### 1.5.3 / 2011-02-26

NOTE:  RubyGems 1.5.0 and 1.5.1 have a broken <tt>gem update --system</tt>.

To upgrade you'll need to use the manual upgrade recipe.  Using sudo/su as
appropriate:

  $ gem install rubygems-update
  $ update_rubygems

Bug Fixes:

* Fix for a bug in Syck which causes install failures for gems packaged with
  Psych.  Bug #28965 by Aaron Patterson.


From noreply at rubyforge.org  Mon Feb 28 13:56:11 2011
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Mon, 28 Feb 2011 13:56:11 -0500 (EST)
Subject: [Rubygems-developers] [ rubygems-Bugs-28907 ] [RG 1.5.0/Ruby 1.9.x]
	source gem build error due to syck?
Message-ID: <20110228185611.EFE2E1678325@rubyforge.org>

Bugs item #28907, was opened at 2011-02-03 10:59
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126

Category: `gem` commands (other)
Group: v1.5.x
>Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: Jon Forums (jonforums)
Assigned to: Eric Hodel (drbrain)
Summary: [RG 1.5.0/Ruby 1.9.x] source gem build error due to syck?

Initial Comment:
When building a source gem from http://github.com/oopsforge/oops-null using 'rake gem' I get the following error on Win7 with:

  * ruby 1.9.2p174 (2011-01-28 revision 30696) [i386-mingw32]
  * ruby 1.9.3dev (2011-02-04 trunk 30776) [i386-mingw32]

but no errors using "ruby 1.8.7 (2010-12-23 patchlevel 330) [i386-mingw32]".  

Manually building via 'gem build oops-null.gemspec' work fine on all the Ruby versions including JRuby 1.6.0.RC1.  All versions have been upgraded to RG 1.5.0 via "gem update --system".

FWIW, the failure does not occur on "ruby 1.9.2 (2010-12-25 patchlevel 136) [i386-mingw32]" using RG 1.3.7

My "fix" was to add the following lines to the project Rakefile after the 3 require's:

require 'yaml'
YAML::ENGINE.yamler='psych' if defined?(YAML::ENGINE)

I will try to replicate on my Arch system later this afternoon.

Reproducible?

Jon


== ERROR ==

C:\projects\oops-null-git>gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.2 (2011-01-28 patchlevel 174) [i386-mingw32]
  - INSTALLATION DIRECTORY: C:/ruby192/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: C:/ruby192/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/ruby192/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mingw32
  - GEM PATHS:
     - C:/ruby192/lib/ruby/gems/1.9.1
     - C:/Users/Jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", "http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org


C:\projects\oops-null-git>rake gem
(in C:/projects/oops-null-git)
mkdir -p pkg
mkdir -p pkg
mkdir -p pkg/oops-null-0.3.0/bin
rm -f pkg/oops-null-0.3.0/bin/nulloops
ln bin/nulloops pkg/oops-null-0.3.0/bin/nulloops
rm -f pkg/oops-null-0.3.0/Rakefile
ln Rakefile pkg/oops-null-0.3.0/Rakefile
rm -f pkg/oops-null-0.3.0/oops-null.gemspec
ln oops-null.gemspec pkg/oops-null-0.3.0/oops-null.gemspec
mkdir -p pkg/oops-null-0.3.0/ext/oops_null
rm -f pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
ln ext/oops_null/extconf.rb pkg/oops-null-0.3.0/ext/oops_null/extconf.rb
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
ln ext/oops_null/oops_null.c pkg/oops-null-0.3.0/ext/oops_null/oops_null.c
rm -f pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
ln ext/oops_null/oops_null.h pkg/oops-null-0.3.0/ext/oops_null/oops_null.h
mkdir -p pkg/oops-null-0.3.0/lib
rm -f pkg/oops-null-0.3.0/lib/oops-null.rb
ln lib/oops-null.rb pkg/oops-null-0.3.0/lib/oops-null.rb
cd pkg/oops-null-0.3.0
rake aborted!
undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
C:/ruby192/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
C:/ruby192/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
C:/ruby192/lib/ruby/1.9.1/psych.rb:166:in `dump'
C:/ruby192/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block (2 levels) in to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `map'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `block in to_yaml'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `call'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `emit'
C:/ruby192/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:725:in `to_yaml'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1157:in `when_writing'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
C:/ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1092:in `chdir'
C:/ruby192/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `call'
C:/ruby192/lib/ruby/1.9.1/rake.rb:634:in `block in execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:629:in `execute'
C:/ruby192/lib/ruby/1.9.1/rake.rb:595:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:605:in `block in invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:602:in `invoke_prerequisites'
C:/ruby192/lib/ruby/1.9.1/rake.rb:594:in `block in invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
C:/ruby192/lib/ruby/1.9.1/rake.rb:588:in `invoke_with_call_chain'
C:/ruby192/lib/ruby/1.9.1/rake.rb:581:in `invoke'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2041:in `invoke_task'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block (2 levels) in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `each'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2019:in `block in top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling'
C:/ruby192/lib/ruby/1.9.1/rake.rb:2013:in `top_level'
C:/ruby192/lib/ruby/1.9.1/rake.rb:1992:in `run'
C:/ruby192/bin/rake:31:in `<main>'

----------------------------------------------------------------------

>Comment By: Eric Hodel (drbrain)
Date: 2011-02-28 10:56

Message:
Fixed by 1.5.3

----------------------------------------------------------------------

Comment By: Ryan Davis (zenspider)
Date: 2011-02-25 11:38

Message:
So, to be clear, if psych is used to create a gemspec with a version specifier using "=", and the gem is subsequently loaded using syck, this error will occur.

This is a bug in syck.

Our workaround is to look up the parsed value and if it looks up nil, fall back on a manual "=". We should backport this fix into the 1.5 line.

Eric. I'll leave the backport to you.

----------------------------------------------------------------------

Comment By: Roger Pack (rogerdpack)
Date: 2011-02-25 10:24

Message:
Just got this with jeweler, too, FYI.

https://gist.github.com/844237

----------------------------------------------------------------------

Comment By: Leonard Chin (lchin)
Date: 2011-02-09 23:37

Message:
The same error occurs with hoe

Using RubyGems at commit 182bcaf7bd4f77493794 with Ruby 1.9.2-p136
https://github.com/rubygems/rubygems/tree/182bcaf7bd4f77493794d216ac37aa9935655943

rake package --trace
(in /Users/lchin/Downloads/buggy)
** Invoke package (first_time)
** Invoke pkg/buggy-1.0.0.tgz (first_time, not_needed)
** Invoke pkg/buggy-1.0.0 (first_time, not_needed)
** Invoke .autotest (first_time, not_needed)
** Invoke History.txt (first_time, not_needed)
** Invoke Manifest.txt (first_time, not_needed)
** Invoke README.txt (first_time, not_needed)
** Invoke Rakefile (first_time, not_needed)
** Invoke bin/buggy (first_time, not_needed)
** Invoke lib/buggy.rb (first_time, not_needed)
** Invoke test/test_buggy.rb (first_time, not_needed)
** Invoke .autotest (not_needed)
** Invoke History.txt (not_needed)
** Invoke Manifest.txt (not_needed)
** Invoke README.txt (not_needed)
** Invoke Rakefile (not_needed)
** Invoke bin/buggy (not_needed)
** Invoke lib/buggy.rb (not_needed)
** Invoke test/test_buggy.rb (not_needed)
** Invoke gem (first_time)
** Invoke pkg/buggy-1.0.0.gem (first_time)
** Invoke pkg (first_time, not_needed)
** Invoke pkg/buggy-1.0.0 (not_needed)
** Invoke .autotest (not_needed)
** Invoke History.txt (not_needed)
** Invoke Manifest.txt (not_needed)
** Invoke README.txt (not_needed)
** Invoke Rakefile (not_needed)
** Invoke bin/buggy (not_needed)
** Invoke lib/buggy.rb (not_needed)
** Invoke test/test_buggy.rb (not_needed)
** Execute pkg/buggy-1.0.0.gem
cd pkg/buggy-1.0.0
WARNING:  description and summary are identical
rake aborted!
undefined method `write' for #<Syck::Emitter:0x00000100919d48>
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `end_document'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in `visit_Psych_Nodes_Document'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/visitor.rb:10:in `accept'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `block in visit_Psych_Nodes_Stream'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `each'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/emitter.rb:10:in `visit_Psych_Nodes_Stream'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/visitors/visitor.rb:11:in `accept'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/nodes/node.rb:36:in `to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych.rb:166:in `dump'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/psych/core_ext.rb:13:in `psych_to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `node_export'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `add'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:706:in `encode_with'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:728:in `block (2 levels) in to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `map'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:727:in `block in to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/syck.rb:401:in `call'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/syck.rb:401:in `emit'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/syck.rb:401:in `quick_emit'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:726:in `to_yaml'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:78:in `block (2 levels) in write_package'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:73:in `block (3 levels) in add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:83:in `new'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:67:in `block (2 levels) in add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `wrap'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:65:in `block in add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_writer.rb:113:in `add_file'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:63:in `add_gem_contents'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package/tar_output.rb:31:in `open'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package.rb:68:in `open'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:77:in `block in write_package'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `open'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:76:in `write_package'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/builder.rb:39:in `build'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:116:in `block (3 levels) in define'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:1159:in `when_writing'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:115:in `block (2 levels) in define'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/fileutils.rb:121:in `chdir'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/fileutils.rb:121:in `cd'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:1094:in `chdir'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/package_task.rb:114:in `block in define'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:636:in `call'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:636:in `block in execute'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:631:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:597:in `block in invoke_with_call_chain'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:607:in `block in invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:596:in `block in invoke_with_call_chain'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:607:in `block in invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:596:in `block in invoke_with_call_chain'
/Users/lchin/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2029:in `block (2 levels) in top_level'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2029:in `each'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2029:in `block in top_level'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2001:in `block in run'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/gems/rake-0.8.7/bin/rake:31:in `<top (required)>'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/bin/rake:19:in `load'
/Users/lchin/.rvm/gems/ruby-1.9.2-p136 at global/bin/rake:19:in `<main>'

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-05 14:00

Message:
All OK now with the updated rake-compiler.

So I'm clear, this is the main commit to pay attention to?

https://github.com/rubygems/rubygems/commit/67f9f760c782142d9bfd8099750274ba498d6682

Given the simple tweak to rake-compiler, is your
recommendation that other gems requiring yaml also prefer
psych when running on 1.9.2+ and RG 1.5.0+

FWIW, I personally like the idea of preferring psych, but
would like to have first seen it mentioned in one of the
following rather than in a bt:

http://blog.segment7.net/2011/01/31/rubygems-1-5

https://github.com/rubygems/rubygems/blob/master/UPGRADING.rdoc 

Jon

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 15:37

Message:
Yes, you are loading syck (require 'yaml') before psych (require 'psych'):

https://github.com/luislavena/rake-compiler/blob/master/lib/rake/baseextensiontask.rb

This is not supported.

A patch will be sent to rake-compiler.

You can work around this by requiring psych before rake-compiler.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 13:01

Message:
That's not the issue, sorry I wasn't clear.  I'm not mixing 
syck or psyck in the same ruby in my code.

My original Rakefile https://github.com/oopsforge/oops-
null/blob/master/Rakefile that worked pre-1.5.0 didn't 
explicitly require 'yaml' or the YAML::ENGINE.yamler= 
nonsense.

I added these lines to get the gem to build when I saw the 
error message

undefined method `write' for #<Syck::Emitter:0x22bd9e0>
C:/ruby192/lib/ruby/1.9.1/psych/visitors/emitter.rb:17:in 
`end_document'
...

..as I guessed that explicitly setting the YAML engine to 
psych would prevent syck from being visited/wrapped by 
psych.

I think something's changed in RG 1.5.0 and/or ruby_1_9_2 or 
trunk that's causing the problem. I wanted to dig into how 
psych was visiting/wrapping syck but ran out of time. I also 
did a quick look through rake-compiler and don't think it's 
to blame.

Given that my original Rakefile fails on Win7 MRI 1.9.2-
p174, 1.9.2-p136, 1.9.3dev and Arch 1.9.3dev when using RG 
1.5.0 I still think the problem is in RG.

Hopefully I explained it more clearly this time.

Would you take one more look at that long back trace and see 
if you change your mind on the issue?

----------------------------------------------------------------------

Comment By: Eric Hodel (drbrain)
Date: 2011-02-04 12:33

Message:
Do not mix syck (require 'yaml') and psych (require 'psych') in the same ruby.

RubyGems uses psych on ruby 1.9.2 and newer as syck is deprecated and will be removed at a future date.  Please update your Rakefile to match.

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-04 06:53

Message:
same failure on "ruby 1.9.2p136 (2010-12-25) [i386-mingw32]" 
upgraded from RG 1.3.7 to RG 1.5.0

----------------------------------------------------------------------

Comment By: Jon Forums (jonforums)
Date: 2011-02-03 11:13

Message:
similar failure and working "fix" on Arch using:

ruby 1.9.3dev (2011-02-04 trunk 30776) [i686-linux]

RubyGems Environment:
  - RUBYGEMS VERSION: 1.5.0
  - RUBY VERSION: 1.9.3 (2011-02-04 patchlevel -1) [i686-
linux]
  - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: /usr/local/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/local/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-linux
  - GEM PATHS:
     - /usr/local/lib/ruby/gems/1.9.1
     - /home/jon/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["http://rubygems.org", 
"http://gemcutter.org"]
     - "gem" => "--no-ri --no-rdoc"
  - REMOTE SOURCES:
     - http://rubygems.org
     - http://gemcutter.org

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28907&group_id=126