On Jun 24, 2008, at 21:26 , Chad Woolley wrote:
On Tue, Jun 24, 2008 at 4:08 PM, Ryan Davis <ryand-
[EMAIL PROTECTED]> wrote:
you and I are already caught up, but for the record: 0.4.3 was
fixed but
0.4.2 still has the same problem. 0.4.2 was deleted but that doesn't
replicate so it should be rereleased as well (unless we can find
tom online)
OK, I just re-released from my 0.4.2 tag, packaged with RubyGems
1.2.0 release.
I still am not sure how to reproduce this error, can you confirm or
tell me how to check?
gah... lame. I have no idea what's wrong now:
502 % sudo gem sources -c; sudo gem update --system --debug; gem -v
Password:
*** Removed user source cache ***
*** Removed latest user source cache ***
*** Removed system source cache ***
*** Removed latest system source cache ***
Exception `NameError' at /Library/Ruby/Site/1.8/rubygems/
command_manager.rb:133 - uninitialized constant
Gem::Commands::UpdateCommand
Updating RubyGems
Exception `Errno::ENOENT' at /Library/Ruby/Site/1.8/rubygems/
source_info_cache.rb:206 - No such file or directory - /Library/Ruby/
Gems/1.8/latest_source_cache
Bulk updating Gem source index for: http://gems.rubyforge.org/
Nothing to update
1.1.1
_______________________________________________
Rubygems-developers mailing list
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
