`gem cert --add` error
FileUtils appears not being required during gem cert
--add command:
Exception `NameError' at /Library/Ruby/Site/1.8/rubygems/command_manager.rb:163 - uninitialized constant Gem::Commands::CertCommand
Exception `NameError' at /Library/Ruby/Site/1.8/rubygems/security.rb:665 - uninitialized constant Gem::Security::FileUtils
ERROR: While executing gem ... (NameError)
uninitialized constant Gem::Security::FileUtils
/Library/Ruby/Site/1.8/rubygems/security.rb:665:in `verify_trust_dir'
/Library/Ruby/Site/1.8/rubygems/security.rb:770:in `add_trusted_cert'
/Library/Ruby/Site/1.8/rubygems/commands/cert_command.rb:12:in `initialize'
/Library/Ruby/Site/1.8/rubygems/command.rb:443:in `call'
/Library/Ruby/Site/1.8/rubygems/command.rb:443:in `configure_options'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1267:in `call'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1267:in `parse_in_order'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1254:in `catch'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1254:in `parse_in_order'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1248:in `order!'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1339:in `permute!'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1360:in `parse!'
/Library/Ruby/Site/1.8/rubygems/command.rb:348:in `handle_options'
/Library/Ruby/Site/1.8/rubygems/command.rb:271:in `invoke'
/Library/Ruby/Site/1.8/rubygems/command_manager.rb:133:in `process_args'
/Library/Ruby/Site/1.8/rubygems/command_manager.rb:103:in `run'
/Library/Ruby/Site/1.8/rubygems/gem_runner.rb:63:in `run'
/usr/bin/gem:21
Comments are currently closed for this discussion. You can start a new one.
2 Posted by robert.slifka on 26 Feb, 2011 08:35 PM
Interesting coincidence - same problem here within 12 hours :)
slif:~$ gem cert --build email_address
ERROR: While executing gem ... (NameError)
On RubyGems 1.5.2.
Support Staff 3 Posted by Eric Hodel on 26 Feb, 2011 09:02 PM
Fixed in trunk, will be in 1.6.0
Eric Hodel closed this discussion on 26 Feb, 2011 09:02 PM.
robert.slifka re-opened this discussion on 26 Feb, 2011 09:33 PM
4 Posted by robert.slifka on 26 Feb, 2011 09:33 PM
FYI, just downgrade to 1.3.3 conduct your business then upgrade :)
Support Staff 5 Posted by Eric Hodel on 26 Feb, 2011 10:51 PM
You should be able to work around this with
ruby -rfileutils -S gem cert …Eric Hodel closed this discussion on 26 Feb, 2011 10:51 PM.