From hgs at dmu.ac.uk Thu Apr 1 04:55:21 2010 From: hgs at dmu.ac.uk (Hugh Sasse) Date: Thu, 1 Apr 2010 09:55:21 +0100 (BST) Subject: [Rubygems-developers] Rubygems Packaging Enhancements and Designs In-Reply-To: <90CA14FE-2377-436B-9670-117FCAB4429A@zenspider.com> References: <38F0B358-9035-4691-8D1A-DE82AB60AC0D@gmail.com> <87807826-397A-4FEB-B619-408C208B1B36@gmail.com> <90CA14FE-2377-436B-9670-117FCAB4429A@zenspider.com> Message-ID: On Wed, 31 Mar 2010, Ryan Davis wrote: > > On Mar 31, 2010, at 17:15 , Hugh Sasse wrote: > > > (Pessamistic version control), and that is the flow of the text > > suggests that a couple of examples would fit nicely at the end: > > > > "~> 2.7.1.8" => ">= 2.7.1.8", "< 2.7.2" > > "~> 2.7.1" => ">= 2.7.1", "< 2.8" > > I just modified the last paragraph to read: > > Notice that we only include 2 digits of the version. The operator will drop the final digit of a version, then increment the remaining final digit to get the upper limit version number. Therefore ?~> 2.2? is equivalent to: [?>= 2.2?, ?< 3.0?]. Had we said ?~> 2.2.0?, it would have been equivalent to: [?>= 2.2.0?, ?< 2.3.0?]. The last digit specifies the level of granularity of version control. (Remember, you can alway supply an explicit upper limit if the pessimistic operator is too limited for you). > > Edits welcome. Thank you, that's even better. Hugh From noreply at rubyforge.org Sat Apr 3 08:54:25 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 3 Apr 2010 08:54:25 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28049 ] GEM_HOME or XDG_CACHE_HOME should be used instead of $HOME/.gem Message-ID: <20100403125425.B7CBB18582E3@rubyforge.org> Bugs item #28049, was opened at 2010-04-03 12:54 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28049&group_id=126 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Gioele Barabucci (gioele) Assigned to: Nobody (None) Summary: GEM_HOME or XDG_CACHE_HOME should be used instead of $HOME/.gem Initial Comment: The last few versions of rubygems started using the ~/.gem/ directory, cluttering the $HOME directory. The files currently found in ~/.gem/ should be placed somewhere under the $GEM_HOME directory (if specified). Otherwise, those files could be saved in $XDG_DATA_HOME or $XDG_CONFIG_HOME as described in the XDG Base Directory Specification: . This article explains the importance of following the XDG Base Directory Specification. $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.6 - RUBY VERSION: 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux] - INSTALLATION DIRECTORY: /home/gioele/foo_bar/ruby/gems - RUBYGEMS PREFIX: /home/gioele/foo_bar/ruby - RUBY EXECUTABLE: /usr/bin/ruby1.8 - EXECUTABLE DIRECTORY: /home/gioele/foo_bar/ruby/gems/bin - RUBYGEMS PLATFORMS: - ruby - x86_64-linux - GEM PATHS: - /home/gioele/foo_bar/ruby/gems - /home/gioele/.gem/ruby/1.8 - /usr/lib/ruby/gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://gems.rubyforge.org/"] - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28049&group_id=126 From noreply at rubyforge.org Sat Apr 3 12:08:08 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 3 Apr 2010 12:08:08 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Patches-28050 ] speed up proxy executables in Ruby 1.9 Message-ID: <20100403160808.8EF6018582CE@rubyforge.org> Patches item #28050, was opened at 2010-04-03 09:08 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=28050&group_id=126 Category: `gem install` Group: None Status: Open Resolution: None Priority: 3 Submitted By: Suraj Kurapati (snk) Assigned to: Nobody (None) Summary: speed up proxy executables in Ruby 1.9 Initial Comment: Hello, I am using RubyGems 1.3.6 with Ruby 1.9.1p378. I consistently observe a huge time overhead when running proxy executables (installed by RubyGems in /usr/bin/) in comparison to directly running the underlying executables provided by gems in their bin/ directory. The attached tarball serves to demonstrate this observation: # tar zxf rubygems-fast-proxy-executable.tgz # cd rubygems-fast-proxy-executable/ # tree -F . ??? bin/ ? ??? foobarbaz* ??? foobarbaz.gemspec 1 directory, 2 files # cat bin/foobarbaz #!/usr/bin/env ruby puts __FILE__ # cat foobarbaz.gemspec spec = Gem::Specification.new do |s| s.name = 'foobarbaz' s.version = '0.0.0' s.summary = 'make rubygems proxy executables fast!' s.executables = s.name s.files = "bin/#{s.name}" end # gem build foobarbaz.gemspec WARNING: no author specified WARNING: no description specified WARNING: no email specified WARNING: no homepage specified WARNING: no rubyforge_project specified Successfully built RubyGem Name: foobarbaz Version: 0.0.0 File: foobarbaz-0.0.0.gem # sudo gem install foobarbaz-0.0.0.gem Successfully installed foobarbaz-0.0.0 1 gem installed # which foobarbaz /usr/bin/foobarbaz # time foobarbaz /usr/lib/ruby/gems/1.9.1/gems/foobarbaz-0.0.0/bin/foobarbaz real 0m1.926s user 0m1.730s sys 0m0.180s # time ./bin/foobarbaz ./bin/foobarbaz real 0m0.050s user 0m0.043s sys 0m0.007s In Ruby 1.9, the $LOAD_PATH is already pre-seeded with the bin/ and lib/ directories of all gems installed in the environment, so the proxy executable (such as /usr/bin/foobarbaz) could be reduced to the following: #!/usr/bin/ruby # # This file was generated by RubyGems. # # The application 'foobarbaz' is installed as part of a gem, and # this file is here to facilitate running it. # require 'rubygems' version = [] if ARGV.first =~ /^_(.+)_$/ and Gem::Version.correct? $1 then version << $1 ARGV.shift end if RUBY_VERSION < '1.9' or not version.empty? then gem 'foobarbaz', *version end load 'foobarbaz' After making this change, the runtime overhead of the RubyGems proxy executable is greatly reduced: # time foobarbaz /usr/lib/ruby/gems/1.9.1/gems/foobarbaz-0.0.0/bin/foobarbaz real 0m0.054s user 0m0.043s sys 0m0.010s However, I do not observe any improvement (or degradation) in performance after trying these changes in Ruby 1.8: # time ~/.multiruby/install/1.8.6-p383/bin/foobarbaz /home/sun/.multiruby/install/1.8.6-p383/lib/ruby/gems/1.8/gems/foobarbaz-0.0.0/bin/foobarbaz real 0m0.157s user 0m0.130s sys 0m0.027s Since this change does not negatively affect Ruby 1.8, I say let's do it and make RubyGems proxy executables *super fast* in Ruby 1.9! Thanks for your consideration. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=28050&group_id=126 From noreply at rubyforge.org Tue Apr 6 07:41:58 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 6 Apr 2010 07:41:58 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27868 ] rubygems 1.3.6 isn't compatible with rails 2.2.2 Message-ID: <20100406114158.A6403159802A@rubyforge.org> Bugs item #27868, was opened at 2010-02-22 14:08 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27868&group_id=126 Category: other Group: v1.3.x Status: Open Resolution: Accepted Priority: 3 Submitted By: Wei Jen Lu (weijenlu) Assigned to: Eric Hodel (drbrain) Summary: rubygems 1.3.6 isn't compatible with rails 2.2.2 Initial Comment: I updated rubygems to 1.3.6 and run my app which using rails 2.2.2. My app has exception: /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/gem_dependency.rb:224:in `specification': undefined method `version_requirements=' for # (NoMethodError) from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `inject' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `each' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `inject' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:63:in `locate_plugins' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `map' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `locate_plugins' ... 34 levels... from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/commands/server.rb:49 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `require' from script/server:3 If I rollback to 1.3.5, then everything is fine. Please help me. thanks. My platform: OS: Mac OS X 10.5.8 Ruby: ruby 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0] Wei Jen ---------------------------------------------------------------------- Comment By: David Gaya (myelocyte) Date: 2010-04-06 13:41 Message: I had the same problem. I had two gems with :version specified (will_paginate and rubyist-aasm). I simply removed the version dependence. < config.gem 'rubyist-aasm', :version => '~> 2.0.2', :lib => 'aasm', :source => "http://gems.github.com" > config.gem 'rubyist-aasm', :lib => 'aasm', :source => "http://gems.github.com" < config.gem 'will_paginate', :version => '~> 2.3.11', :source => 'http://gemcutter.org' > config.gem 'will_paginate' ---------------------------------------------------------------------- Comment By: Martin Fencl (arta) Date: 2010-03-22 00:11 Message: I am facing a similar problem, getting this error when running ar_sendmail: ? ~/.c (master)? $ ar_sendmail Unhandled exception undefined method `version_requirements=' for #(NoMethodError): /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/gem_dependency.rb:224:in `specification' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `inject' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `each' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `inject' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:63:in `locate_plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `map' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `locate_plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:27:in `all_plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:22:in `plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:45:in `add_plugin_load_paths' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:269:in `add_plugin_load_paths' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:135:in `process' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `send' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `run' ./config/environment.rb:19 /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/lib/action_mailer/ar_sendmail.rb:252:in `process_args' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/lib/action_mailer/ar_sendmail.rb:250:in `chdir' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/lib/action_mailer/ar_sendmail.rb:250:in `process_args' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/lib/action_mailer/ar_sendmail.rb:269:in `run' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/bin/ar_sendmail:5 /usr/local/bin/ar_sendmail:19:in `load' /usr/local/bin/ar_sendmail:19 Rolling back to rubygems 1.3.5 doesn't help, gemcutter is installed .... My setup: OSX SL, Ruby 1.8.7p174, Rails 2.2.2. I didn't have any issues with ar_sendmail before. Thanks for any help, martin ---------------------------------------------------------------------- Comment By: Thong Kuah (kuahyeow) Date: 2010-03-21 22:06 Message: I had the exact same problem where version_requirement= was broken. After getting rubygems trunk, I now get a deprecation warning "Gem::Dependency#version_requirements= is deprecated and will be removed on or after August 2010. Use Gem::Dependency.new". So that seems to have fixed it. ---------------------------------------------------------------------- Comment By: Robert Berger (rberger) Date: 2010-03-05 10:29 Message: Eric: I svn checked out trunk, and from the top dir of the checkout did sudo ruby setup.rb and then I did a ./script/console from within my 2.2.2 app and it looks like it fixes this problem. I now get a deprecated warning. It looks like the rake commands work in general. ---------------------------------------------------------------------- Comment By: Dylan Fogarty-MacDonald (dylanfm) Date: 2010-02-25 03:51 Message: I'm experiencing the exact same issue. Rubygems 1.3.6 Ruby 1.8.6 (2008-08-08 patchlevel 286) [x86_64-linux] ---------------------------------------------------------------------- Comment By: Wei Jen Lu (weijenlu) Date: 2010-02-24 09:19 Message: I found out this issue is caused by gemcutter be removed. For my system, I use authlogic 1.3.8 and it depend on gemcutter 0.3.0. When I update rubygems, the update process removed gemcutter, then this problem happened. I fixed this problem after reinstall gemcutter. ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2010-02-24 08:03 Message: I think I have this fixed in trunk, but I can't replicate it with an empty rails 2.2.2 app. Can one of you test it out? Check out RubyGems then run: ruby -I/path/to/rubygems/lib script/server or: ruby -I/path/to/rubygems/lib -S rake ---------------------------------------------------------------------- Comment By: Florent Vaucelle (florent) Date: 2010-02-23 11:44 Message: Hi, having the same issue on Fedora 9 with REE 1.8.7, rails 2.2.2 installed. undefined method `version_requirements=' for # ../vendor/rails/railties/lib/rails/gem_dependency.rb:224:in `specification' ../vendor/rails/railties/lib/rails/plugin/locator.rb:81:in `plugins' /opt/ruby-ee-1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `inject' ../vendor/rails/railties/lib/rails/plugin/locator.rb:81:in `each' ../vendor/rails/railties/lib/rails/plugin/locator.rb:81:in `inject' ../vendor/rails/railties/lib/rails/plugin/locator.rb:81:in `plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:63:in `locate_plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:62:in `map' ../vendor/rails/railties/lib/rails/plugin/loader.rb:62:in `locate_plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:27:in `all_plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:22:in `plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:45:in `add_plugin_load_paths' ../vendor/rails/railties/lib/initializer.rb:269:in `add_plugin_load_paths' ../vendor/rails/railties/lib/initializer.rb:135:in `process' ../vendor/rails/railties/lib/initializer.rb:112:in `send' ../vendor/rails/railties/lib/initializer.rb:112:in `run' environment.rb:13 /opt/ruby-ee-1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /opt/ruby-ee-1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' vendor/rails/activesupport/lib/active_support/dependencies.rb:153:in `require' vendor/rails/activesupport/lib/active_support/dependencies.rb:521:in `new_constants_in' vendor/rails/activesupport/lib/active_support/dependencies.rb:153:in `require' vendor/rails/railties/lib/tasks/misc.rake:3 /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /opt/ruby-ee-1.8.7/lib/ruby/1.8/monitor.rb:242:in `synchronize' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:607:in `invoke_prerequisites' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in `each' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:596:in `invoke_with_call_chain' /opt/ruby-ee-1.8.7/lib/ruby/1.8/monitor.rb:242:in `synchronize' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /opt/ruby-ee-1.8.7/bin/rake:19:in `load' /opt/ruby-ee-1.8.7/bin/rake:19 ---------------------------------------------------------------------- Comment By: Charles Ju (charlesju) Date: 2010-02-23 03:50 Message: I just updated to rubygems 1.3.6 and my app is on rails 2.2.2. My platform is OSX 10.6.2 and ruby at ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0]. 1.3.5 is fine undefined method `version_requirements=' for :Gem::Dependency /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/gem_dependency.rb:224:in `specification' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `inject' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `each' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `inject' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:63:in `locate_plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `map' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `locate_plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:27:in `all_plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:22:in `plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:45:in `add_plugin_load_paths' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:269:in `add_plugin_load_paths' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:135:in `process' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `send' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `run' /Users/charlesju/work/SyncManager/config/environment.rb:16 /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `require' Charles ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2010-02-23 03:04 Message: Time to vendor in rubygems? Can that be done? Dan ---------------------------------------------------------------------- Comment By: Vidal Graupera (vgraupera) Date: 2010-02-23 02:40 Message: I hit the exact same problem. My platform is OS X 10.6.2 and ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0] ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27868&group_id=126 From noreply at rubyforge.org Tue Apr 6 12:14:33 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 6 Apr 2010 12:14:33 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27868 ] rubygems 1.3.6 isn't compatible with rails 2.2.2 Message-ID: <20100406161433.C239E18582EE@rubyforge.org> Bugs item #27868, was opened at 2010-02-22 07:08 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27868&group_id=126 Category: other Group: v1.3.x Status: Open Resolution: Accepted Priority: 3 Submitted By: Wei Jen Lu (weijenlu) Assigned to: Eric Hodel (drbrain) Summary: rubygems 1.3.6 isn't compatible with rails 2.2.2 Initial Comment: I updated rubygems to 1.3.6 and run my app which using rails 2.2.2. My app has exception: /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/gem_dependency.rb:224:in `specification': undefined method `version_requirements=' for # (NoMethodError) from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `inject' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `each' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `inject' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:63:in `locate_plugins' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `map' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `locate_plugins' ... 34 levels... from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/commands/server.rb:49 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `require' from script/server:3 If I rollback to 1.3.5, then everything is fine. Please help me. thanks. My platform: OS: Mac OS X 10.5.8 Ruby: ruby 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0] Wei Jen ---------------------------------------------------------------------- Comment By: Martin Fencl (arta) Date: 2010-04-06 11:14 Message: Yes, to fix the 'version_requirements=' issue, I checked out patched rubygems (thanks to Adam Meehan, adzap-ar_mailer): svn checkout svn://rubyforge.org/var/svn/rubygems cd trunk ruby setup.rb It is version 1.3.6 and the fix comes at a price of a deprecation warning. martin ---------------------------------------------------------------------- Comment By: David Gaya (myelocyte) Date: 2010-04-06 06:41 Message: I had the same problem. I had two gems with :version specified (will_paginate and rubyist-aasm). I simply removed the version dependence. < config.gem 'rubyist-aasm', :version => '~> 2.0.2', :lib => 'aasm', :source => "http://gems.github.com" > config.gem 'rubyist-aasm', :lib => 'aasm', :source => "http://gems.github.com" < config.gem 'will_paginate', :version => '~> 2.3.11', :source => 'http://gemcutter.org' > config.gem 'will_paginate' ---------------------------------------------------------------------- Comment By: Martin Fencl (arta) Date: 2010-03-21 18:11 Message: I am facing a similar problem, getting this error when running ar_sendmail: ? ~/.c (master)? $ ar_sendmail Unhandled exception undefined method `version_requirements=' for #(NoMethodError): /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/gem_dependency.rb:224:in `specification' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `inject' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `each' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `inject' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:63:in `locate_plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `map' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `locate_plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:27:in `all_plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:22:in `plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:45:in `add_plugin_load_paths' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:269:in `add_plugin_load_paths' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:135:in `process' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `send' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `run' ./config/environment.rb:19 /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/lib/action_mailer/ar_sendmail.rb:252:in `process_args' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/lib/action_mailer/ar_sendmail.rb:250:in `chdir' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/lib/action_mailer/ar_sendmail.rb:250:in `process_args' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/lib/action_mailer/ar_sendmail.rb:269:in `run' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/bin/ar_sendmail:5 /usr/local/bin/ar_sendmail:19:in `load' /usr/local/bin/ar_sendmail:19 Rolling back to rubygems 1.3.5 doesn't help, gemcutter is installed .... My setup: OSX SL, Ruby 1.8.7p174, Rails 2.2.2. I didn't have any issues with ar_sendmail before. Thanks for any help, martin ---------------------------------------------------------------------- Comment By: Thong Kuah (kuahyeow) Date: 2010-03-21 16:06 Message: I had the exact same problem where version_requirement= was broken. After getting rubygems trunk, I now get a deprecation warning "Gem::Dependency#version_requirements= is deprecated and will be removed on or after August 2010. Use Gem::Dependency.new". So that seems to have fixed it. ---------------------------------------------------------------------- Comment By: Robert Berger (rberger) Date: 2010-03-05 03:29 Message: Eric: I svn checked out trunk, and from the top dir of the checkout did sudo ruby setup.rb and then I did a ./script/console from within my 2.2.2 app and it looks like it fixes this problem. I now get a deprecated warning. It looks like the rake commands work in general. ---------------------------------------------------------------------- Comment By: Dylan Fogarty-MacDonald (dylanfm) Date: 2010-02-24 20:51 Message: I'm experiencing the exact same issue. Rubygems 1.3.6 Ruby 1.8.6 (2008-08-08 patchlevel 286) [x86_64-linux] ---------------------------------------------------------------------- Comment By: Wei Jen Lu (weijenlu) Date: 2010-02-24 02:19 Message: I found out this issue is caused by gemcutter be removed. For my system, I use authlogic 1.3.8 and it depend on gemcutter 0.3.0. When I update rubygems, the update process removed gemcutter, then this problem happened. I fixed this problem after reinstall gemcutter. ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2010-02-24 01:03 Message: I think I have this fixed in trunk, but I can't replicate it with an empty rails 2.2.2 app. Can one of you test it out? Check out RubyGems then run: ruby -I/path/to/rubygems/lib script/server or: ruby -I/path/to/rubygems/lib -S rake ---------------------------------------------------------------------- Comment By: Florent Vaucelle (florent) Date: 2010-02-23 04:44 Message: Hi, having the same issue on Fedora 9 with REE 1.8.7, rails 2.2.2 installed. undefined method `version_requirements=' for # ../vendor/rails/railties/lib/rails/gem_dependency.rb:224:in `specification' ../vendor/rails/railties/lib/rails/plugin/locator.rb:81:in `plugins' /opt/ruby-ee-1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `inject' ../vendor/rails/railties/lib/rails/plugin/locator.rb:81:in `each' ../vendor/rails/railties/lib/rails/plugin/locator.rb:81:in `inject' ../vendor/rails/railties/lib/rails/plugin/locator.rb:81:in `plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:63:in `locate_plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:62:in `map' ../vendor/rails/railties/lib/rails/plugin/loader.rb:62:in `locate_plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:27:in `all_plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:22:in `plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:45:in `add_plugin_load_paths' ../vendor/rails/railties/lib/initializer.rb:269:in `add_plugin_load_paths' ../vendor/rails/railties/lib/initializer.rb:135:in `process' ../vendor/rails/railties/lib/initializer.rb:112:in `send' ../vendor/rails/railties/lib/initializer.rb:112:in `run' environment.rb:13 /opt/ruby-ee-1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /opt/ruby-ee-1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' vendor/rails/activesupport/lib/active_support/dependencies.rb:153:in `require' vendor/rails/activesupport/lib/active_support/dependencies.rb:521:in `new_constants_in' vendor/rails/activesupport/lib/active_support/dependencies.rb:153:in `require' vendor/rails/railties/lib/tasks/misc.rake:3 /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /opt/ruby-ee-1.8.7/lib/ruby/1.8/monitor.rb:242:in `synchronize' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:607:in `invoke_prerequisites' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in `each' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:596:in `invoke_with_call_chain' /opt/ruby-ee-1.8.7/lib/ruby/1.8/monitor.rb:242:in `synchronize' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /opt/ruby-ee-1.8.7/bin/rake:19:in `load' /opt/ruby-ee-1.8.7/bin/rake:19 ---------------------------------------------------------------------- Comment By: Charles Ju (charlesju) Date: 2010-02-22 20:50 Message: I just updated to rubygems 1.3.6 and my app is on rails 2.2.2. My platform is OSX 10.6.2 and ruby at ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0]. 1.3.5 is fine undefined method `version_requirements=' for :Gem::Dependency /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/gem_dependency.rb:224:in `specification' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `inject' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `each' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `inject' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:63:in `locate_plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `map' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `locate_plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:27:in `all_plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:22:in `plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:45:in `add_plugin_load_paths' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:269:in `add_plugin_load_paths' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:135:in `process' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `send' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `run' /Users/charlesju/work/SyncManager/config/environment.rb:16 /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `require' Charles ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2010-02-22 20:04 Message: Time to vendor in rubygems? Can that be done? Dan ---------------------------------------------------------------------- Comment By: Vidal Graupera (vgraupera) Date: 2010-02-22 19:40 Message: I hit the exact same problem. My platform is OS X 10.6.2 and ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0] ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27868&group_id=126 From noreply at rubyforge.org Mon Apr 12 13:05:12 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 12 Apr 2010 13:05:12 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Patches-28083 ] Eliminate a misleading warning when installing a gem with the --bindir option Message-ID: <20100412170512.283051D7889B@rubyforge.org> Patches item #28083, was opened at 2010-04-12 19:05 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=28083&group_id=126 Category: `gem install` Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Frank Luithle (sigi) Assigned to: Nobody (None) Summary: Eliminate a misleading warning when installing a gem with the --bindir option Initial Comment: The --bindir option changes the target directory for executables/wrappers. 'gem install' makes a sanity check to see if the bin target directory is in the current PATH, and outputs a warning if that's not the case. However, when --bindir is used, the value of the option is not recognized when checking for PATH consistency, so the warning is always given even if the PATH is correct (ie. it contains the target bin directory). This patch corrects this towards a more sane behaviour. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=28083&group_id=126 From noreply at rubyforge.org Wed Apr 14 12:06:16 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 14 Apr 2010 12:06:16 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28091 ] RubyGems Installer Cuts Off Beginning Characters Message-ID: <20100414160616.A48AF1858320@rubyforge.org> Bugs item #28091, was opened at 2010-04-14 16:06 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28091&group_id=126 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: A Wilson (aawilson) Assigned to: Nobody (None) Summary: RubyGems Installer Cuts Off Beginning Characters Initial Comment: With ruby-1.9.1 on an mswin32 environment, running setup.rb produces files in the lib\ruby\site_ruby\1.9.1\rubygems which are mostly missing the first four characters of the file. For example, C:\scripting\ruby-1.9.1\lib\ruby\site_ruby\1.9.1\rubygems\commands\list_command.rb has the following for its first line: ire 'rubygems/command' rather than require 'rubygems/command' Inspection of the sources under the rubygems-1.3.6 directory shows that those sources do not have this issue, indicating that the problem has something to do with setup.rb or its dependencies. A workaround for this is to manually copy the rubygems-1.3.6\lib\rubygems directory into ruby-1.9.1\lib\ruby\site_ruby\1.9.1\. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28091&group_id=126 From noreply at rubyforge.org Thu Apr 15 00:40:49 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 15 Apr 2010 00:40:49 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28092 ] Errno::EHOSTDOWN: Host is down - connect(2) Message-ID: <20100415044049.93FED1D7888F@rubyforge.org> Bugs item #28092, was opened at 2010-04-14 21:40 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28092&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Eric Peterson (ericdp) Assigned to: Nobody (None) Summary: Errno::EHOSTDOWN: Host is down - connect(2) Initial Comment: On a Mac v.10.6.3, attempting to update my gems. here's my environment and then the errors I get >ruby -v ruby 1.8.7 (2009-06-08 patchlevel 173) [universal-darwin10.0] >gem -v 1.3.6 >gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.6 - RUBY VERSION: 1.8.7 (2009-06-08 patchlevel 173) [universal-darwin10.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-10 - GEM PATHS: - /Library/Ruby/Gems/1.8 - /Users/eric/.gem/ruby/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/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 >sudo gem update -v Updating installed gems GET http://gems.rubyforge.org/latest_specs.4.8.gz 302 Found HEAD http://gems.rubyforge.org/specs.4.8.gz 302 Found HEAD http://gems.rubyforge.org/yaml 200 OK HEAD http://gems.github.com/specs.4.8.gz 200 OK WARNING: RubyGems 1.2+ index not found for: http://gems.rubyforge.org/ RubyGems will revert to legacy indexes degrading performance. HEAD http://gems.rubyforge.org/Marshal.4.8 200 OK GET http://gems.rubyforge.org/quick/latest_index.rz 302 Found Latest index not found, using quick index GET http://gems.rubyforge.org/quick/index.rz 302 Found ERROR: Falling back to bulk fetch: No quick index found: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/quick/index.rz) Bulk updating Gem source index for: http://gems.rubyforge.org/ GET http://gems.rubyforge.org/Marshal.4.8.Z 302 Found ERROR: Unable to fetch Marshal.4.8.Z: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/Marshal.4.8.Z) GET http://gems.rubyforge.org/Marshal.4.8 302 Found ERROR: Unable to fetch Marshal.4.8: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/Marshal.4.8) GET http://gems.rubyforge.org/yaml.Z 302 Found ERROR: Unable to fetch yaml.Z: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/yaml.Z) GET http://gems.rubyforge.org/yaml 302 Found ERROR: Unable to fetch yaml: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/yaml) ERROR: While executing gem ... (Gem::RemoteSourceException) Error fetching remote gem cache: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/yaml) ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28092&group_id=126 From noreply at rubyforge.org Sat Apr 17 00:29:35 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 17 Apr 2010 00:29:35 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28103 ] Errno::EHOSTDOWN: Host is down - connect(2) Message-ID: <20100417042935.5CFEE1858322@rubyforge.org> Bugs item #28103, was opened at 2010-04-16 21:29 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28103&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Eric Peterson (ericdp) Assigned to: Nobody (None) Summary: Errno::EHOSTDOWN: Host is down - connect(2) Initial Comment: On a Mac v.10.6.3, attempting to update my gems. here's my environment and then the errors I get >ruby -v ruby 1.8.7 (2009-06-08 patchlevel 173) [universal-darwin10.0] >gem -v 1.3.6 >gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.6 - RUBY VERSION: 1.8.7 (2009-06-08 patchlevel 173) [universal-darwin10.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-10 - GEM PATHS: - /Library/Ruby/Gems/1.8 - /Users/eric/.gem/ruby/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/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 >sudo gem update -v Updating installed gems GET http://gems.rubyforge.org/latest_specs.4.8.gz 302 Found HEAD http://gems.rubyforge.org/specs.4.8.gz 302 Found HEAD http://gems.rubyforge.org/yaml 200 OK HEAD http://gems.github.com/specs.4.8.gz 200 OK WARNING: RubyGems 1.2+ index not found for: http://gems.rubyforge.org/ RubyGems will revert to legacy indexes degrading performance. HEAD http://gems.rubyforge.org/Marshal.4.8 200 OK GET http://gems.rubyforge.org/quick/latest_index.rz 302 Found Latest index not found, using quick index GET http://gems.rubyforge.org/quick/index.rz 302 Found ERROR: Falling back to bulk fetch: No quick index found: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/quick/index.rz) Bulk updating Gem source index for: http://gems.rubyforge.org/ GET http://gems.rubyforge.org/Marshal.4.8.Z 302 Found ERROR: Unable to fetch Marshal.4.8.Z: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/Marshal.4.8.Z) GET http://gems.rubyforge.org/Marshal.4.8 302 Found ERROR: Unable to fetch Marshal.4.8: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/Marshal.4.8) GET http://gems.rubyforge.org/yaml.Z 302 Found ERROR: Unable to fetch yaml.Z: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/yaml.Z) GET http://gems.rubyforge.org/yaml 302 Found ERROR: Unable to fetch yaml: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/yaml) ERROR: While executing gem ... (Gem::RemoteSourceException) Error fetching remote gem cache: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/yaml) ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28103&group_id=126 From rick.denatale at gmail.com Sat Apr 17 17:20:47 2010 From: rick.denatale at gmail.com (Rick DeNatale) Date: Sat, 17 Apr 2010 17:20:47 -0400 Subject: [Rubygems-developers] [ANN] Announcing ad_agency version 0.1.0 Message-ID: Announcing ad_agency version 0.1.0 An extension to Jeweler for generating announcements One of the facilities I missed in moving from hoe to jeweler was the ability to easily announce new versions of gems. ad_agency fills that hole. Changes: === 0.1.0 Initial Release Basic generation of announce email - see README.rdoc -- 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 noreply at rubyforge.org Sun Apr 18 03:19:55 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sun, 18 Apr 2010 03:19:55 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27872 ] 1.3.6 & quot; gem unpack& quot; fails with & quot; You don't have write permissions& quot; error Message-ID: <20100418071955.D909F1D78895@rubyforge.org> Bugs item #27872, was opened at 2010-02-22 19:07 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27872&group_id=126 Category: None Group: v1.3.x Status: Closed Resolution: Accepted Priority: 3 Submitted By: Timothy Jones (tjones) Assigned to: Eric Hodel (drbrain) Summary: 1.3.6 &quot;gem unpack&quot; fails with &quot;You don't have write permissions&quot; error Initial Comment: Running "gem unpack" version 1.3.6 as a non-root user (without write permissions into the system gem repository) fails with a permissions error, even though the target directory IS writable. This appears to be a 1.3.6 regression as it worked properly before. ---------------------------------------------------------------------- Comment By: Vladimir Sizikov (vvs) Date: 2010-04-18 09:19 Message: We got a similar bug report against JRuby 1.5RC1 (which includes rubygems 1.3.6): http://jira.codehaus.org/browse/JRUBY-4727 Any hints on when 1.3.7 is going to be released? ---------------------------------------------------------------------- Comment By: Kurt Werle (kwerle) Date: 2010-03-20 19:11 Message: This is much more than "highly annoying". It means that I can't install gems unless I have root. Installing gems should almost never require root. ---------------------------------------------------------------------- Comment By: Chad Woolley (thewoolleyman) Date: 2010-03-04 09:14 Message: The RubyGems test suite runs under Continuous Integration here: http://ci.pivotallabs.com:3333/builds/RubyGems If a particular feature is not covered by the test suite, patches to the test suite are welcome. ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2010-03-04 08:20 Message: http://rubyforge.org/tracker/index.php?func=detail&aid=27868&group_id=126&atid=575 is more important, but I have no confirmation of a fix. You mean RubyGems should have a test suite like the one in the test directory? ---------------------------------------------------------------------- Comment By: Timothy Jones (tjones) Date: 2010-03-03 21:31 Message: Understood. Perhaps you might consider automated testing in the future to prevent such regressions and maintain the integrity of the project. ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2010-03-03 21:22 Message: I think this issue is less critical than others like actual gem loading. At any time you can checkout the code from the repository and install yourself (ruby setup.rb) Each project has it's own release process, your annoyance level is not the priority, the whole project integrity is. ---------------------------------------------------------------------- Comment By: Timothy Jones (tjones) Date: 2010-03-03 20:55 Message: I think a patch release should be issued for this ASAP. It is highly annoying. ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2010-02-24 07:00 Message: Fixed in r2458 ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27872&group_id=126 From noreply at rubyforge.org Mon Apr 19 23:20:51 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 19 Apr 2010 23:20:51 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27960 ] rubygems 1.3.6 can't fetch a gem with a version other than the newest version Message-ID: <20100420032051.3BEDE18582CE@rubyforge.org> Bugs item #27960, was opened at 2010-03-12 13:21 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27960&group_id=126 Category: `gem` commands (remote behavior) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Eric Hankins (stormsilver) Assigned to: Nobody (None) Summary: rubygems 1.3.6 can't fetch a gem with a version other than the newest version Initial Comment: It seems that with the newest version of rubygems, gem fetch can only fetch the newest version of a gem. If you specify any version other than the newest one in a given repo, it tells you that it cannot find the gem. Here is an example session showing the problem with activesupport, but it happens with any gem. # gem -v 1.3.6 # ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [x86_64-linux] # gem sources *** CURRENT SOURCES *** http://rubygems.org # gem list -r -a activesupport *** REMOTE GEMS *** activesupport (2.3.5, 2.3.4, 2.3.3, 2.3.2, 2.2.3, 2.2.2, 2.1.2, 2.1.1, 2.1.0, 2.0.5, 2.0.4, 2.0.2, 2.0.1, 2.0.0, 1.4.4, 1.4.3, 1.4.2, 1.4.1, 1.4.0, 1.3.1, 1.3.0, 1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0) activesupport-jcache (0.1.0) # gem fetch activesupport -v 2.3.2 ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.2" ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.4" ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.5" Downloaded activesupport-2.3.5 ---------------------------------------------------------------------- Comment By: Stephen Bannasch (stepheneb) Date: 2010-04-19 22:20 Message: I've confirmed this same bug on MacOS X 10.5.8. The problem occurs using: gem fetch and does not occur using: gem install $ gem list -r -a ci_reporter *** REMOTE GEMS *** ci_reporter (1.6.2, 1.6.1, 1.6.0, 1.5.3, 1.5.2, 1.5.1, 1.5, 1.4, 1.3.5, 1.3.4, 1.3.3, 1.3.2, 1.3.1, 1.3, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2, 1.1, 1.0) $ gem fetch ci_reporter -v '= 1.6.0' ERROR: Could not find ci_reporter in any repository $ sudo gem install ci_reporter -v '= 1.6.0' Successfully installed ci_reporter-1.6.0 1 gem installed /Library/Ruby/Gems/1.8/gems/rdoc-2.5.4/lib/rdoc/ruby_lex.rb:67: warning: parenthesize argument(s) for future version Installing ri documentation for ci_reporter-1.6.0... Building YARD (yri) index for ci_reporter-1.6.0... Installing RDoc documentation for ci_reporter-1.6.0... $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.6 - RUBY VERSION: 1.8.6 (2009-06-08 patchlevel 369) [universal-darwin9.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-9 - GEM PATHS: - /Library/Ruby/Gems/1.8 - /Users/stephen/.gem/ruby/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://rubygems.org", "http://gems.opscode.com/"] - "gemcutter_key" => "12a51589b36ebd91e969de9fedfb5c17" - REMOTE SOURCES: - http://rubygems.org - http://gems.opscode.com/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27960&group_id=126 From noreply at rubyforge.org Mon Apr 19 23:35:15 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 19 Apr 2010 23:35:15 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28118 ] first gem fails to install when installing two gems with specific version constraints Message-ID: <20100420033515.1351918582D0@rubyforge.org> Bugs item #28118, was opened at 2010-04-19 22:35 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28118&group_id=126 Category: `gem install` command Group: None Status: Open Resolution: None Priority: 3 Submitted By: Stephen Bannasch (stepheneb) Assigned to: Nobody (None) Summary: first gem fails to install when installing two gems with specific version constraints Initial Comment: When installing two gems that have specific version constrains the first gem will no be installed with an error like this: ERROR: could not find gem locally or in a repository Both the gems ci_reporter and hpricot exist in multiple versions: $ gem list -a -r ci_reporter *** REMOTE GEMS *** ci_reporter (1.6.2, 1.6.1, 1.6.0, 1.5.3, 1.5.2, 1.5.1, 1.5, 1.4, 1.3.5, 1.3.4, 1.3.3, 1.3.2, 1.3.1, 1.3, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2, 1.1, 1.0) $ gem list -a -r hpricot *** REMOTE GEMS *** hpricot (0.8.2, 0.8.1, 0.8, 0.7, 0.6.164, 0.6.161, 0.6, 0.5, 0.4) When I try and install multiple gems with specific version constraints gem reports the first gem can't be found. $ sudo gem install ci_reporter -v'>= 1.6.0' hpricot -v'= 0.6.164' ERROR: could not find gem ci_reporter locally or in a repository Building native extensions. This could take a while... Successfully installed hpricot-0.6.164 1 gem installed /Library/Ruby/Gems/1.8/gems/rdoc-2.5.4/lib/rdoc/ruby_lex.rb:67: warning: parenthesize argument(s) for future version Installing ri documentation for hpricot-0.6.164... Building YARD (yri) index for hpricot-0.6.164... Installing RDoc documentation for hpricot-0.6.164... If I instead uninstall hpricot and reverse the order of the installed gems, gem reports the other gem can't be found: $ sudo gem uninstall hpricot Successfully uninstalled hpricot-0.6.164 $ sudo gem install hpricot -v'= 0.6.164' ci_reporter -v'>= 1.6.0' ERROR: could not find gem hpricot locally or in a repository Successfully installed ci_reporter-1.6.2 1 gem installed /Library/Ruby/Gems/1.8/gems/rdoc-2.5.4/lib/rdoc/ruby_lex.rb:67: warning: parenthesize argument(s) for future version Installing ri documentation for ci_reporter-1.6.2... Building YARD (yri) index for ci_reporter-1.6.2... Installing RDoc documentation for ci_reporter-1.6.2... $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.6 - RUBY VERSION: 1.8.6 (2009-06-08 patchlevel 369) [universal-darwin9.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-9 - GEM PATHS: - /Library/Ruby/Gems/1.8 - /Users/stephen/.gem/ruby/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://rubygems.org", "http://gems.opscode.com/"] - "gemcutter_key" => "12a51589b36ebd91e969de9fedfb5c17" - REMOTE SOURCES: - http://rubygems.org - http://gems.opscode.com/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28118&group_id=126 From devnull+rubygems-ci at pivotallabs.com Tue Apr 20 03:29:31 2010 From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com) Date: Tue, 20 Apr 2010 07:29:31 +0000 Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2485 failed Message-ID: <4bcd57db8aabb_5370..fdbe41b86234@ci.pivotallabs.com.tmail> The build failed. CHANGES ------- New revision 2485 detected Revision 2485 committed by drbrain on 2010-04-20 07:15:22 Merge 2484 M /trunk M /branches/1_3 M /branches/1_3/lib/rubygems/specification.rb M /branches/1_3/test/gemutilities.rb M /branches/1_3/ChangeLog TEST FAILURES AND ERRORS ----------------------- Name: test_class_from_file_by_path(TestGemFormat) Type: Failure Message: Expected "pl-1-i386-linux", not "pl-1-x86-linux". ./test/test_gem_format.rb:27 Name: test_generate_index_legacy_back_to_back(TestGemIndexer) Type: Failure Message: /tmp/test_rubygems_25638/quick/pl-1-i386-linux.gemspec.rz does not exist ./test/test_gem_indexer.rb:380 Name: test_generate_index_modern_back_to_back(TestGemIndexer) Type: Failure Message: /tmp/test_rubygems_25638/quick/pl-1-i386-linux.gemspec.rz does not exist ./test/test_gem_indexer.rb:476 Name: test_generate_index_latest_specs(TestGemIndexer) Type: Failure Message: Expected [["a", Gem::Version.new("2"), "ruby"], ["a_evil", Gem::Version.new("9"), "ruby"], ["b", Gem::Version.new("2"), "ruby"], ["c", Gem::Version.new("1.2"), "ruby"], ["d", Gem::Version.new("2.0"), "ruby"], ["pl", Gem::Version.new("1"), "i386-linux"]], not [["a", Gem::Version.new("2"), "ruby"], ["a_evil", Gem::Version.new("9"), "ruby"], ["b", Gem::Version.new("2"), "ruby"], ["c", Gem::Version.new("1.2"), "ruby"], ["d", Gem::Version.new("2.0"), "ruby"]]. ./test/test_gem_indexer.rb:588 Name: test_generate_index_legacy(TestGemIndexer) Type: Failure Message: /tmp/test_rubygems_25638/quick/pl-1-i386-linux.gemspec.rz does not exist ./test/test_gem_indexer.rb:326 Name: test_generate_index(TestGemIndexer) Type: Failure Message: Expected "a-1\na-2\na-3.a\na_evil-9\nb-2\nc-1.2\nd-2.0\nd-2.0.a\nd-2.0.b\npl-1-i386-linux\n", not "a-1\na-2\na-3.a\na_evil-9\nb-2\nc-1.2\nd-2.0\nd-2.0.a\nd-2.0.b\n". ./test/test_gem_indexer.rb:124 Name: test_generate_index_specs(TestGemIndexer) Type: Failure Message: Expected [["a", Gem::Version.new("1"), "ruby"], ["a", Gem::Version.new("2"), "ruby"], ["a_evil", Gem::Version.new("9"), "ruby"], ["b", Gem::Version.new("2"), "ruby"], ["c", Gem::Version.new("1.2"), "ruby"], ["d", Gem::Version.new("2.0"), "ruby"], ["pl", Gem::Version.new("1"), "i386-linux"]], not [["a", Gem::Version.new("1"), "ruby"], ["a", Gem::Version.new("2"), "ruby"], ["a_evil", Gem::Version.new("9"), "ruby"], ["b", Gem::Version.new("2"), "ruby"], ["c", Gem::Version.new("1.2"), "ruby"], ["d", Gem::Version.new("2.0"), "ruby"]]. ./test/test_gem_indexer.rb:554 Name: test_generate_index_ui(TestGemIndexer) Type: Failure Message: Expected /^\.\.\.\.\.\.\.\.\.\.$/ to match "Loading 10 gems from /tmp/test_rubygems_25638\n.........\nLoaded all gems\nloaded: 0.014s\nGenerating Marshal quick index gemspecs for 9 gems\n.........\nComplete\nGenerated Marshal quick index gemspecs: 0.030s\nGenerating YAML quick index gemspecs for 9 gems\n......\nComplete\nGenerated YAML quick index gemspecs: 0.018s\nGenerating quick index\nGenerated quick index: 0.000s\nGenerating latest index\nGenerated latest index: 0.000s\nGenerating Marshal master index\nGenerated Marshal master index: 0.001s\nGenerating YAML master index for 9 gems (this may take a while)\n.........\nComplete\nGenerated YAML master index: 0.024s\nGenerating specs index\nGenerated specs index: 0.000s\nGenerating latest specs index\nGenerated latest specs index: 0.000s\nGenerating prerelease specs index\nGenerated prerelease specs index: 0.000s\nGenerated rss: 0.001s\nCompressing indicies\nCompressed indicies: 0.035s\n". ./test/test_gem_indexer.rb:495 Name: test_to_yaml_platform_legacy(TestGemSpecification) Type: Failure Message: Expected "powerpc-darwin7.9.0", not "powerpc-darwin-7". ./test/test_gem_specification.rb:914 See http://ci.pivotallabs.com:3333/builds/RubyGems/2485 for details. From devnull+rubygems-ci at pivotallabs.com Tue Apr 20 03:23:53 2010 From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com) Date: Tue, 20 Apr 2010 07:23:53 +0000 Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2484 failed Message-ID: <4bcd5689e7581_5370..fdbe41b861d2@ci.pivotallabs.com.tmail> The build failed. CHANGES ------- New revision 2484 detected Revision 2484 committed by drbrain on 2010-04-20 07:10:29 Ruby bug #3102 M /trunk/lib/rubygems/specification.rb M /trunk/test/gemutilities.rb M /trunk/ChangeLog TEST FAILURES AND ERRORS ----------------------- Name: test_class_from_file_by_path(TestGemFormat) Type: Failure Message: Expected "pl-1-i386-linux", not "pl-1-x86-linux". ./test/test_gem_format.rb:27 Name: test_generate_index_latest_specs(TestGemIndexer) Type: Failure Message: Expected [["a", Gem::Version.new("2"), "ruby"], ["a_evil", Gem::Version.new("9"), "ruby"], ["b", Gem::Version.new("2"), "ruby"], ["c", Gem::Version.new("1.2"), "ruby"], ["d", Gem::Version.new("2.0"), "ruby"], ["pl", Gem::Version.new("1"), "i386-linux"]], not [["a", Gem::Version.new("2"), "ruby"], ["a_evil", Gem::Version.new("9"), "ruby"], ["b", Gem::Version.new("2"), "ruby"], ["c", Gem::Version.new("1.2"), "ruby"], ["d", Gem::Version.new("2.0"), "ruby"]]. ./test/test_gem_indexer.rb:588 Name: test_generate_index_legacy_back_to_back(TestGemIndexer) Type: Failure Message: /tmp/test_rubygems_25056/quick/pl-1-i386-linux.gemspec.rz does not exist ./test/test_gem_indexer.rb:380 Name: test_generate_index_modern_back_to_back(TestGemIndexer) Type: Failure Message: /tmp/test_rubygems_25056/quick/pl-1-i386-linux.gemspec.rz does not exist ./test/test_gem_indexer.rb:476 Name: test_generate_index_specs(TestGemIndexer) Type: Failure Message: Expected [["a", Gem::Version.new("1"), "ruby"], ["a", Gem::Version.new("2"), "ruby"], ["a_evil", Gem::Version.new("9"), "ruby"], ["b", Gem::Version.new("2"), "ruby"], ["c", Gem::Version.new("1.2"), "ruby"], ["d", Gem::Version.new("2.0"), "ruby"], ["pl", Gem::Version.new("1"), "i386-linux"]], not [["a", Gem::Version.new("1"), "ruby"], ["a", Gem::Version.new("2"), "ruby"], ["a_evil", Gem::Version.new("9"), "ruby"], ["b", Gem::Version.new("2"), "ruby"], ["c", Gem::Version.new("1.2"), "ruby"], ["d", Gem::Version.new("2.0"), "ruby"]]. ./test/test_gem_indexer.rb:554 Name: test_generate_index_ui(TestGemIndexer) Type: Failure Message: Expected /^\.\.\.\.\.\.\.\.\.\.$/ to match "Loading 10 gems from /tmp/test_rubygems_25056\n.........\nLoaded all gems\nloaded: 0.014s\nGenerating Marshal quick index gemspecs for 9 gems\n.........\nComplete\nGenerated Marshal quick index gemspecs: 0.004s\nGenerating YAML quick index gemspecs for 9 gems\n......\nComplete\nGenerated YAML quick index gemspecs: 0.044s\nGenerating quick index\nGenerated quick index: 0.000s\nGenerating latest index\nGenerated latest index: 0.000s\nGenerating Marshal master index\nGenerated Marshal master index: 0.001s\nGenerating YAML master index for 9 gems (this may take a while)\n.........\nComplete\nGenerated YAML master index: 0.025s\nGenerating specs index\nGenerated specs index: 0.000s\nGenerating latest specs index\nGenerated latest specs index: 0.000s\nGenerating prerelease specs index\nGenerated prerelease specs index: 0.000s\nGenerated rss: 0.001s\nCompressing indicies\nCompressed indicies: 0.004s\n". ./test/test_gem_indexer.rb:495 Name: test_generate_index(TestGemIndexer) Type: Failure Message: Expected "a-1\na-2\na-3.a\na_evil-9\nb-2\nc-1.2\nd-2.0\nd-2.0.a\nd-2.0.b\npl-1-i386-linux\n", not "a-1\na-2\na-3.a\na_evil-9\nb-2\nc-1.2\nd-2.0\nd-2.0.a\nd-2.0.b\n". ./test/test_gem_indexer.rb:124 Name: test_generate_index_legacy(TestGemIndexer) Type: Failure Message: /tmp/test_rubygems_25056/quick/pl-1-i386-linux.gemspec.rz does not exist ./test/test_gem_indexer.rb:326 Name: test_to_yaml_platform_legacy(TestGemSpecification) Type: Failure Message: Expected "powerpc-darwin7.9.0", not "powerpc-darwin-7". ./test/test_gem_specification.rb:914 See http://ci.pivotallabs.com:3333/builds/RubyGems/2484 for details. From noreply at rubyforge.org Tue Apr 20 05:16:03 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 20 Apr 2010 05:16:03 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28122 ] uninitialized constant Gem::RbConfig when installing rubygems 1.3.6 on Ubuntu dapper (Regression from 1.3.5) Message-ID: <20100420091604.0CC66185830C@rubyforge.org> Bugs item #28122, was opened at 20/04/2010 11:16 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28122&group_id=126 Category: RubyGems installer (setup.rb) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Joel Kociolek (fcjoel) Assigned to: Nobody (None) Summary: uninitialized constant Gem::RbConfig when installing rubygems 1.3.6 on Ubuntu dapper (Regression from 1.3.5) Initial Comment: When installing rubygems 1.3.6 on Ubuntu Dapper (6.04 LTS) I get the following error: # ruby setup.rb ./lib/rubygems.rb:124: uninitialized constant Gem::RbConfig (NameError) from setup.rb:24 Rubygems 1.3.5 installs fine Ruby version on Ubuntu Dapper is 1.8.4 It looks like the same bug as [#16457] that was closed long ago. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28122&group_id=126 From devnull+rubygems-ci at pivotallabs.com Tue Apr 20 13:56:55 2010 From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com) Date: Tue, 20 Apr 2010 17:56:55 +0000 Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2486 failed Message-ID: <4bcdeae71e964_5370..fdbe41b86394@ci.pivotallabs.com.tmail> The build failed. CHANGES ------- New revision 2486 detected Revision 2486 committed by drbrain on 2010-04-20 17:40:44 Ruby bug #3103 M /trunk/lib/rubygems/remote_fetcher.rb M /trunk/ChangeLog TEST FAILURES AND ERRORS ----------------------- Name: test_class_from_file_by_path(TestGemFormat) Type: Failure Message: Expected "pl-1-i386-linux", not "pl-1-x86-linux". ./test/test_gem_format.rb:27 Name: test_generate_index_legacy_back_to_back(TestGemIndexer) Type: Failure Message: /tmp/test_rubygems_21261/quick/pl-1-i386-linux.gemspec.rz does not exist ./test/test_gem_indexer.rb:380 Name: test_generate_index_modern_back_to_back(TestGemIndexer) Type: Failure Message: /tmp/test_rubygems_21261/quick/pl-1-i386-linux.gemspec.rz does not exist ./test/test_gem_indexer.rb:476 Name: test_generate_index(TestGemIndexer) Type: Failure Message: Expected "a-1\na-2\na-3.a\na_evil-9\nb-2\nc-1.2\nd-2.0\nd-2.0.a\nd-2.0.b\npl-1-i386-linux\n", not "a-1\na-2\na-3.a\na_evil-9\nb-2\nc-1.2\nd-2.0\nd-2.0.a\nd-2.0.b\n". ./test/test_gem_indexer.rb:124 Name: test_generate_index_ui(TestGemIndexer) Type: Failure Message: Expected /^\.\.\.\.\.\.\.\.\.\.$/ to match "Loading 10 gems from /tmp/test_rubygems_21261\n.........\nLoaded all gems\nloaded: 0.014s\nGenerating Marshal quick index gemspecs for 9 gems\n.........\nComplete\nGenerated Marshal quick index gemspecs: 0.026s\nGenerating YAML quick index gemspecs for 9 gems\n......\nComplete\nGenerated YAML quick index gemspecs: 0.019s\nGenerating quick index\nGenerated quick index: 0.000s\nGenerating latest index\nGenerated latest index: 0.000s\nGenerating Marshal master index\nGenerated Marshal master index: 0.001s\nGenerating YAML master index for 9 gems (this may take a while)\n.........\nComplete\nGenerated YAML master index: 0.024s\nGenerating specs index\nGenerated specs index: 0.000s\nGenerating latest specs index\nGenerated latest specs index: 0.000s\nGenerating prerelease specs index\nGenerated prerelease specs index: 0.000s\nGenerated rss: 0.001s\nCompressing indicies\nCompressed indicies: 0.032s\n". ./test/test_gem_indexer.rb:495 Name: test_generate_index_legacy(TestGemIndexer) Type: Failure Message: /tmp/test_rubygems_21261/quick/pl-1-i386-linux.gemspec.rz does not exist ./test/test_gem_indexer.rb:326 Name: test_generate_index_specs(TestGemIndexer) Type: Failure Message: Expected [["a", Gem::Version.new("1"), "ruby"], ["a", Gem::Version.new("2"), "ruby"], ["a_evil", Gem::Version.new("9"), "ruby"], ["b", Gem::Version.new("2"), "ruby"], ["c", Gem::Version.new("1.2"), "ruby"], ["d", Gem::Version.new("2.0"), "ruby"], ["pl", Gem::Version.new("1"), "i386-linux"]], not [["a", Gem::Version.new("1"), "ruby"], ["a", Gem::Version.new("2"), "ruby"], ["a_evil", Gem::Version.new("9"), "ruby"], ["b", Gem::Version.new("2"), "ruby"], ["c", Gem::Version.new("1.2"), "ruby"], ["d", Gem::Version.new("2.0"), "ruby"]]. ./test/test_gem_indexer.rb:554 Name: test_generate_index_latest_specs(TestGemIndexer) Type: Failure Message: Expected [["a", Gem::Version.new("2"), "ruby"], ["a_evil", Gem::Version.new("9"), "ruby"], ["b", Gem::Version.new("2"), "ruby"], ["c", Gem::Version.new("1.2"), "ruby"], ["d", Gem::Version.new("2.0"), "ruby"], ["pl", Gem::Version.new("1"), "i386-linux"]], not [["a", Gem::Version.new("2"), "ruby"], ["a_evil", Gem::Version.new("9"), "ruby"], ["b", Gem::Version.new("2"), "ruby"], ["c", Gem::Version.new("1.2"), "ruby"], ["d", Gem::Version.new("2.0"), "ruby"]]. ./test/test_gem_indexer.rb:588 Name: test_to_yaml_platform_legacy(TestGemSpecification) Type: Failure Message: Expected "powerpc-darwin7.9.0", not "powerpc-darwin-7". ./test/test_gem_specification.rb:914 See http://ci.pivotallabs.com:3333/builds/RubyGems/2486 for details. From noreply at rubyforge.org Tue Apr 20 18:10:46 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 20 Apr 2010 18:10:46 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28122 ] uninitialized constant Gem::RbConfig when installing rubygems 1.3.6 on Ubuntu dapper (Regression from 1.3.5) Message-ID: <20100420221046.CB83C1858313@rubyforge.org> Bugs item #28122, was opened at 2010-04-20 02:16 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28122&group_id=126 Category: RubyGems installer (setup.rb) Group: v1.3.x >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: Joel Kociolek (fcjoel) >Assigned to: Eric Hodel (drbrain) Summary: uninitialized constant Gem::RbConfig when installing rubygems 1.3.6 on Ubuntu dapper (Regression from 1.3.5) Initial Comment: When installing rubygems 1.3.6 on Ubuntu Dapper (6.04 LTS) I get the following error: # ruby setup.rb ./lib/rubygems.rb:124: uninitialized constant Gem::RbConfig (NameError) from setup.rb:24 Rubygems 1.3.5 installs fine Ruby version on Ubuntu Dapper is 1.8.4 It looks like the same bug as [#16457] that was closed long ago. ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-20 15:10 Message: Upgrade to ruby 1.8.6 or newer. I haven't tested RubyGems on a version older than 1.8.6 in over a year, so I guess I should have made it official earlier. The next release will require ruby 1.8.6 or newer. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28122&group_id=126 From devnull+rubygems-ci at pivotallabs.com Tue Apr 20 23:48:10 2010 From: devnull+rubygems-ci at pivotallabs.com (devnull+rubygems-ci at pivotallabs.com) Date: Wed, 21 Apr 2010 03:48:10 +0000 Subject: [Rubygems-developers] [CruiseControl] RubyGems build 2487 fixed Message-ID: <4bce757aab962_5370..fdbe41b86485@ci.pivotallabs.com.tmail> The build has been fixed. CHANGES ------- New revision 2487 detected Revision 2487 committed by drbrain on 2010-04-21 03:31:56 Be sure to run our custom yaml encoder. (Need to check with Aaron) M /trunk/lib/rubygems/specification.rb M /trunk/test/test_gem_specification.rb See http://ci.pivotallabs.com:3333/builds/RubyGems/2487 for details. From noreply at rubyforge.org Tue Apr 20 23:41:09 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 20 Apr 2010 23:41:09 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27996 ] "gem install rails" command fails with time-out error Message-ID: <20100421034109.B83AC1D78896@rubyforge.org> Bugs item #27996, was opened at 2010-03-21 23:23 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27996&group_id=126 Category: `gem install` command Group: None Status: Open Resolution: None >Priority: 1 Submitted By: Z R (zhinker) >Assigned to: Eric Hodel (drbrain) >Summary: "gem install rails" command fails with time-out error Initial Comment: Hi, I just tried installing ruby on rails on a clean Ubuntu 9.10 VM. I followed the steps on this site: http://castilho.biz/blog/2009/11/05/ruby-on-rails-ubuntu-9-10-karmic-koala/. However, when I try to install rails it fails with a timeout error. I reran the command with the --debug parameter and pasted that output below. zain at ubuntu-x86:~$ sudo gem --debug install rails Exception `NameError' at /usr/lib/ruby/1.8/rubygems/command_manager.rb:161 - uninitialized constant Gem::Commands::InstallCommand Exception `Gem::LoadError' at /usr/lib/ruby/1.8/rubygems.rb:827 - Could not find RubyGem test-unit (>= 0) Exception `Gem::LoadError' at /usr/lib/ruby/1.8/rubygems.rb:827 - Could not find RubyGem sources (> 0.0.1) Exception `#' at /usr/lib/ruby/1.8/timeout.rb:60 - execution expired Exception `Timeout::Error' at /usr/lib/ruby/1.8/timeout.rb:74 - execution expired Exception `Gem::RemoteFetcher::FetchError' at /usr/lib/ruby/1.8/rubygems/remote_fetcher.rb:170 - timed out (http://gems.rubyforge.org/quick/Marshal.4.8/activesupport-2.3.5.gemspec.rz) Exception `Gem::RemoteFetcher::FetchError' at /usr/lib/ruby/1.8/rubygems/spec_fetcher.rb:76 - timed out (http://gems.rubyforge.org/quick/Marshal.4.8/activesupport-2.3.5.gemspec.rz) Exception `#' at /usr/lib/ruby/1.8/timeout.rb:60 - execution expired Exception `Timeout::Error' at /usr/lib/ruby/1.8/timeout.rb:74 - execution expired Exception `Gem::RemoteFetcher::FetchError' at /usr/lib/ruby/1.8/rubygems/remote_fetcher.rb:170 - timed out (http://gems.rubyforge.org/gems/rake-0.8.7.gem) Exception `Gem::RemoteFetcher::FetchError' at /usr/lib/ruby/1.8/rubygems/remote_fetcher.rb:110 - timed out (http://gems.rubyforge.org/gems/rake-0.8.7.gem) Exception `Gem::RemoteFetcher::FetchError' at /usr/lib/ruby/1.8/rubygems/dependency_installer.rb:236 - timed out (http://gems.rubyforge.org/gems/rake-0.8.7.gem) ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError) timed out (http://gems.rubyforge.org/gems/rake-0.8.7.gem) /usr/lib/ruby/1.8/rubygems/remote_fetcher.rb:170:in `fetch_path' /usr/lib/ruby/1.8/rubygems/remote_fetcher.rb:108:in `download' /usr/lib/ruby/1.8/rubygems/dependency_installer.rb:232:in `install' /usr/lib/ruby/1.8/rubygems/dependency_installer.rb:222:in `each' /usr/lib/ruby/1.8/rubygems/dependency_installer.rb:222:in `install' /usr/lib/ruby/1.8/rubygems/commands/install_command.rb:118:in `execute' /usr/lib/ruby/1.8/rubygems/commands/install_command.rb:115:in `each' /usr/lib/ruby/1.8/rubygems/commands/install_command.rb:115:in `execute' /usr/lib/ruby/1.8/rubygems/command.rb:257:in `invoke' /usr/lib/ruby/1.8/rubygems/command_manager.rb:132:in `process_args' /usr/lib/ruby/1.8/rubygems/command_manager.rb:102:in `run' /usr/lib/ruby/1.8/rubygems/gem_runner.rb:58:in `run' /usr/bin/gem:21 ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2010-03-22 01:57 Message: Please provide the output of `gem env` and also repeat the command with --verbose, which will tell us which files are timing out. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27996&group_id=126 From noreply at rubyforge.org Tue Apr 20 23:47:48 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 20 Apr 2010 23:47:48 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27995 ] Gem.default_exec_format does not work with IronRuby Message-ID: <20100421034748.A23A21D78897@rubyforge.org> Bugs item #27995, was opened at 2010-03-21 22:44 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27995&group_id=126 >Category: other >Group: v1.3.x Status: Open Resolution: None Priority: 4 Submitted By: Shri Borde (shrib) >Assigned to: Eric Hodel (drbrain) Summary: Gem.default_exec_format does not work with IronRuby Initial Comment: Gem.default_exec_format assumes that the Ruby interpreter command line (RbConfig::CONGIF[:ruby_install_name]) is of the form *ruby*. This works for command lines like ruby, ruby18, ruby19, jruby, etc. However, this does not work for IronRuby where the command line is "ir.exe". As a result, "ir.exe -S gem update --system" fails with the call stack shown below. This is a serious issue for IronRuby. RubyGems should have some way of dealing with such command lines. It could perhaps look at some new config setting, eg. RbConfig::CONFIG["defaul_exec_format"]. Or it could just append "%s" to RbConfig::CONGIF[:ruby_install_name]. lib/rubygems/defaults.rb:57:in `default_exec_format' lib/rubygems/commands/setup_command.rb:72:in `description' lib/rubygems/command.rb:393:in `create_option_parser' lib/rubygems/command.rb:359:in `parser' lib/rubygems/command.rb:328:in `handle_options' lib/rubygems/command.rb:251:in `invoke' lib/rubygems/command_manager.rb:134:in `process_args' lib/rubygems/command_manager.rb:104:in `run' lib/rubygems/gem_runner.rb:58:in `run' setup.rb:35 ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-20 20:47 Message: rubygems/defaults/ironruby.rb would go in RbConfig::CONFIG['rubylibdir'] (not in RuybGems) so it should be picked up even by setup.rb ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2010-03-23 00:19 Message: Good point, i think the answer is, there should be... ---------------------------------------------------------------------- Comment By: Shri Borde (shrib) Date: 2010-03-22 23:18 Message: The failure above happens in the child process spawned by the main "ir.exe -S gem update --system" process. The command line of the child process is "ir.exe setup.rb" and it executes in the rubygems-update gem folder after downloading the latest version of the rubygems-update gem. So if I add lib/rubygems/ironruby.rb, it would help with most commands except for "update --system". Is there a way to fix it for "update --system" too? Thanks for the comments. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2010-03-22 01:38 Message: Seems that iron ruby should be overriding default_exec_format in its own defaults/[engine].rb . >From the documentation: # == RubyGems Defaults, Packaging # # RubyGems defaults are stored in rubygems/defaults.rb. If you're packaging # RubyGems or implementing Ruby you can change RubyGems' defaults. # # For RubyGems packagers, provide lib/rubygems/operating_system.rb and # override any defaults from lib/rubygems/defaults.rb. # # For Ruby implementers, provide lib/rubygems/#{RUBY_ENGINE}.rb and override # any defaults from lib/rubygems/defaults.rb. HTH ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27995&group_id=126 From noreply at rubyforge.org Wed Apr 21 00:19:54 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 00:19:54 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27960 ] rubygems 1.3.6 can't fetch a gem with a version other than the newest version Message-ID: <20100421041954.7AB46185831E@rubyforge.org> Bugs item #27960, was opened at 2010-03-12 10:21 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27960&group_id=126 Category: `gem` commands (remote behavior) Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Eric Hankins (stormsilver) >Assigned to: Eric Hodel (drbrain) Summary: rubygems 1.3.6 can't fetch a gem with a version other than the newest version Initial Comment: It seems that with the newest version of rubygems, gem fetch can only fetch the newest version of a gem. If you specify any version other than the newest one in a given repo, it tells you that it cannot find the gem. Here is an example session showing the problem with activesupport, but it happens with any gem. # gem -v 1.3.6 # ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [x86_64-linux] # gem sources *** CURRENT SOURCES *** http://rubygems.org # gem list -r -a activesupport *** REMOTE GEMS *** activesupport (2.3.5, 2.3.4, 2.3.3, 2.3.2, 2.2.3, 2.2.2, 2.1.2, 2.1.1, 2.1.0, 2.0.5, 2.0.4, 2.0.2, 2.0.1, 2.0.0, 1.4.4, 1.4.3, 1.4.2, 1.4.1, 1.4.0, 1.3.1, 1.3.0, 1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0) activesupport-jcache (0.1.0) # gem fetch activesupport -v 2.3.2 ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.2" ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.4" ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.5" Downloaded activesupport-2.3.5 ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-20 21:19 Message: Fixed. ---------------------------------------------------------------------- Comment By: Stephen Bannasch (stepheneb) Date: 2010-04-19 20:20 Message: I've confirmed this same bug on MacOS X 10.5.8. The problem occurs using: gem fetch and does not occur using: gem install $ gem list -r -a ci_reporter *** REMOTE GEMS *** ci_reporter (1.6.2, 1.6.1, 1.6.0, 1.5.3, 1.5.2, 1.5.1, 1.5, 1.4, 1.3.5, 1.3.4, 1.3.3, 1.3.2, 1.3.1, 1.3, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2, 1.1, 1.0) $ gem fetch ci_reporter -v '= 1.6.0' ERROR: Could not find ci_reporter in any repository $ sudo gem install ci_reporter -v '= 1.6.0' Successfully installed ci_reporter-1.6.0 1 gem installed /Library/Ruby/Gems/1.8/gems/rdoc-2.5.4/lib/rdoc/ruby_lex.rb:67: warning: parenthesize argument(s) for future version Installing ri documentation for ci_reporter-1.6.0... Building YARD (yri) index for ci_reporter-1.6.0... Installing RDoc documentation for ci_reporter-1.6.0... $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.6 - RUBY VERSION: 1.8.6 (2009-06-08 patchlevel 369) [universal-darwin9.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-9 - GEM PATHS: - /Library/Ruby/Gems/1.8 - /Users/stephen/.gem/ruby/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://rubygems.org", "http://gems.opscode.com/"] - "gemcutter_key" => "12a51589b36ebd91e969de9fedfb5c17" - REMOTE SOURCES: - http://rubygems.org - http://gems.opscode.com/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27960&group_id=126 From noreply at rubyforge.org Wed Apr 21 00:22:21 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 00:22:21 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28024 ] plugins: can't bind as string (for better or worse). Message-ID: <20100421042221.270511D78897@rubyforge.org> Bugs item #28024, was opened at 2010-03-29 13:07 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28024&group_id=126 >Category: `gem` commands (other) >Group: v1.3.x >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: Roger Pack (rogerdpack) >Assigned to: Eric Hodel (drbrain) Summary: plugins: can't bind as string (for better or worse). Initial Comment: If I call Gem::CommandManager.instance.register_command 'git_install' I get this: ERROR: While executing gem ... (NoMethodError) undefined method `summary' for nil:NilClass C:/Ruby19/lib/ruby/site_ruby/1.9.1/rubygems/commands/help_command.rb:122:in `block in execute' C:/Ruby19/lib/ruby/site_ruby/1.9.1/rubygems/commands/help_command.rb:120:in `each' C:/Ruby19/lib/ruby/site_ruby/1.9.1/rubygems/commands/help_command.rb:120:in `execute' C:/Ruby19/lib/ruby/site_ruby/1.9.1/rubygems/command.rb:258:in `invoke' C:/Ruby19/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:134:in `process_args' C:/Ruby19/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb:104:in `run' C:/Ruby19/lib/ruby/site_ruby/1.9.1/rubygems/gem_runner.rb:58:in `run' C:/Ruby19/bin/gem:21:in `
' however with a symbol it works great. Thanks! -rp ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-20 21:22 Message: Use a Symbol I've updated the documentation. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28024&group_id=126 From noreply at rubyforge.org Wed Apr 21 00:24:49 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 00:24:49 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27917 ] A warning occurs when I run gem update --system (Ruby 1.9.1) Message-ID: <20100421042449.C27ED1D78899@rubyforge.org> Bugs item #27917, was opened at 2010-03-03 00:42 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27917&group_id=126 Category: None Group: None >Status: Closed Resolution: None Priority: 3 Submitted By: katherine pe (bridgeutopia) Assigned to: Nobody (None) Summary: A warning occurs when I run gem update --system (Ruby 1.9.1) Initial Comment: $ gem update --system WARNING: /usr/lib/ruby/gems/1.8/specifications/archive-tar-minitar-0.5.1.gemspec:12: invalid multibyte char (UTF-8) /usr/lib/ruby/gems/1.8/specifications/archive-tar-minitar-0.5.1.gemspec:12: syntax error, unexpected tIDENTIFIER, expecting keyword_end ...d heavily on Mauricio Fern?ndez's implementation in rpa-base... ... ^ /usr/lib/ruby/gems/1.8/specifications/archive-tar-minitar-0.5.1.gemspec:31: syntax error, unexpected tFLOAT, expecting keyword_end ...rsion) >= Gem::Version.new('1.2.0') then ... ^ /usr/lib/ruby/gems/1.8/specifications/archive-tar-minitar-0.5.1.gemspec:31: no . floating literal anymore; put 0 before dot ...sion) >= Gem::Version.new('1.2.0') then ... ^ /usr/lib/ruby/gems/1.8/specifications/archive-tar-minitar-0.5.1.gemspec:31: unterminated string meets end of file WARNING: # -*- encoding: utf-8 -*- Gem::Specification.new do |s| s.name = %q{archive-tar-minitar} s.version = "0.5.1" s.required_rubygems_version = nil if s.respond_to? :required_rubygems_version= s.autorequire = %q{archive/tar/minitar} s.cert_chain = nil s.date = %q{2004-09-27} s.default_executable = %q{minitar} s.description = %q{Archive::Tar::Minitar is a pure-Ruby library and command-line utility that provides the ability to deal with POSIX tar(1) archive files. The implementation is based heavily on Mauricio Fern?ndez's implementation in rpa-base, but has been reorganised to promote reuse in other projects.} s.email = %q{minitar at halostatue.ca} s.executables = ["minitar"] s.extra_rdoc_files = ["README", "ChangeLog", "Install"] s.files = ["bin", "ChangeLog", "Install", "lib", "Rakefile", "README", "tests", "bin/minitar", "lib/archive", "lib/archive/tar", "lib/archive/tar/minitar", "lib/archive/tar/minitar.rb", "lib/archive/tar/minitar/command.rb", "tests/tc_tar.rb", "tests/testall.rb"] s.has_rdoc = true s.homepage = %q{http://rubyforge.org/projects/ruwiki/} s.rdoc_options = ["--title", "Archive::Tar::MiniTar -- A POSIX tarchive library", "--main", "README", "--line-numbers"] s.require_paths = ["lib"] s.required_ruby_version = Gem::Requirement.new(">= 1.8.1") s.rubyforge_project = %q{ruwiki} s.rubygems_version = %q{1.3.1} s.summary = %q{Provides POSIX tarchive management from Ruby programs.} s.test_files = ["tests/testall.rb"] if s.respond_to? :specification_version then current_version = Gem::Specification::CURRENT_SPECIFICATION_VERSION s.specification_version = 1 if Gem::Version.new(Gem::RubyGemsVersion) >= Gem::Version.new('1.2.0') then else end else end end WARNING: /usr/lib/ruby/gems/1.8/specifications/archive-tar-minitar-0.5.1.gemspec:12: invalid multibyte char (UTF-8) /usr/lib/ruby/gems/1.8/specifications/archive-tar-minitar-0.5.1.gemspec:12: syntax error, unexpected tIDENTIFIER, expecting keyword_end ...d heavily on Mauricio Fern?ndez's implementation in rpa-base... ... ^ /usr/lib/ruby/gems/1.8/specifications/archive-tar-minitar-0.5.1.gemspec:31: syntax error, unexpected tFLOAT, expecting keyword_end ...rsion) >= Gem::Version.new('1.2.0') then ... ^ /usr/lib/ruby/gems/1.8/specifications/archive-tar-minitar-0.5.1.gemspec:31: no . floating literal anymore; put 0 before dot ...sion) >= Gem::Version.new('1.2.0') then ... ^ /usr/lib/ruby/gems/1.8/specifications/archive-tar-minitar-0.5.1.gemspec:31: unterminated string meets end of file WARNING: # -*- encoding: utf-8 -*- Gem::Specification.new do |s| s.name = %q{archive-tar-minitar} s.version = "0.5.1" s.required_rubygems_version = nil if s.respond_to? :required_rubygems_version= s.autorequire = %q{archive/tar/minitar} s.cert_chain = nil s.date = %q{2004-09-27} s.default_executable = %q{minitar} s.description = %q{Archive::Tar::Minitar is a pure-Ruby library and command-line utility that provides the ability to deal with POSIX tar(1) archive files. The implementation is based heavily on Mauricio Fern?ndez's implementation in rpa-base, but has been reorganised to promote reuse in other projects.} s.email = %q{minitar at halostatue.ca} s.executables = ["minitar"] s.extra_rdoc_files = ["README", "ChangeLog", "Install"] s.files = ["bin", "ChangeLog", "Install", "lib", "Rakefile", "README", "tests", "bin/minitar", "lib/archive", "lib/archive/tar", "lib/archive/tar/minitar", "lib/archive/tar/minitar.rb", "lib/archive/tar/minitar/command.rb", "tests/tc_tar.rb", "tests/testall.rb"] s.has_rdoc = true s.homepage = %q{http://rubyforge.org/projects/ruwiki/} s.rdoc_options = ["--title", "Archive::Tar::MiniTar -- A POSIX tarchive library", "--main", "README", "--line-numbers"] s.require_paths = ["lib"] s.required_ruby_version = Gem::Requirement.new(">= 1.8.1") s.rubyforge_project = %q{ruwiki} s.rubygems_version = %q{1.3.1} s.summary = %q{Provides POSIX tarchive management from Ruby programs.} s.test_files = ["tests/testall.rb"] if s.respond_to? :specification_version then current_version = Gem::Specification::CURRENT_SPECIFICATION_VERSION s.specification_version = 1 if Gem::Version.new(Gem::RubyGemsVersion) >= Gem::Version.new('1.2.0') then else end else end end ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2010-04-20 21:24 Message: Closing due to lack of response by reporter. Reporter, if you come back, please reopen. ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2010-03-03 23:28 Message: If this is ruby 1.9 why does the directory say 1.8? Did you install this gem with ruby 1.9? ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27917&group_id=126 From noreply at rubyforge.org Wed Apr 21 00:31:51 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 00:31:51 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28091 ] RubyGems Installer Cuts Off Beginning Characters Message-ID: <20100421043151.C8E271858321@rubyforge.org> Bugs item #28091, was opened at 2010-04-14 09:06 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28091&group_id=126 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: A Wilson (aawilson) Assigned to: Nobody (None) Summary: RubyGems Installer Cuts Off Beginning Characters Initial Comment: With ruby-1.9.1 on an mswin32 environment, running setup.rb produces files in the lib\ruby\site_ruby\1.9.1\rubygems which are mostly missing the first four characters of the file. For example, C:\scripting\ruby-1.9.1\lib\ruby\site_ruby\1.9.1\rubygems\commands\list_command.rb has the following for its first line: ire 'rubygems/command' rather than require 'rubygems/command' Inspection of the sources under the rubygems-1.3.6 directory shows that those sources do not have this issue, indicating that the problem has something to do with setup.rb or its dependencies. A workaround for this is to manually copy the rubygems-1.3.6\lib\rubygems directory into ruby-1.9.1\lib\ruby\site_ruby\1.9.1\. ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-20 21:31 Message: RubyGems' setup.rb uses FileUtils#install to do all its copying, so I suspect the problem will exist there. Can you rule out FileUtils as the source of this problem? ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28091&group_id=126 From noreply at rubyforge.org Wed Apr 21 00:32:35 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 00:32:35 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28033 ] gem unpack fails as non-privileged user Message-ID: <20100421043236.33AF01858321@rubyforge.org> Bugs item #28033, was opened at 2010-03-30 07:12 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28033&group_id=126 Category: `gem` commands (other) Group: None >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: Mathieu Sauve-Frankel (kisoku) >Assigned to: Eric Hodel (drbrain) Summary: gem unpack fails as non-privileged user Initial Comment: Rubygems::Installer when called with options[:unpack] will always attempt to create the default gem directory, even when running as a non-privileged user. As Rubygems::Commands::UnpackCommand does not have the --user-install option included, it is not longer possible to unpack gems as a user who does not have write access to @gem_home. See line 136 of lib/rubygems/installer.rb ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-20 21:32 Message: Duplicate of #27872 which is fixed. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28033&group_id=126 From noreply at rubyforge.org Wed Apr 21 00:39:50 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 00:39:50 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28092 ] Errno::EHOSTDOWN: Host is down - connect(2) Message-ID: <20100421043950.3A01F1858328@rubyforge.org> Bugs item #28092, was opened at 2010-04-14 21:40 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28092&group_id=126 Category: `gem` commands (other) Group: v1.3.x >Status: Closed Resolution: None Priority: 3 Submitted By: Eric Peterson (ericdp) >Assigned to: Eric Hodel (drbrain) Summary: Errno::EHOSTDOWN: Host is down - connect(2) Initial Comment: On a Mac v.10.6.3, attempting to update my gems. here's my environment and then the errors I get >ruby -v ruby 1.8.7 (2009-06-08 patchlevel 173) [universal-darwin10.0] >gem -v 1.3.6 >gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.6 - RUBY VERSION: 1.8.7 (2009-06-08 patchlevel 173) [universal-darwin10.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-10 - GEM PATHS: - /Library/Ruby/Gems/1.8 - /Users/eric/.gem/ruby/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/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 >sudo gem update -v Updating installed gems GET http://gems.rubyforge.org/latest_specs.4.8.gz 302 Found HEAD http://gems.rubyforge.org/specs.4.8.gz 302 Found HEAD http://gems.rubyforge.org/yaml 200 OK HEAD http://gems.github.com/specs.4.8.gz 200 OK WARNING: RubyGems 1.2+ index not found for: http://gems.rubyforge.org/ RubyGems will revert to legacy indexes degrading performance. HEAD http://gems.rubyforge.org/Marshal.4.8 200 OK GET http://gems.rubyforge.org/quick/latest_index.rz 302 Found Latest index not found, using quick index GET http://gems.rubyforge.org/quick/index.rz 302 Found ERROR: Falling back to bulk fetch: No quick index found: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/quick/index.rz) Bulk updating Gem source index for: http://gems.rubyforge.org/ GET http://gems.rubyforge.org/Marshal.4.8.Z 302 Found ERROR: Unable to fetch Marshal.4.8.Z: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/Marshal.4.8.Z) GET http://gems.rubyforge.org/Marshal.4.8 302 Found ERROR: Unable to fetch Marshal.4.8: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/Marshal.4.8) GET http://gems.rubyforge.org/yaml.Z 302 Found ERROR: Unable to fetch yaml.Z: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/yaml.Z) GET http://gems.rubyforge.org/yaml 302 Found ERROR: Unable to fetch yaml: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/yaml) ERROR: While executing gem ... (Gem::RemoteSourceException) Error fetching remote gem cache: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/yaml) ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-20 21:39 Message: Apparently you have connectivity issues. I have no way of reproducing this, but I now rescue Errno::EHOSTDOWN when attempting to make an HTTP connection, so hopefully it will raise a friendlier error. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28092&group_id=126 From noreply at rubyforge.org Wed Apr 21 00:40:25 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 00:40:25 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28103 ] Errno::EHOSTDOWN: Host is down - connect(2) Message-ID: <20100421044025.6F1371858322@rubyforge.org> Bugs item #28103, was opened at 2010-04-16 21:29 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28103&group_id=126 Category: `gem` commands (other) Group: v1.3.x >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: Eric Peterson (ericdp) Assigned to: Nobody (None) Summary: Errno::EHOSTDOWN: Host is down - connect(2) Initial Comment: On a Mac v.10.6.3, attempting to update my gems. here's my environment and then the errors I get >ruby -v ruby 1.8.7 (2009-06-08 patchlevel 173) [universal-darwin10.0] >gem -v 1.3.6 >gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.6 - RUBY VERSION: 1.8.7 (2009-06-08 patchlevel 173) [universal-darwin10.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-10 - GEM PATHS: - /Library/Ruby/Gems/1.8 - /Users/eric/.gem/ruby/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/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 >sudo gem update -v Updating installed gems GET http://gems.rubyforge.org/latest_specs.4.8.gz 302 Found HEAD http://gems.rubyforge.org/specs.4.8.gz 302 Found HEAD http://gems.rubyforge.org/yaml 200 OK HEAD http://gems.github.com/specs.4.8.gz 200 OK WARNING: RubyGems 1.2+ index not found for: http://gems.rubyforge.org/ RubyGems will revert to legacy indexes degrading performance. HEAD http://gems.rubyforge.org/Marshal.4.8 200 OK GET http://gems.rubyforge.org/quick/latest_index.rz 302 Found Latest index not found, using quick index GET http://gems.rubyforge.org/quick/index.rz 302 Found ERROR: Falling back to bulk fetch: No quick index found: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/quick/index.rz) Bulk updating Gem source index for: http://gems.rubyforge.org/ GET http://gems.rubyforge.org/Marshal.4.8.Z 302 Found ERROR: Unable to fetch Marshal.4.8.Z: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/Marshal.4.8.Z) GET http://gems.rubyforge.org/Marshal.4.8 302 Found ERROR: Unable to fetch Marshal.4.8: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/Marshal.4.8) GET http://gems.rubyforge.org/yaml.Z 302 Found ERROR: Unable to fetch yaml.Z: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/yaml.Z) GET http://gems.rubyforge.org/yaml 302 Found ERROR: Unable to fetch yaml: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/yaml) ERROR: While executing gem ... (Gem::RemoteSourceException) Error fetching remote gem cache: Errno::EHOSTDOWN: Host is down - connect(2) (http://gems.rubyforge.org/yaml) ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-20 21:40 Message: Duplicate of #28092 ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28103&group_id=126 From noreply at rubyforge.org Wed Apr 21 00:45:39 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 00:45:39 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27944 ] require does not populate Gem.loaded_specs under Ruby 1.9.1. Message-ID: <20100421044539.8CB30185831F@rubyforge.org> Bugs item #27944, was opened at 2010-03-08 17:50 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27944&group_id=126 Category: #gem and #require methods Group: v1.3.x Status: Open Resolution: None >Priority: 1 Submitted By: postmodern (postmodern) Assigned to: Eric Hodel (drbrain) Summary: require does not populate Gem.loaded_specs under Ruby 1.9.1. Initial Comment: I recently upgraded to RubyGems 1.3.6 under Ruby 1.8.7 and 1.9.1. I noticed that *only* under Ruby 1.9.1, the 'require' method would not populate Gem.loaded_specs: >> RUBY_VERSION # => "1.9.1" >> Gem.loaded_specs # => {} >> require 'rack' # => true >> Gem.loaded_specs # => {} ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2010-03-09 00:53 Message: That is because the spec isn't loaded under ruby 1.9.x. That is because ruby 1.9 bypasses rubygems and uses the gem prelude to populate the load path. Inspect $: to see. I don't like gem-prelude, personally, but I don't think it is going to change in ruby 1.9.x. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27944&group_id=126 From noreply at rubyforge.org Wed Apr 21 00:50:34 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 00:50:34 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27896 ] gem install failing because of permission errors Message-ID: <20100421045034.6224E1858309@rubyforge.org> Bugs item #27896, was opened at 2010-02-26 09:12 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27896&group_id=126 >Category: `gem install` command >Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Matt Patterson (fidothe) >Assigned to: Eric Hodel (drbrain) Summary: gem install failing because of permission errors Initial Comment: 1.3.6 seems to have broken the ability to install gems in your home directory... matt$ gem install treetop ERROR: While executing gem ... (Gem::FilePermissionError) You don't have write permissions into the /usr/bin directory. with 1.3.5 and earlier, this command would result in text saying something like "installed in ~/.gem because /usr/bin/ not writable" and a successfull install. ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-20 21:50 Message: --user-install was disabled by default in 1.3.6, but failed to make it into the release notes. You can enable it for yourself via ~/.gemrc, see http://rubygems.rubyforge.org/rubygems-update/Gem/ConfigFile.html ---------------------------------------------------------------------- Comment By: Matt Patterson (fidothe) Date: 2010-02-26 10:21 Message: Explicitly setting $GEM_HOME to /Users/matt/.gem/ruby/1.8 causes 1.3.6's `gem install` to install gems without complaint. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27896&group_id=126 From noreply at rubyforge.org Wed Apr 21 00:50:49 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 00:50:49 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27868 ] rubygems 1.3.6 isn't compatible with rails 2.2.2 Message-ID: <20100421045049.D1EAE1858322@rubyforge.org> Bugs item #27868, was opened at 2010-02-22 05:08 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27868&group_id=126 Category: other Group: v1.3.x >Status: Closed Resolution: Accepted Priority: 3 Submitted By: Wei Jen Lu (weijenlu) Assigned to: Eric Hodel (drbrain) Summary: rubygems 1.3.6 isn't compatible with rails 2.2.2 Initial Comment: I updated rubygems to 1.3.6 and run my app which using rails 2.2.2. My app has exception: /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/gem_dependency.rb:224:in `specification': undefined method `version_requirements=' for # (NoMethodError) from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `inject' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `each' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `inject' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:63:in `locate_plugins' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `map' from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `locate_plugins' ... 34 levels... from /Users/weijen/.gem/ruby/1.8/gems/rails-2.2.2/lib/commands/server.rb:49 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `require' from script/server:3 If I rollback to 1.3.5, then everything is fine. Please help me. thanks. My platform: OS: Mac OS X 10.5.8 Ruby: ruby 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0] Wei Jen ---------------------------------------------------------------------- Comment By: Martin Fencl (arta) Date: 2010-04-06 09:14 Message: Yes, to fix the 'version_requirements=' issue, I checked out patched rubygems (thanks to Adam Meehan, adzap-ar_mailer): svn checkout svn://rubyforge.org/var/svn/rubygems cd trunk ruby setup.rb It is version 1.3.6 and the fix comes at a price of a deprecation warning. martin ---------------------------------------------------------------------- Comment By: David Gaya (myelocyte) Date: 2010-04-06 04:41 Message: I had the same problem. I had two gems with :version specified (will_paginate and rubyist-aasm). I simply removed the version dependence. < config.gem 'rubyist-aasm', :version => '~> 2.0.2', :lib => 'aasm', :source => "http://gems.github.com" > config.gem 'rubyist-aasm', :lib => 'aasm', :source => "http://gems.github.com" < config.gem 'will_paginate', :version => '~> 2.3.11', :source => 'http://gemcutter.org' > config.gem 'will_paginate' ---------------------------------------------------------------------- Comment By: Martin Fencl (arta) Date: 2010-03-21 16:11 Message: I am facing a similar problem, getting this error when running ar_sendmail: ? ~/.c (master)? $ ar_sendmail Unhandled exception undefined method `version_requirements=' for #(NoMethodError): /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/gem_dependency.rb:224:in `specification' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `inject' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `each' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `inject' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:63:in `locate_plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `map' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `locate_plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:27:in `all_plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:22:in `plugins' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:45:in `add_plugin_load_paths' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:269:in `add_plugin_load_paths' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:135:in `process' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `send' /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `run' ./config/environment.rb:19 /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/lib/action_mailer/ar_sendmail.rb:252:in `process_args' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/lib/action_mailer/ar_sendmail.rb:250:in `chdir' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/lib/action_mailer/ar_sendmail.rb:250:in `process_args' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/lib/action_mailer/ar_sendmail.rb:269:in `run' /usr/local/lib/ruby/gems/1.8/gems/adzap-ar_mailer-2.1.6/bin/ar_sendmail:5 /usr/local/bin/ar_sendmail:19:in `load' /usr/local/bin/ar_sendmail:19 Rolling back to rubygems 1.3.5 doesn't help, gemcutter is installed .... My setup: OSX SL, Ruby 1.8.7p174, Rails 2.2.2. I didn't have any issues with ar_sendmail before. Thanks for any help, martin ---------------------------------------------------------------------- Comment By: Thong Kuah (kuahyeow) Date: 2010-03-21 14:06 Message: I had the exact same problem where version_requirement= was broken. After getting rubygems trunk, I now get a deprecation warning "Gem::Dependency#version_requirements= is deprecated and will be removed on or after August 2010. Use Gem::Dependency.new". So that seems to have fixed it. ---------------------------------------------------------------------- Comment By: Robert Berger (rberger) Date: 2010-03-05 01:29 Message: Eric: I svn checked out trunk, and from the top dir of the checkout did sudo ruby setup.rb and then I did a ./script/console from within my 2.2.2 app and it looks like it fixes this problem. I now get a deprecated warning. It looks like the rake commands work in general. ---------------------------------------------------------------------- Comment By: Dylan Fogarty-MacDonald (dylanfm) Date: 2010-02-24 18:51 Message: I'm experiencing the exact same issue. Rubygems 1.3.6 Ruby 1.8.6 (2008-08-08 patchlevel 286) [x86_64-linux] ---------------------------------------------------------------------- Comment By: Wei Jen Lu (weijenlu) Date: 2010-02-24 00:19 Message: I found out this issue is caused by gemcutter be removed. For my system, I use authlogic 1.3.8 and it depend on gemcutter 0.3.0. When I update rubygems, the update process removed gemcutter, then this problem happened. I fixed this problem after reinstall gemcutter. ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2010-02-23 23:03 Message: I think I have this fixed in trunk, but I can't replicate it with an empty rails 2.2.2 app. Can one of you test it out? Check out RubyGems then run: ruby -I/path/to/rubygems/lib script/server or: ruby -I/path/to/rubygems/lib -S rake ---------------------------------------------------------------------- Comment By: Florent Vaucelle (florent) Date: 2010-02-23 02:44 Message: Hi, having the same issue on Fedora 9 with REE 1.8.7, rails 2.2.2 installed. undefined method `version_requirements=' for # ../vendor/rails/railties/lib/rails/gem_dependency.rb:224:in `specification' ../vendor/rails/railties/lib/rails/plugin/locator.rb:81:in `plugins' /opt/ruby-ee-1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `inject' ../vendor/rails/railties/lib/rails/plugin/locator.rb:81:in `each' ../vendor/rails/railties/lib/rails/plugin/locator.rb:81:in `inject' ../vendor/rails/railties/lib/rails/plugin/locator.rb:81:in `plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:63:in `locate_plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:62:in `map' ../vendor/rails/railties/lib/rails/plugin/loader.rb:62:in `locate_plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:27:in `all_plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:22:in `plugins' ../vendor/rails/railties/lib/rails/plugin/loader.rb:45:in `add_plugin_load_paths' ../vendor/rails/railties/lib/initializer.rb:269:in `add_plugin_load_paths' ../vendor/rails/railties/lib/initializer.rb:135:in `process' ../vendor/rails/railties/lib/initializer.rb:112:in `send' ../vendor/rails/railties/lib/initializer.rb:112:in `run' environment.rb:13 /opt/ruby-ee-1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /opt/ruby-ee-1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' vendor/rails/activesupport/lib/active_support/dependencies.rb:153:in `require' vendor/rails/activesupport/lib/active_support/dependencies.rb:521:in `new_constants_in' vendor/rails/activesupport/lib/active_support/dependencies.rb:153:in `require' vendor/rails/railties/lib/tasks/misc.rake:3 /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /opt/ruby-ee-1.8.7/lib/ruby/1.8/monitor.rb:242:in `synchronize' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:607:in `invoke_prerequisites' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in `each' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:596:in `invoke_with_call_chain' /opt/ruby-ee-1.8.7/lib/ruby/1.8/monitor.rb:242:in `synchronize' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /opt/ruby-ee-1.8.7/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /opt/ruby-ee-1.8.7/bin/rake:19:in `load' /opt/ruby-ee-1.8.7/bin/rake:19 ---------------------------------------------------------------------- Comment By: Charles Ju (charlesju) Date: 2010-02-22 18:50 Message: I just updated to rubygems 1.3.6 and my app is on rails 2.2.2. My platform is OSX 10.6.2 and ruby at ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0]. 1.3.5 is fine undefined method `version_requirements=' for :Gem::Dependency /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/gem_dependency.rb:224:in `specification' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `inject' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `each' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `inject' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/locator.rb:81:in `plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:63:in `locate_plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `map' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:62:in `locate_plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:27:in `all_plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:22:in `plugins' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/plugin/loader.rb:45:in `add_plugin_load_paths' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:269:in `add_plugin_load_paths' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:135:in `process' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `send' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in `run' /Users/charlesju/work/SyncManager/config/environment.rb:16 /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `require' Charles ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2010-02-22 18:04 Message: Time to vendor in rubygems? Can that be done? Dan ---------------------------------------------------------------------- Comment By: Vidal Graupera (vgraupera) Date: 2010-02-22 17:40 Message: I hit the exact same problem. My platform is OS X 10.6.2 and ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0] ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27868&group_id=126 From noreply at rubyforge.org Wed Apr 21 00:59:52 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 00:59:52 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27857 ] gem search with version doesn't correctly limit the version Message-ID: <20100421045952.F154B1858323@rubyforge.org> Bugs item #27857, was opened at 2010-02-18 15:07 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27857&group_id=126 >Category: `gem` commands (other) >Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Greg Hazel (ghazel) >Assigned to: Eric Hodel (drbrain) Summary: gem search with version doesn't correctly limit the version Initial Comment: $ gem search ghazel-POpen4 -r --version "= 0.1.4.1" *** REMOTE GEMS *** ghazel-POpen4 (0.1.5.1) Notice it returned a result which is incorrect. 0.1.4.1 is even available: http://gemcutter.org/gems/ghazel-POpen4 ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-20 21:59 Message: --version is only for use with --installed. I've updated --help to show this. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27857&group_id=126 From noreply at rubyforge.org Wed Apr 21 01:38:36 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 01:38:36 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27856 ] gem platform problem Message-ID: <20100421053836.F06CA1D798FC@rubyforge.org> Bugs item #27856, was opened at 2010-02-18 15:02 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27856&group_id=126 >Category: `gem` commands (other) >Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Greg Hazel (ghazel) >Assigned to: Eric Hodel (drbrain) Summary: gem platform problem Initial Comment: Trying to install a gem failed. Here's a little story written in bash: user at host:~/$ gem tumble This command is deprecated, Gemcutter.org is the primary source for gems. user at host:~/$ gem sources *** CURRENT SOURCES *** http://gems.rubyforge.org/ user at host:~/$ gem search ghazel-POpen4 *** LOCAL GEMS *** user at host:~/$ gem search -r ghazel-POpen4 *** REMOTE GEMS *** ghazel-POpen4 (0.1.4.1) user at host:~/$ gem install ghazel-POpen4 ERROR: could not find gem ghazel-POpen4 locally or in a repository The problem here actually was that there was only a "x86-mswin32" gem available, but gem didn't present that information in any way - either in the error message or in the search output. ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-20 22:38 Message: Short gem list output now prints out platforms when there are non-ruby platforms for a version: $ gem search -ra ghazel-POpen4 *** REMOTE GEMS *** ghazel-POpen4 (0.1.5.1 ruby x86-mswin32, 0.1.4.1 x86-mswin32) ---------------------------------------------------------------------- Comment By: Greg Hazel (ghazel) Date: 2010-02-18 15:04 Message: http://rubyforge.org/tracker/index.php? func=detail&aid=21325&group_id=126&atid=575 ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27856&group_id=126 From noreply at rubyforge.org Wed Apr 21 01:40:30 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 01:40:30 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27561 ] --platform is ignored Message-ID: <20100421054030.9E2CB1D798FC@rubyforge.org> Bugs item #27561, was opened at 2009-12-14 09:50 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27561&group_id=126 Category: `gem install` command >Group: v1.3.x >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: Roger Pack (rogerdpack) >Assigned to: Eric Hodel (drbrain) Summary: --platform is ignored Initial Comment: Currently with this command: gem install sys-proctable --platform=non-existent-platform if the platform doesn't exist it defaults back to ruby--essentially ignoring --platform. I was surprised to not receive at warning that platform was being ignored. Thank you for your consideration. -r ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-20 22:40 Message: RubyGems always attempts to install a gem with ruby platform if one is available. If one matching --platform (or your default platform) that one will be chosen over the ruby version. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27561&group_id=126 From noreply at rubyforge.org Wed Apr 21 05:26:27 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 05:26:27 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27960 ] rubygems 1.3.6 can't fetch a gem with a version other than the newest version Message-ID: <20100421092627.862651858309@rubyforge.org> Bugs item #27960, was opened at 2010-03-12 18:21 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27960&group_id=126 Category: `gem` commands (remote behavior) Group: v1.3.x Status: Closed Resolution: Accepted Priority: 3 Submitted By: Eric Hankins (stormsilver) Assigned to: Eric Hodel (drbrain) Summary: rubygems 1.3.6 can't fetch a gem with a version other than the newest version Initial Comment: It seems that with the newest version of rubygems, gem fetch can only fetch the newest version of a gem. If you specify any version other than the newest one in a given repo, it tells you that it cannot find the gem. Here is an example session showing the problem with activesupport, but it happens with any gem. # gem -v 1.3.6 # ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [x86_64-linux] # gem sources *** CURRENT SOURCES *** http://rubygems.org # gem list -r -a activesupport *** REMOTE GEMS *** activesupport (2.3.5, 2.3.4, 2.3.3, 2.3.2, 2.2.3, 2.2.2, 2.1.2, 2.1.1, 2.1.0, 2.0.5, 2.0.4, 2.0.2, 2.0.1, 2.0.0, 1.4.4, 1.4.3, 1.4.2, 1.4.1, 1.4.0, 1.3.1, 1.3.0, 1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0) activesupport-jcache (0.1.0) # gem fetch activesupport -v 2.3.2 ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.2" ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.4" ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.5" Downloaded activesupport-2.3.5 ---------------------------------------------------------------------- >Comment By: James Tucker (raggi) Date: 2010-04-21 09:26 Message: You need to revoke your gemcutter key now Stephen, and generate a new one ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2010-04-21 04:19 Message: Fixed. ---------------------------------------------------------------------- Comment By: Stephen Bannasch (stepheneb) Date: 2010-04-20 03:20 Message: I've confirmed this same bug on MacOS X 10.5.8. The problem occurs using: gem fetch and does not occur using: gem install $ gem list -r -a ci_reporter *** REMOTE GEMS *** ci_reporter (1.6.2, 1.6.1, 1.6.0, 1.5.3, 1.5.2, 1.5.1, 1.5, 1.4, 1.3.5, 1.3.4, 1.3.3, 1.3.2, 1.3.1, 1.3, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2, 1.1, 1.0) $ gem fetch ci_reporter -v '= 1.6.0' ERROR: Could not find ci_reporter in any repository $ sudo gem install ci_reporter -v '= 1.6.0' Successfully installed ci_reporter-1.6.0 1 gem installed /Library/Ruby/Gems/1.8/gems/rdoc-2.5.4/lib/rdoc/ruby_lex.rb:67: warning: parenthesize argument(s) for future version Installing ri documentation for ci_reporter-1.6.0... Building YARD (yri) index for ci_reporter-1.6.0... Installing RDoc documentation for ci_reporter-1.6.0... $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.6 - RUBY VERSION: 1.8.6 (2009-06-08 patchlevel 369) [universal-darwin9.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-9 - GEM PATHS: - /Library/Ruby/Gems/1.8 - /Users/stephen/.gem/ruby/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://rubygems.org", "http://gems.opscode.com/"] - "gemcutter_key" => "12a51589b36ebd91e969de9fedfb5c17" - REMOTE SOURCES: - http://rubygems.org - http://gems.opscode.com/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27960&group_id=126 From noreply at rubyforge.org Wed Apr 21 18:47:04 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 18:47:04 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27960 ] rubygems 1.3.6 can't fetch a gem with a version other than the newest version Message-ID: <20100421224705.08B2F185832B@rubyforge.org> Bugs item #27960, was opened at 2010-03-12 13:21 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27960&group_id=126 Category: `gem` commands (remote behavior) Group: v1.3.x Status: Closed Resolution: Accepted Priority: 3 Submitted By: Eric Hankins (stormsilver) Assigned to: Eric Hodel (drbrain) Summary: rubygems 1.3.6 can't fetch a gem with a version other than the newest version Initial Comment: It seems that with the newest version of rubygems, gem fetch can only fetch the newest version of a gem. If you specify any version other than the newest one in a given repo, it tells you that it cannot find the gem. Here is an example session showing the problem with activesupport, but it happens with any gem. # gem -v 1.3.6 # ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [x86_64-linux] # gem sources *** CURRENT SOURCES *** http://rubygems.org # gem list -r -a activesupport *** REMOTE GEMS *** activesupport (2.3.5, 2.3.4, 2.3.3, 2.3.2, 2.2.3, 2.2.2, 2.1.2, 2.1.1, 2.1.0, 2.0.5, 2.0.4, 2.0.2, 2.0.1, 2.0.0, 1.4.4, 1.4.3, 1.4.2, 1.4.1, 1.4.0, 1.3.1, 1.3.0, 1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0) activesupport-jcache (0.1.0) # gem fetch activesupport -v 2.3.2 ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.2" ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.4" ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.5" Downloaded activesupport-2.3.5 ---------------------------------------------------------------------- Comment By: Stephen Bannasch (stepheneb) Date: 2010-04-21 17:47 Message: Thanks for that warning James, I wondered about that just after I posted the comment. I haven't been able to figure out yet how to revoke the gemcutter key. The key displayed by: gem env -- is not the key stored here: ~/.gem/credentials Which appears to be what is used now: http://rubygems.org/pages/gem_docs It's a bit annoying that: gem env displays the key ;-) I'll keep looking to make sure the key is revoked. Thanks again. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2010-04-21 04:26 Message: You need to revoke your gemcutter key now Stephen, and generate a new one ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2010-04-20 23:19 Message: Fixed. ---------------------------------------------------------------------- Comment By: Stephen Bannasch (stepheneb) Date: 2010-04-19 22:20 Message: I've confirmed this same bug on MacOS X 10.5.8. The problem occurs using: gem fetch and does not occur using: gem install $ gem list -r -a ci_reporter *** REMOTE GEMS *** ci_reporter (1.6.2, 1.6.1, 1.6.0, 1.5.3, 1.5.2, 1.5.1, 1.5, 1.4, 1.3.5, 1.3.4, 1.3.3, 1.3.2, 1.3.1, 1.3, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2, 1.1, 1.0) $ gem fetch ci_reporter -v '= 1.6.0' ERROR: Could not find ci_reporter in any repository $ sudo gem install ci_reporter -v '= 1.6.0' Successfully installed ci_reporter-1.6.0 1 gem installed /Library/Ruby/Gems/1.8/gems/rdoc-2.5.4/lib/rdoc/ruby_lex.rb:67: warning: parenthesize argument(s) for future version Installing ri documentation for ci_reporter-1.6.0... Building YARD (yri) index for ci_reporter-1.6.0... Installing RDoc documentation for ci_reporter-1.6.0... $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.6 - RUBY VERSION: 1.8.6 (2009-06-08 patchlevel 369) [universal-darwin9.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-9 - GEM PATHS: - /Library/Ruby/Gems/1.8 - /Users/stephen/.gem/ruby/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://rubygems.org", "http://gems.opscode.com/"] - "gemcutter_key" => "12a51589b36ebd91e969de9fedfb5c17" - REMOTE SOURCES: - http://rubygems.org - http://gems.opscode.com/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27960&group_id=126 From rick.denatale at gmail.com Wed Apr 21 21:06:53 2010 From: rick.denatale at gmail.com (Rick DeNatale) Date: Wed, 21 Apr 2010 21:06:53 -0400 Subject: [Rubygems-developers] [ANN] ad_agency version 0.1.2 has been released Message-ID: Announcing ad_agency version 0.1.2 An extension to Jeweler for generating announcements One of the facilities I missed in moving from hoe to jeweler was the ability to easily announce new versions of gems. ad_agency fills that hole. Changes: === v0.1.2 2010-04-21 Version bump to 0.1.2 update README === v0.1.1 2010-04-21 update history file again fix merge problem history file generator now writes History.txt history file generator now writes History.txt generate tag for untagged changes from HISTORY Version bump to 0.1.1 added history file generator task refactor for specability fixed spelling of task name === v0.1.0 2010-04-17 change own rakefile to use gem Add documentation, rename raketask Version bump to 0.1.0 Version bump to 0.0.0 Initial commit to ad_agency. From noreply at rubyforge.org Wed Apr 21 23:09:32 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 23:09:32 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27260 ] rubygems 1.3.5 can't install prerelease gems with dependencies Message-ID: <20100422030932.DD8FC185832A@rubyforge.org> Bugs item #27260, was opened at 2009-10-08 18:24 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27260&group_id=126 Category: `gem install` command Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Aslak Helles?y (aslak_hellesoy) >Assigned to: Eric Hodel (drbrain) Summary: rubygems 1.3.5 can't install prerelease gems with dependencies Initial Comment: To reproduce: # Make sure a dependency isn't on your system. Ignore uninstall error if you don't have it. sudo gem uninstall term-ansicolor # cucumber depends on term-ansicolor sudo gem install cucumber --version 0.4.0.rc1 ERROR: Error installing cucumber: cucumber requires term-ansicolor (>= 1.0.3, runtime) # It works fine with: sudo gem install cucumber --version 0.3.104 The error also happens if you run: sudo gem install cucumber --prerelease (I'm planning to release cucumber 0.4.0 in a few days, so this might not let you reproduce it with --prerelease). FYI: cucumber 0.4.0.rc1 was packaged with rubygems 1.3.5 ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-21 20:09 Message: Fixed in 1.3.6 ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27260&group_id=126 From noreply at rubyforge.org Wed Apr 21 23:15:50 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 23:15:50 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27048 ] Cannot use rubygems-update 1.3.5 to update from rubygems 1.2.x installation Message-ID: <20100422031550.4D3F7185832A@rubyforge.org> Bugs item #27048, was opened at 2009-09-04 00:10 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27048&group_id=126 Category: `gem` commands (other) >Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Alain Hoang (hoanga) >Assigned to: Eric Hodel (drbrain) Summary: Cannot use rubygems-update 1.3.5 to update from rubygems 1.2.x installation Initial Comment: Hi, I ran into a case where if had an older installation of Rubygems 1.2.0 then tried to install rubygems-update 1.3.5 and tried to use the update_rubygems command you would get an error like the following: `report-activate-error': Could not find RubyGem session (>= 0) (Gem::LoadError) This makes it impossible to update rubygems from version 1.3.5 of rubygems-update. But it IS possible with version 1.3.4 of rubygems-update. I consider this behavior extremely unfriendly for people who are on rubygems 1.2.x and want to use a provided mechanism for upgrading I believe in the email thread below. Someone else also gets a similar stack trace and their solution was to upgrade from source: http://www.pubbs.net/ruby/200907/68654/ It would be much more preferred to be able to update rubygems via version 1.3.5 (and beyond) of rubygems-update. But what is considered the canonical way to upgrade? ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-21 20:15 Message: Fixed in 1.3.6 ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27048&group_id=126 From noreply at rubyforge.org Wed Apr 21 23:17:25 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 23:17:25 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27327 ] RubyGems does not work properly with upcomming Ruby 1.9.2 Message-ID: <20100422031725.8BEAF185832B@rubyforge.org> Bugs item #27327, was opened at 2009-10-21 06:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27327&group_id=126 Category: #gem and #require methods Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: V?t Ondruch (voxik) >Assigned to: Eric Hodel (drbrain) Summary: RubyGems does not work properly with upcomming Ruby 1.9.2 Initial Comment: With ruby ruby 1.9.2dev (2009-10-07) [i386-mswin32_90], coming from win32-unicode-test branch, RubyGems does not work properly anymore. The problem is in initialization of system_config_path variable. The original code is: system_config_path = begin require 'Win32API' CSIDL_COMMON_APPDATA = 0x0023 path = 0.chr * 260 SHGetFolderPath = Win32API.new 'shell32', 'SHGetFolderPath', 'PLPLP', 'L', :stdcall SHGetFolderPath.call nil, CSIDL_COMMON_APPDATA, nil, 1, path path.strip rescue LoadError '/etc' end but it should be replaced by the following version: system_config_path = begin require 'Win32API' CSIDL_COMMON_APPDATA = 0x0023 path = 0.chr * 260 SHGetFolderPath = Win32API.new 'shell32', 'SHGetFolderPathW', 'PLPLP', 'L', :stdcall SHGetFolderPath.call nil, CSIDL_COMMON_APPDATA, nil, 1, path path.force_encoding('UTF-16LE').encode!('UTF-8') path.strip rescue LoadError '/etc' end i.e. the wide version of SHGetFolderPath should be used. However this code should be probably specific for specific Ruby versions. The problem can be reproduced for example on czech windows XP, where the method SHGetFolderPath returns following string: "c:\Documents and Settings\All Users\Data aplikac?" ("c:\Documents and Settings\All Users\Application data" in EN windows), with US-ASCII encoding, which is completely wrong. ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-21 20:17 Message: AFAIK, this has been fixed. ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-10-21 10:12 Message: Not as easy at you make it look like Win32API is going to be deprecated at 1.9.2 By that time, all should have switched to DL. DL doesn't work with x86_64, at least not for my Windows. There still lot of pieces in Ruby stdlib that depend on Win32API that need to switch to DL. ---------------------------------------------------------------------- Comment By: V?t Ondruch (voxik) Date: 2009-10-21 10:08 Message: > And Luis, why not have one case for 1.8 and one for 1.9 here? I agree with that, why not? ---------------------------------------------------------------------- Comment By: Nikolai Weibull (pcp) Date: 2009-10-21 09:52 Message: Also, use dl instead of Win32API, as Win32API is deprecated. And Luis, why not have one case for 1.8 and one for 1.9 here? ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-10-21 07:52 Message: You're correct. We can't implement Wide characters API as Ruby 1.8 do not support encoding in the same way 1.9 does. A workaround will be use Win32API completely for the encoding translation, but I'm having hard time finding that right now. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27327&group_id=126 From noreply at rubyforge.org Wed Apr 21 23:54:27 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Apr 2010 23:54:27 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27087 ] Rubygems 1.3.5 and Ruby 1.9 breaks hard after require 'rubygems/specification' Message-ID: <20100422035427.572A2185832D@rubyforge.org> Bugs item #27087, was opened at 2009-09-10 13:34 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27087&group_id=126 Category: #gem and #require methods Group: None Status: Open Resolution: None >Priority: 1 Submitted By: Rob Sanheim (rsanheim) Assigned to: Eric Hodel (drbrain) Summary: Rubygems 1.3.5 and Ruby 1.9 breaks hard after require 'rubygems/specification' Initial Comment: Please see the repo: http://github.com/rsanheim/ruby19_rubygems_bug/tree/master The build is here: http://runcoderun.com/rsanheim/ruby19_rubygems_bug The failing build on Ruby 1.9.1 p243: http://runcoderun.com/rsanheim/ruby19_rubygems_bug http://runcoderun.com/rsanheim/ruby19_rubygems_bug/builds/09a9f683fe7848980e10ac7bd2291040ec11ea17/1/ruby_191 Here is the simplest code to illustrate: require 'hoe' gem 'hoe' # these should work puts "about to break 'gem'" require 'rubygems/specification' gem 'hoe' # exception thrown here when it shouldn't be ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-21 20:54 Message: I'm not entirely sure how this is breaking, but require 'rubygems' provides Gem::Specification, so you don't need to require it. The workaround is to not require 'rubygems/specification'. ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2009-09-11 00:30 Message: We've already tracked down the problem. The workaround as described is to remove your manually installed rubygems from 1.9.x. ---------------------------------------------------------------------- Comment By: Adam Salter (aqsalter) Date: 2009-09-10 23:33 Message: Ryan: Sorry about that. I (too) am working on several projects, busy and wanted to throw in my helpful comments... I find problems can get fixed quicker if the devs know how many people are affected. I misunderstood your initial comment: '0 failures out of 4' sounds like no failures, which could certainly be assumed to be a good thing - except we are trying to track down a problem. +1 biting off a much ruder comment and looking to the future with hope and optimism. ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2009-09-10 23:08 Message: Please don't +1. That shit is obnoxious. We don't need to test this against jeweler if we have a much cleaner smaller repro that is standalone. ---------------------------------------------------------------------- Comment By: Adam Salter (aqsalter) Date: 2009-09-10 18:47 Message: +1 please fix... Not exactly 'urgent' but annoying. I raised a bug on the 'jeweler' gem because of this: http://github.com/technicalpickles/jeweler/issues#issue/34 I'm sure that the code i provide there: Rakefile: require 'jeweler' rake -T will trigger issue. ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2009-09-10 13:54 Message: Huh! % sudo gem uninstall rubygems-update % multiruby -rubygems -rrubygems/specification -e 'gem "hoe"' ... TOTAL RESULT = 0 failures out of 4 Passed: 1.9.1-p129, 1.8.7-p72, 1.8.7-p160, 1.8.6-p368 ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2009-09-10 13:53 Message: Easier repro of the warnings: multiruby -rubygems -rrubygems/specification -e 0 and: multiruby -rubygems -rrubygems/specification -e 'gem "hoe"' ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27087&group_id=126 From noreply at rubyforge.org Thu Apr 22 00:00:13 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Apr 2010 00:00:13 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27211 ] gem contents does not show prefix by default Message-ID: <20100422040018.0308B1858317@rubyforge.org> Bugs item #27211, was opened at 2009-09-29 01:39 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27211&group_id=126 Category: None >Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Mamoru Tasaka (mtasaka) >Assigned to: Eric Hodel (drbrain) Summary: gem contents does not show prefix by default Initial Comment: On Fedora, with rubygems-1.3.5-1.fc12.noarch ruby-1.8.6.369-3.fc12.i686 $ gem contents --help shows: ------------------------------------------------ Defaults: --no-lib-only --prefix ------------------------------------------------ However prefix is not shown by default: ------------------------------------------------ $ gem contents --lib-only gettext lib lib/gettext lib/gettext/tools.rb lib/gettext/poparser.rb lib/gettext/textdomain.rb lib/gettext/textdomain_manager.rb ..... ------------------------------------------------ The attached patch seems to work. ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-21 21:00 Message: I have updated the command's behavior to match the documented defaults. ---------------------------------------------------------------------- Comment By: Mamoru Tasaka (mtasaka) Date: 2009-09-29 03:05 Message: Also I think the explanation of $ gem contents: ------------------------------------------------ --[no-]prefix Don't include installed path prefix ------------------------------------------------ is confusing because actually with "--prefix" prefix _is_ shown. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27211&group_id=126 From noreply at rubyforge.org Thu Apr 22 00:06:12 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Apr 2010 00:06:12 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27366 ] gem env command doesn't display ~/.gem as a gem path Message-ID: <20100422040612.8D0BE1858317@rubyforge.org> Bugs item #27366, was opened at 2009-10-28 09:24 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27366&group_id=126 Category: `gem` commands (other) >Group: v1.3.x Status: Open Resolution: None >Priority: 1 Submitted By: Roger Pack (rogerdpack) >Assigned to: Eric Hodel (drbrain) Summary: gem env command doesn't display ~/.gem as a gem path Initial Comment: Currently gem treats ~/.gem as a gem path, however running gem env doesn't hint at that fact. rdp at li49-39:~/dev/downloads/rubygems-1.3.5$ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.5 - RUBY VERSION: 1.8.6 (2009-3-4 patchlevel 287) [i686-linux] - INSTALLATION DIRECTORY: /home/rdp/dev/downloads/rubygems-1.3.5 - RUBY EXECUTABLE: /usr/local/bin/ruby - EXECUTABLE DIRECTORY: /home/rdp/dev/downloads/rubygems-1.3.5/bin - RUBYGEMS PLATFORMS: - ruby - x86-linux - GEM PATHS: - /home/rdp/dev/downloads/rubygems-1.3.5 - GEM CONFIGURATION: ... Thanks! -r ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-21 21:06 Message: Mine shows ~/.gem as well. I cannot reproduce. gem env gemdir is the same as GEM_HOME ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-10-28 10:51 Message: Hm, mine did on Snow Leopard: RubyGems Environment: - RUBYGEMS VERSION: 1.3.5 - RUBY VERSION: 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin10.0.0] - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.8 - RUBY EXECUTABLE: /usr/local/bin/ruby - EXECUTABLE DIRECTORY: /usr/local/bin - RUBYGEMS PLATFORMS: - ruby - x86-darwin-10 - GEM PATHS: - /usr/local/lib/ruby/gems/1.8 - /Users/dberger/.gem/ruby/1.8 ... Interestingly, when I run "gem env gempath" it only shows my .gem path, while "gem env gemdir" only shows the /usr/local/lib path. Intentional? Not sure. Not sure what to make of this yet. Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27366&group_id=126 From noreply at rubyforge.org Thu Apr 22 00:07:18 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Apr 2010 00:07:18 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27431 ] gem install --test fails when using a custom --install-dir Message-ID: <20100422040718.40C021858317@rubyforge.org> Bugs item #27431, was opened at 2009-11-12 17:30 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27431&group_id=126 Category: `gem install` command (extensions) Group: v1.3.x >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: Francis Drake (do_not_bug) >Assigned to: Eric Hodel (drbrain) Summary: gem install --test fails when using a custom --install-dir Initial Comment: gem install --test some.gem and gem install --install-dir /tmp/foo some.gem both work, but combining the options such as gem install --test --install-dir /tmp/foo some.gem fails when trying to load the gem. The workaround for the bug: export GEM_HOME=/tmp/foo && gem check --test some should illustrate the problem. The install command simply does not add the new gem's dir to the list of gemdirs before trying to load it. ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-21 21:07 Message: The --test feature is scheduled to be removed in a future version of RubyGems, so I will not be fixing this. Sorry :( ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27431&group_id=126 From noreply at rubyforge.org Thu Apr 22 00:07:39 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Apr 2010 00:07:39 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27502 ] gem install -t mygem.gem results in " undefined method `passed?' for #< MiniTest::Unit:0x9594a00> " Message-ID: <20100422040739.4BFAF185832D@rubyforge.org> Bugs item #27502, was opened at 2009-12-01 10:25 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27502&group_id=126 Category: `gem install` command >Group: v1.3.x >Status: Closed Resolution: Rejected Priority: 3 Submitted By: Jan Wedekind (wedesoft) Assigned to: Eric Hodel (drbrain) Summary: gem install -t mygem.gem results in "undefined method `passed?' for #<MiniTest::Unit:0x9594a00>" Initial Comment: I am using ruby-1.9.1-p243 and rubygems-1.3.5 under GNU/Linux. # Using Ruby-1.8.6 the experimental gem works: mkdir /tmp/malloc cd /tmp/malloc wget http://www.wedesoft.demon.co.uk/downloads/malloc.tar.bz2 # I've attached it to this bug report as well tar xjf malloc.tar.bz2 make clean all && sudo make install # Using Ruby-1.9.1-p243 running the test suite fails: make clean all RUBY_VERSION=1.9 && make install RUBY_VERSION=1.9 # ... # 3 tests, 11 assertions, 0 failures, 0 errors, 0 skips # ERROR: While executing gem ... (NoMethodError) # undefined method `passed?' for # ---------------------------------------------------------------------- Comment By: Jan Wedekind (wedesoft) Date: 2009-12-01 17:46 Message: Thanks for your swift response ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2009-12-01 16:35 Message: We're going to remove -t support from the install command. We simply can't support it since every test framework works differently. I'll file a new ticket to remove -t. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27502&group_id=126 From noreply at rubyforge.org Thu Apr 22 00:08:08 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Apr 2010 00:08:08 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27453 ] requiring rubygems should not create $HOME/.gem Message-ID: <20100422040808.86BA71858317@rubyforge.org> Bugs item #27453, was opened at 2009-11-18 11:23 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27453&group_id=126 Category: #gem and #require methods >Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Marcus Rueckert (darix) >Assigned to: Eric Hodel (drbrain) Summary: requiring rubygems should not create $HOME/.gem Initial Comment: hi, while debugging one of my ruby apps i noticed that a simple "require 'rubygems'" is enough to get the whole ~/.gem/ directory structure created. i think those directories should only be created when you call the gem cmdline tool. ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-21 21:08 Message: I believe this no longer happens. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27453&group_id=126 From noreply at rubyforge.org Thu Apr 22 00:08:27 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Apr 2010 00:08:27 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27574 ] "gem server" command reads only one directory. Message-ID: <20100422040827.BB462185832A@rubyforge.org> Bugs item #27574, was opened at 2009-12-15 18:45 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27574&group_id=126 Category: `gem server` command Group: None >Status: Closed Resolution: None Priority: 3 Submitted By: Yuki Sonoda (yugui) Assigned to: Nobody (None) >Summary: "gem server" command reads only one directory. Initial Comment: "gem server" command reads specs from only one directory, by default, Gem.dir. The command can take --dir option, however, it does not support two or more directories. I use --user-install for all gems when installing. So I hope the spec loader to be able to read specs from two or more directories and to read from both GEM_HOME and GEM_PATH by default. ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-21 21:08 Message: Dup of #27574 ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27574&group_id=126 From noreply at rubyforge.org Thu Apr 22 00:20:32 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Apr 2010 00:20:32 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27573 ] "gem server" command reads only one directory. Message-ID: <20100422042032.CA1361858317@rubyforge.org> Bugs item #27573, was opened at 2009-12-15 18:45 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27573&group_id=126 Category: `gem server` command >Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Yuki Sonoda (yugui) >Assigned to: Eric Hodel (drbrain) >Summary: "gem server" command reads only one directory. Initial Comment: "gem server" command reads specs from only one directory, by default, Gem.dir. The command can take --dir option, however, it does not support two or more directories. I use --user-install for all gems when installing. So I hope the spec loader to be able to read specs from two or more directories and to read from both GEM_HOME and GEM_PATH by default. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27573&group_id=126 From noreply at rubyforge.org Thu Apr 22 00:30:37 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Apr 2010 00:30:37 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27960 ] rubygems 1.3.6 can't fetch a gem with a version other than the newest version Message-ID: <20100422043037.666781858317@rubyforge.org> Bugs item #27960, was opened at 2010-03-12 13:21 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27960&group_id=126 Category: `gem` commands (remote behavior) Group: v1.3.x Status: Closed Resolution: Accepted Priority: 3 Submitted By: Eric Hankins (stormsilver) Assigned to: Eric Hodel (drbrain) Summary: rubygems 1.3.6 can't fetch a gem with a version other than the newest version Initial Comment: It seems that with the newest version of rubygems, gem fetch can only fetch the newest version of a gem. If you specify any version other than the newest one in a given repo, it tells you that it cannot find the gem. Here is an example session showing the problem with activesupport, but it happens with any gem. # gem -v 1.3.6 # ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [x86_64-linux] # gem sources *** CURRENT SOURCES *** http://rubygems.org # gem list -r -a activesupport *** REMOTE GEMS *** activesupport (2.3.5, 2.3.4, 2.3.3, 2.3.2, 2.2.3, 2.2.2, 2.1.2, 2.1.1, 2.1.0, 2.0.5, 2.0.4, 2.0.2, 2.0.1, 2.0.0, 1.4.4, 1.4.3, 1.4.2, 1.4.1, 1.4.0, 1.3.1, 1.3.0, 1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0) activesupport-jcache (0.1.0) # gem fetch activesupport -v 2.3.2 ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.2" ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.4" ERROR: Could not find activesupport in any repository # gem fetch activesupport -v "=2.3.5" Downloaded activesupport-2.3.5 ---------------------------------------------------------------------- Comment By: Stephen Bannasch (stepheneb) Date: 2010-04-21 23:30 Message: To close the side thread about the visibility of the gemcutter API keyin the: 'gem env' output -- here's what Nick Quaranto wrote: From: Nick Quaranto Subject: how to revoke a gemcutter API key? You can safely remove that line from your `~/.gemrc`. It's not used anymore after several complaints about this very situation, which is why it lives in `~/.gem/credentials` now. ---------------------------------------------------------------------- Comment By: Stephen Bannasch (stepheneb) Date: 2010-04-21 17:47 Message: Thanks for that warning James, I wondered about that just after I posted the comment. I haven't been able to figure out yet how to revoke the gemcutter key. The key displayed by: gem env -- is not the key stored here: ~/.gem/credentials Which appears to be what is used now: http://rubygems.org/pages/gem_docs It's a bit annoying that: gem env displays the key ;-) I'll keep looking to make sure the key is revoked. Thanks again. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2010-04-21 04:26 Message: You need to revoke your gemcutter key now Stephen, and generate a new one ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2010-04-20 23:19 Message: Fixed. ---------------------------------------------------------------------- Comment By: Stephen Bannasch (stepheneb) Date: 2010-04-19 22:20 Message: I've confirmed this same bug on MacOS X 10.5.8. The problem occurs using: gem fetch and does not occur using: gem install $ gem list -r -a ci_reporter *** REMOTE GEMS *** ci_reporter (1.6.2, 1.6.1, 1.6.0, 1.5.3, 1.5.2, 1.5.1, 1.5, 1.4, 1.3.5, 1.3.4, 1.3.3, 1.3.2, 1.3.1, 1.3, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2, 1.1, 1.0) $ gem fetch ci_reporter -v '= 1.6.0' ERROR: Could not find ci_reporter in any repository $ sudo gem install ci_reporter -v '= 1.6.0' Successfully installed ci_reporter-1.6.0 1 gem installed /Library/Ruby/Gems/1.8/gems/rdoc-2.5.4/lib/rdoc/ruby_lex.rb:67: warning: parenthesize argument(s) for future version Installing ri documentation for ci_reporter-1.6.0... Building YARD (yri) index for ci_reporter-1.6.0... Installing RDoc documentation for ci_reporter-1.6.0... $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.6 - RUBY VERSION: 1.8.6 (2009-06-08 patchlevel 369) [universal-darwin9.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-9 - GEM PATHS: - /Library/Ruby/Gems/1.8 - /Users/stephen/.gem/ruby/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://rubygems.org", "http://gems.opscode.com/"] - "gemcutter_key" => "12a51589b36ebd91e969de9fedfb5c17" - REMOTE SOURCES: - http://rubygems.org - http://gems.opscode.com/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27960&group_id=126 From noreply at rubyforge.org Thu Apr 22 00:33:18 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Apr 2010 00:33:18 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27700 ] unable to load gems *ever* if --disable-gems is passed [1.9] Message-ID: <20100422043318.B71B91858317@rubyforge.org> Bugs item #27700, was opened at 2010-01-18 20:37 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27700&group_id=126 Category: #gem and #require methods >Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Roger Pack (rogerdpack) >Assigned to: Eric Hodel (drbrain) Summary: unable to load gems *ever* if --disable-gems is passed [1.9] Initial Comment: Appears that this file fails require 'rubygems' require 'os' in 1.9 if you start Ruby with --disable-gems This was surprising to me, because I assumed that doing a require 'rubygems' would "re-enable" rubygems. Perhaps I am wrong? Thanks. -r ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-21 21:33 Message: Fixed, rubygems now loads custom_require when --disable-gems is set. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27700&group_id=126 From noreply at rubyforge.org Thu Apr 22 10:22:28 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Apr 2010 10:22:28 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28091 ] RubyGems Installer Cuts Off Beginning Characters Message-ID: <20100422142229.004D71858302@rubyforge.org> Bugs item #28091, was opened at 2010-04-14 16:06 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28091&group_id=126 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: A Wilson (aawilson) Assigned to: Nobody (None) Summary: RubyGems Installer Cuts Off Beginning Characters Initial Comment: With ruby-1.9.1 on an mswin32 environment, running setup.rb produces files in the lib\ruby\site_ruby\1.9.1\rubygems which are mostly missing the first four characters of the file. For example, C:\scripting\ruby-1.9.1\lib\ruby\site_ruby\1.9.1\rubygems\commands\list_command.rb has the following for its first line: ire 'rubygems/command' rather than require 'rubygems/command' Inspection of the sources under the rubygems-1.3.6 directory shows that those sources do not have this issue, indicating that the problem has something to do with setup.rb or its dependencies. A workaround for this is to manually copy the rubygems-1.3.6\lib\rubygems directory into ruby-1.9.1\lib\ruby\site_ruby\1.9.1\. ---------------------------------------------------------------------- >Comment By: A Wilson (aawilson) Date: 2010-04-22 14:22 Message: I did a couple of copies with FileUtils.install without any problems, but I wasn't able to track down where setub.rb uses it, so I don't know if there are any options you're using that would affect that. ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2010-04-21 04:31 Message: RubyGems' setup.rb uses FileUtils#install to do all its copying, so I suspect the problem will exist there. Can you rule out FileUtils as the source of this problem? ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28091&group_id=126 From noreply at rubyforge.org Thu Apr 22 11:56:42 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Apr 2010 11:56:42 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27700 ] unable to load gems *ever* if --disable-gems is passed [1.9] Message-ID: <20100422155642.8380F18582EE@rubyforge.org> Bugs item #27700, was opened at 2010-01-19 04:37 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27700&group_id=126 Category: #gem and #require methods Group: v1.3.x Status: Closed Resolution: Accepted Priority: 3 Submitted By: Roger Pack (rogerdpack) Assigned to: Eric Hodel (drbrain) Summary: unable to load gems *ever* if --disable-gems is passed [1.9] Initial Comment: Appears that this file fails require 'rubygems' require 'os' in 1.9 if you start Ruby with --disable-gems This was surprising to me, because I assumed that doing a require 'rubygems' would "re-enable" rubygems. Perhaps I am wrong? Thanks. -r ---------------------------------------------------------------------- >Comment By: Roger Pack (rogerdpack) Date: 2010-04-22 15:56 Message: sweet thanks ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2010-04-22 04:33 Message: Fixed, rubygems now loads custom_require when --disable-gems is set. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27700&group_id=126 From drbrain at segment7.net Thu Apr 22 14:00:13 2010 From: drbrain at segment7.net (Eric Hodel) Date: Thu, 22 Apr 2010 11:00:13 -0700 Subject: [Rubygems-developers] RubyGems 1.3.7.pre.1 - please review! Message-ID: Did I miss anything? I missed: * Requires Ruby 1.8.6 or newer. Download: http://segment7.net/~drbrain/temp/rubygems-update-1.3.7.pre.1.gem New features: * `gem` commands * `gem install` and `gem fetch` now report alternate platforms when a matching one couldn't be found. * `gem contents` --prefix is now the default as specified in --help. Bug #27211 by Mamoru Tasaka. * `gem fetch` can fetch of old versions again. Bug #27960 by Eric Hankins. * `gem query` and friends output now lists platforms. Bug #27856 by Greg Hazel. * `gem server` now allows specification of multiple gem dirs for documentation. Bug #27573 by Yuki Sonoda. * `gem unpack` can unpack gems again. Bug #27872 by Timothy Jones. * `gem unpack` now unpacks remote gems. * --user-install is no longer the default. If you really liked it, see Gem::ConfigFile to learn how to set it by default. (This change was made in 1.3.6) * RubyGems now has platform support for IronRuby. Patch #27951 by Will Green. Bug fixes: * Require rubygems/custom_require if --disable-gem was set. Bug #27700 by Roger Pack. * RubyGems now protects against exceptions being raised by plugins. * rubygems/builder now requires user_interaction. Ruby Bug #1040 by Phillip Toland. * Gem::Dependency support #version_requirements= with a warning. Fix for old Rails versions. Bug #27868 by Wei Jen Lu. * Gem::PackageTask depends on the package dir like the other rake package tasks so dependencies can be hooked up correctly. From noreply at rubyforge.org Thu Apr 22 14:02:10 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Apr 2010 14:02:10 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28091 ] RubyGems Installer Cuts Off Beginning Characters Message-ID: <20100422180211.0C7F018582EE@rubyforge.org> Bugs item #28091, was opened at 2010-04-14 09:06 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28091&group_id=126 >Category: RubyGems installer (setup.rb) >Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: A Wilson (aawilson) >Assigned to: Eric Hodel (drbrain) Summary: RubyGems Installer Cuts Off Beginning Characters Initial Comment: With ruby-1.9.1 on an mswin32 environment, running setup.rb produces files in the lib\ruby\site_ruby\1.9.1\rubygems which are mostly missing the first four characters of the file. For example, C:\scripting\ruby-1.9.1\lib\ruby\site_ruby\1.9.1\rubygems\commands\list_command.rb has the following for its first line: ire 'rubygems/command' rather than require 'rubygems/command' Inspection of the sources under the rubygems-1.3.6 directory shows that those sources do not have this issue, indicating that the problem has something to do with setup.rb or its dependencies. A workaround for this is to manually copy the rubygems-1.3.6\lib\rubygems directory into ruby-1.9.1\lib\ruby\site_ruby\1.9.1\. ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2010-04-22 11:02 Message: It's in lib/rubygems/commands/setup_command.rb ---------------------------------------------------------------------- Comment By: A Wilson (aawilson) Date: 2010-04-22 07:22 Message: I did a couple of copies with FileUtils.install without any problems, but I wasn't able to track down where setub.rb uses it, so I don't know if there are any options you're using that would affect that. ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2010-04-20 21:31 Message: RubyGems' setup.rb uses FileUtils#install to do all its copying, so I suspect the problem will exist there. Can you rule out FileUtils as the source of this problem? ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28091&group_id=126 From drbrain at segment7.net Thu Apr 22 14:02:44 2010 From: drbrain at segment7.net (Eric Hodel) Date: Thu, 22 Apr 2010 11:02:44 -0700 Subject: [Rubygems-developers] RubyGems 1.3.7.pre.1 - please review! In-Reply-To: References: Message-ID: <0ECB3CB2-8F8A-42D9-8D83-975D4F1E72B0@segment7.net> On Apr 22, 2010, at 11:00, Eric Hodel wrote: > Did I miss anything? > > I missed: > > * Requires Ruby 1.8.6 or newer. Scratch that, it was already there. From noreply at rubyforge.org Wed Apr 28 01:02:27 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 28 Apr 2010 01:02:27 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Patches-28149 ] Suggest similar gem names when install fails to find any matches Message-ID: <20100428050227.E7BC11858315@rubyforge.org> Patches item #28149, was opened at 2010-04-27 22:02 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=28149&group_id=126 Category: `gem install` Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Justin Collins (presidentbeef) Assigned to: Nobody (None) Summary: Suggest similar gem names when install fails to find any matches Initial Comment: This patch adds a list of suggestions when a gem fails to install. For example: $ gem install rcvo ERROR: Could not find a valid gem 'rcvo' (>= 0) in any repository Possible alternatives: rcov, rcv Some notes: -Only makes suggestions if domain is not :local -Only makes suggestions if non-default version is specified -No idea how well this works with Unicode Arbitrary design decisions, which can easily be changed: -There is an arbitrary limit (12) on the number of suggestions -If this limit is reached, "..." will be appended to the suggestion list -Underscores and hyphens are ignored -Case is ignored -Because of the two above points, "perfect" matches may not be perfect -If a "perfect" match is found, only that suggestion is returned -Similarity is based on the Damerau?Levenshtein distance algorithm -There is a limit on how "different" the names may be. Currently, this is half of the specified name length. This makes more sense for short search names and less sense for long names -Matches will be made to gems that have the specified gem name as a prefix --Prefix matching is skipping for names with length < 4 ---This is because the lower limit for a name of length 3 will be 1, and thus prefix matching will be reported as a perfect match (0). This is clearer in the code, and could probably be changed Time taken searching for suggestions is naturally dependent on the number of gem names that need to be checked and the size of the specified name. I've found the time tolerable, once I discovered I still had RubyForge and GitHub as gem sources and removed them. All tests appear to be passing. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=28149&group_id=126 From noreply at rubyforge.org Thu Apr 29 14:35:46 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 29 Apr 2010 14:35:46 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28154 ] Gem.binary_mode version test for Ruby 1.9 sets invalid rb:ascii-8bit mode Message-ID: <20100429183546.D089C1858317@rubyforge.org> Bugs item #28154, was opened at 2010-04-29 11:35 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28154&group_id=126 Category: other Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Randall Lucas (rlucas) Assigned to: Nobody (None) Summary: Gem.binary_mode version test for Ruby 1.9 sets invalid rb:ascii-8bit mode Initial Comment: In rubygems.rb, line 344, self.binary_mode makes a check for RUBY_VERSION and sets @binary_mode accordingly. However, it assumes wrongly that the mode "rb:ascii-8bit" is available for all RUBY_VERSION > '1.9'. In fact, that mode does NOT work in Ruby 1.9.0, and was added in 1.9.1. (See support below from Ruby core SVN.) This manifests as a cryptic error: ERROR: While executing gem ... (ArgumentError) illegal access mode rb:ascii-8bit (full debugging error output below). Suggested fix: alter self.binary_mode to check for RUBY_VERSION > '1.9.0' thus: binary_mode ||= RUBY_VERSION > '1.9.0' ? 'rb:ascii-8bit' : 'rb' --- Support from Ruby core SVN for the mode name-change that breaks between 1.9.0 and 1.9.1: >From http://svn.ruby-lang.org/cgi-bin/viewvc.cgi/tags/v1_9_0_5/enc/ascii.c?view=log Revision 13670 - (view) (download) (annotate) - [select for diffs] Modified Wed Oct 10 06:50:33 2007 UTC (2 years, 6 months ago) by akr Original Path: trunk/ascii.c File length: 2408 byte(s) Diff to previous 12376 (colored) * encoding.c (rb_enc_init): don't alias iso-8859-1 to ascii. * ascii.c (OnigEncodingASCII): change the name US-ASCII to ASCII-8BIT. --- version info: $ uname -a Linux arrakis 2.6.18-6-amd64 #1 SMP Sat Feb 20 23:34:55 UTC 2010 x86_64 GNU/Linux $ ruby -v ruby 1.9.0 (2006-06-08) [x86_64-linux] $ sudo gem --debug install rake Exception `NameError' at /usr/local/lib/site_ruby/1.9/rubygems/command_manager.rb:163 - uninitialized constant Gem::Commands::InstallCommand Exception `Gem::LoadError' at /usr/local/lib/site_ruby/1.9/rubygems.rb:778 - Could not find RubyGem test-unit (>= 0) Exception `Gem::LoadError' at /usr/local/lib/site_ruby/1.9/rubygems.rb:778 - Could not find RubyGem sources (> 0.0.1) Exception `ArgumentError' at /usr/local/lib/site_ruby/1.9/rubygems/format.rb:50 - illegal access mode rb:ascii-8bit ERROR: While executing gem ... (ArgumentError) illegal access mode rb:ascii-8bit /usr/local/lib/site_ruby/1.9/rubygems/format.rb:50:in `initialize' /usr/local/lib/site_ruby/1.9/rubygems/format.rb:50:in `Gem::Format#from_file_by_path' /usr/local/lib/site_ruby/1.9/rubygems/installer.rb:118:in `initialize' /usr/local/lib/site_ruby/1.9/rubygems/dependency_installer.rb:257:in `Gem::DependencyInstaller#install' /usr/local/lib/site_ruby/1.9/rubygems/dependency_installer.rb:240:in `Gem::DependencyInstaller#install' /usr/local/lib/site_ruby/1.9/rubygems/commands/install_command.rb:119:in `execute' /usr/local/lib/site_ruby/1.9/rubygems/commands/install_command.rb:116:in `execute' /usr/local/lib/site_ruby/1.9/rubygems/command.rb:258:in `Gem::Command#invoke' /usr/local/lib/site_ruby/1.9/rubygems/command_manager.rb:134:in `process_args' /usr/local/lib/site_ruby/1.9/rubygems/command_manager.rb:104:in `Gem::CommandManager#run' /usr/local/lib/site_ruby/1.9/rubygems/gem_runner.rb:58:in `Gem::GemRunner#run' /usr/bin/gem:21 $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.6 - RUBY VERSION: 1.9.0 (2006-06-08) [x86_64-linux] - INSTALLATION DIRECTORY: /usr/lib/ruby1.9/gems/1.9 - RUBY EXECUTABLE: /usr/bin/ruby1.9 - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - x86_64-linux - GEM PATHS: - /usr/lib/ruby1.9/gems/1.9 - /home/rlucas/.gem/ruby/1.9 - 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=28154&group_id=126 From noreply at rubyforge.org Thu Apr 29 15:10:35 2010 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 29 Apr 2010 15:10:35 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-28155 ] source_index.rb uses 1.9.1 IO#read API under RUBY_VERSION 1.9.0; other 1.9.0 issues Message-ID: <20100429191035.32EC5185831B@rubyforge.org> Bugs item #28155, was opened at 2010-04-29 12:10 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28155&group_id=126 Category: other Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Randall Lucas (rlucas) Assigned to: Nobody (None) Summary: source_index.rb uses 1.9.1 IO#read API under RUBY_VERSION 1.9.0; other 1.9.0 issues Initial Comment: Facially, this looks like an argument TypeError, and manifests thus: /usr/local/lib/site_ruby/1.9/rubygems/source_index.rb:91:in `IO#read': can't convert Hash into Integer (TypeError) In fact, it's a very similar issue to #28154. source_index.rb at line 88 checks RUBY_VERSION < '1.9' before using the new :encoding => 'UTF-8' calling syntax for File.read (IO#read). However, this change didn't make it into Ruby 1.9.0 (see below from core Changelog). Again, the fix here is to check RUBY_VERSION < '1.9.1' Similar errors may be lurking in config_file.rb, defaults.rb, vanidator.rb, and in the tests. --- $ irb1.9 irb(main):001:0> File.open '/tmp/thing.txt' , :encoding => 'UTF-8' TypeError: can't convert Hash into String from (irb):1:in `initialize' from (irb):1:in `Kernel#binding' --- Fri Feb 15 16:22:49 2008 Yukihiro Matsumoto * io.c (open_key_args): allow specifying both :mode and :encoding. --- $ ruby -v ruby 1.9.0 (2006-06-08) [x86_64-linux] $ gem ENV RubyGems Environment: - RUBYGEMS VERSION: 1.3.6 - RUBY VERSION: 1.9.0 (2006-06-08) [x86_64-linux] - INSTALLATION DIRECTORY: /usr/lib/ruby1.9/gems/1.9 - RUBY EXECUTABLE: /usr/bin/ruby1.9 - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - x86_64-linux - GEM PATHS: - /usr/lib/ruby1.9/gems/1.9 - /home/rlucas/.gem/ruby/1.9 - 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=28155&group_id=126 From headius at headius.com Thu Apr 29 19:55:54 2010 From: headius at headius.com (Charles Oliver Nutter) Date: Thu, 29 Apr 2010 18:55:54 -0500 Subject: [Rubygems-developers] Trouble uninstalling gems In-Reply-To: <4BD925DE.4040305@neurogami.com> References: <4BD925DE.4040305@neurogami.com> Message-ID: On Thu, Apr 29, 2010 at 1:23 AM, James Britt wrote: > Here's the problem: ?if you do not pass a bindir value ?then MRI "gem" will > install bins in one place, and jruby 'gem" will use a different place. ?This > keeps different versions from stomping each other. > > But if you want to use a bindir option you're stuck having to use the same > value for all versions of ruby that are parsing gemrc. Yeah, this is a problem. Only one gemrc so only one set of options, but multiple Rubies sharing that. It falls into the same category as sharing gem homes: don't do it...but in this case, there's no other option! > Some possible fixes: > > Have the jruby version of rubygems look for > > ?jruby_install: ? ... > ?jruby_uninstall: ?... > > That is, have jruby-specific values. > > Another is to have the jruby rubygems munge that bndir value by appending > '/jruby' to the end of whatever path is given. > > Or just have a jgemrc file. > > I prefer the more explicit approach, but don't like having ?multiple gemrc > files around if most of the values are going to be the same. > > So I thought perhaps the jruby rubygem could look for ?a jgemrc file and use > that to override any values in gemrc. > > Turns out that was easy to hack in. ?I added some code that duplicates the > current calls that loads /etc/.gemrc and ~/.gemrc, but looks for a .jgemrc > file instead. ?It then merges in the values after the standard config values > are applied. > > Don't know if this is the nicest or best way to keep the different bindir > locations distinct, but it seems to work. I think this may simply be a gap in RubyGems. It already manages repositories well, since even if you --user-install it puts things under a "jruby" or a "ruby" dir depending on RUBY_ENGINE. So it seems like it should do something similar for --bindir, allowing a RUBY_ENGINE-specific config file (like a .gemrc-jruby vs .gemrc), config lines (install-jruby: --bindir versus install: --bindir), or target dir munging (/jruby versus ). I've copied the rubygems dev list on this reply... RubyGem devs: Any thoughts on this? I think we've already decided that sharing a gem root across impls is a bad idea, but since we share a .gemrc we run into the same stomping problems. - Charlie