[Rubygems-developers] Warning: Don't upload gems made with the beta yet
nakahiro at sarion.co.jp
Sun Oct 28 21:40:16 EDT 2007
-----BEGIN PGP SIGNED MESSAGE-----
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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
-----END PGP SIGNATURE-----
More information about the Rubygems-developers