[Rubygems-developers] Warning: Don't upload gems made with the beta yet

NAKAMURA, Hiroshi nakahiro at sarion.co.jp
Sun Oct 28 21:40:16 EDT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I'm not the person who should ask it.  I was just curious...

Tom Copeland wrote:
>>> $ gem list --remote rails
>>> *** REMOTE GEMS ***
>>> Bulk updating Gem source index for: http://gems.rubyforge.org
>>> ERROR:  While executing gem ... (TypeError) can't instantiate 
>>> uninitialized class
>>>
>>> I've deleted the gems and Tom is recreating the index as I write this.
>>>
>>> Just shoot me.
>> Actually, maybe it's my fault - Eric, I'm using the indexer from a
>> RubyGems trunk checkout from a few weeks ago; if I do an "svn up" will
>> that help?
> 
> In the meantime, I've disabled gem index rebuilds on RubyForge, so no
> new gems will be deployed there until we sort this out.  That way at
> least the current index will stay up...

Still have the problem?  Can you show me an actual gem of win32-api and
the gems index that caused the problem?

I created a soap4r gem and gems index with svn trunk (0.9.4.6?) but I
can install it with 0.9.4.  On the machine that uses 0.9.4, loading the
Marshal index 'Marshal.4.8' caused an error but I think source_index.rb
in 0.9.4 doesn't try to fetch the Marshal gem index.  And the error I
got is different from the one Dan got.  How I can get the TypeError above?

I've just gave a quick look on source so I may be wrong.

Regards,
// NaHi

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)

iQEVAwUBRyU5/x9L2jg5EEGlAQKWpgf/cteKve3B8gQIt8SK3Qn5f7cGT705/UOC
nfWbxT/ji8AafG648tkB3p6vc4f6Je/ib+eVBb3BqXOhfg45BgnhdPNqYThJbh7a
ahOvWdR884hMf96ew1WpblNX9uZ9D37LW40UumKOjfBmndjNFpidwCMXdRZJdOQS
Bt8W9YWUY2FgfAYUkj5Vlp7oKn/Gq1pNtG8Fyx0WZhL6Q7UFwhLli9p4TKrmTy/H
2E3N/Ud34x13JxBd+qH7Xlf7mmo/wnpInbHbHQMlHLd+reo56H0ynaoOvzx3XSP9
Y0v9MMYs3qKlleIEkyf9cJ4e0ObOKGyn8fm48sxdsJBF3ibCYqQ5Bw==
=07Bz
-----END PGP SIGNATURE-----


More information about the Rubygems-developers mailing list