From noreply at rubyforge.org Fri May 1 00:03:27 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 00:03:27 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25743 ] Gem::Platform#=== bug - returns false when it should return true Message-ID: <20090501040327.18966197859F@rubyforge.org> Bugs item #25743, was opened at 2009-04-30 19:15 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25743&group_id=126 Category: other Group: v1.3.x Status: Open >Resolution: Rejected Priority: 3 Submitted By: Daniel Berger (djberg96) Assigned to: Nobody (None) Summary: Gem::Platform#=== bug - returns false when it should return true Initial Comment: As per IRC, this appears to be a bug: irb(main):005:0> s1 = Gem::Platform.new(['universal', 'darwin', '9']) => # irb(main):006:0> s2 = Gem::Platform.new(['x86', 'darwin', '8']) => # irb(main):007:0> s1 === s2 => false This caused a user on a newer version of OS X some grief when they tried to install sys-proctable, but it was failing because their platform was 'universal-darwin' but the gem is built as 'x86-darwin'. Regards, Dan ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2009-04-30 21:03 Message: Ok, rejected. ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-04-30 20:49 Message: It is the expected behavior. universal-darwin-9 is not compatible with universal-darwin-8 Only universal-darwin is compatible with 9 and 8. Similar with mswin32-60 and mswin32-80 or mswin32-90, since these link to different CRT version, similar thing happens on OSX. At least, that was the last time I've checked. ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-04-30 19:19 Message: And not a minute after I posted this, I think the problem is actually the versions, i.e. 8 vs 9. So, perhaps this is expected behavior after all. Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25743&group_id=126 From noreply at rubyforge.org Fri May 1 00:03:41 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 00:03:41 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25743 ] Gem::Platform#=== bug - returns false when it should return true Message-ID: <20090501040341.F00C218580F5@rubyforge.org> Bugs item #25743, was opened at 2009-04-30 19:15 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25743&group_id=126 Category: other Group: v1.3.x >Status: Closed Resolution: Rejected Priority: 3 Submitted By: Daniel Berger (djberg96) Assigned to: Nobody (None) Summary: Gem::Platform#=== bug - returns false when it should return true Initial Comment: As per IRC, this appears to be a bug: irb(main):005:0> s1 = Gem::Platform.new(['universal', 'darwin', '9']) => # irb(main):006:0> s2 = Gem::Platform.new(['x86', 'darwin', '8']) => # irb(main):007:0> s1 === s2 => false This caused a user on a newer version of OS X some grief when they tried to install sys-proctable, but it was failing because their platform was 'universal-darwin' but the gem is built as 'x86-darwin'. Regards, Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-04-30 21:03 Message: Ok, rejected. ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-04-30 20:49 Message: It is the expected behavior. universal-darwin-9 is not compatible with universal-darwin-8 Only universal-darwin is compatible with 9 and 8. Similar with mswin32-60 and mswin32-80 or mswin32-90, since these link to different CRT version, similar thing happens on OSX. At least, that was the last time I've checked. ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-04-30 19:19 Message: And not a minute after I posted this, I think the problem is actually the versions, i.e. 8 vs 9. So, perhaps this is expected behavior after all. Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25743&group_id=126 From noreply at rubyforge.org Fri May 1 01:26:15 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 01:26:15 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25677 ] Gem::Specification#validate fails if homepage is unspecified Message-ID: <20090501052615.3DE8C1978513@rubyforge.org> Bugs item #25677, was opened at 2009-04-25 08:09 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25677&group_id=126 Category: other Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Mike Burrows (asplake) Assigned to: Nobody (None) Summary: Gem::Specification#validate fails if homepage is unspecified Initial Comment: rubygems/specification.rb:886: unless homepage.empty? or homepage =~ /\A[a-z][a-z\d+.-]*:/i then The above line fails with undefined method `empty?' for nil:NilClass if homepage is nil, and the helpful "no #{attribute} specified" warning a few lines later is never reached. Perhaps someone assumed that everyone has #empty? defined on NilClass? I worked around this problem (and identified my missing homepage setting) by doing just that in my Rakefile. Thank you for an otherwise wonderful thing! Mike RubyGems Environment: - RUBYGEMS VERSION: 1.3.2 - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [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/asplake/.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 - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- Comment By: Mike Burrows (asplake) Date: 2009-05-01 05:26 Message: Thanks, looks to me like the right change to make. URI.parse can be improved independently (via sporkmonger's Addressable::URI perhaps). ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-01 02:07 Message: BTW, the downside of my suggested patch is that URI.parse appears to be pretty liberal with what's legal and what isn't (including empty strings), compared to the current regex. Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-04-30 23:00 Message: Proposed change: --- specification.rb 2009-04-30 16:48:09.000000000 -0600 +++ specification.new 2009-04-30 16:47:56.000000000 -0600 @@ -883,9 +883,13 @@ '"FIXME" or "TODO" is not a summary' end - unless homepage.empty? or homepage =~ /\A[a-z][a-z\d+.-]*:/i then - raise Gem::InvalidSpecificationException, - "\#{homepage}\ is not a URI" + if homepage + begin + URI.parse(homepage) + rescue URI::InvalidURIError + raise Gem::InvalidSpecificationException, + "#{homepage} is not a valid URI" + end end # Warnings ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25677&group_id=126 From noreply at rubyforge.org Fri May 1 05:26:10 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 05:26:10 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25734 ] Gem::Ext::RakeBuilder fails under windows if ENV['rake'] not set Message-ID: <20090501092610.7F6F918581EB@rubyforge.org> Bugs item #25734, was opened at 2009-04-30 00:05 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25734&group_id=126 Category: `gem install` command Group: None >Status: Open Resolution: Accepted Priority: 3 Submitted By: Paolo Angelini (pablito) Assigned to: James Tucker (raggi) Summary: Gem::Ext::RakeBuilder fails under windows if ENV['rake'] not set Initial Comment: line 22 of rake_builder.rb builds a rake command and defaults to Gem.bin_path('rake') if ENV['rake'] is not set: cmd = ENV['rake'] || Gem.bin_path('rake') rescue Gem.default_exec_format % 'rake' unfortunately under windows Gem.bin_path('rake') is not an executable file and line 26: run cmd, results raise an error: 'C:/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake' is not recognized as an int ernal or external command, operable program or batch file. (see also this thread Including Gem.ruby in the command solves the problem: bin_path = /mswin/ =~ RUBY_PLATFORM ? "#{Gem.ruby} #{Gem.bin_path('rake')}" : Gem.bin_path('rake') cmd = ENV['rake'] || bin_path rescue Gem.default_exec_format % 'rake' I didn't file a patch because I couldn't test this under linux and I wanted to avoid any regression bug this is my environment RubyGems Environment: - RUBYGEMS VERSION: 1.3.2 - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] - INSTALLATION DIRECTORY: c:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: c:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: c:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - c:/ruby/lib/ruby/gems/1.8 - C:/Documents and Settings/Administrator/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- >Comment By: James Tucker (raggi) Date: 2009-05-01 09:26 Message: Luis, good catch! ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-04-30 17:59 Message: James, take in consideration that "Gem.ruby" could be inside a PATH with spaces and it need to be handled properly. The same applies to rake. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-04-30 12:10 Message: Fixed in r2180. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-04-30 12:05 Message: What is required for normal operation on most builds should be: "#{Gem.ruby} -rubygems #{Gem.bin_path('rake')}" ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-04-30 00:19 Message: The problem I see is that RakeBuild should use Gem.ruby + Gem.bin_path('rake') and not rake directly. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25734&group_id=126 From noreply at rubyforge.org Fri May 1 05:43:20 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 05:43:20 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25734 ] Gem::Ext::RakeBuilder fails under windows if ENV['rake'] not set Message-ID: <20090501094320.8F4D318580FF@rubyforge.org> Bugs item #25734, was opened at 2009-04-30 00:05 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25734&group_id=126 Category: `gem install` command Group: None Status: Open Resolution: Accepted Priority: 3 Submitted By: Paolo Angelini (pablito) Assigned to: James Tucker (raggi) Summary: Gem::Ext::RakeBuilder fails under windows if ENV['rake'] not set Initial Comment: line 22 of rake_builder.rb builds a rake command and defaults to Gem.bin_path('rake') if ENV['rake'] is not set: cmd = ENV['rake'] || Gem.bin_path('rake') rescue Gem.default_exec_format % 'rake' unfortunately under windows Gem.bin_path('rake') is not an executable file and line 26: run cmd, results raise an error: 'C:/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake' is not recognized as an int ernal or external command, operable program or batch file. (see also this thread Including Gem.ruby in the command solves the problem: bin_path = /mswin/ =~ RUBY_PLATFORM ? "#{Gem.ruby} #{Gem.bin_path('rake')}" : Gem.bin_path('rake') cmd = ENV['rake'] || bin_path rescue Gem.default_exec_format % 'rake' I didn't file a patch because I couldn't test this under linux and I wanted to avoid any regression bug this is my environment RubyGems Environment: - RUBYGEMS VERSION: 1.3.2 - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] - INSTALLATION DIRECTORY: c:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: c:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: c:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - c:/ruby/lib/ruby/gems/1.8 - C:/Documents and Settings/Administrator/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- >Comment By: James Tucker (raggi) Date: 2009-05-01 09:43 Message: Gem.ruby already escapes correctly. I shall correct in Gem.bin_path. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-05-01 09:26 Message: Luis, good catch! ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-04-30 17:59 Message: James, take in consideration that "Gem.ruby" could be inside a PATH with spaces and it need to be handled properly. The same applies to rake. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-04-30 12:10 Message: Fixed in r2180. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-04-30 12:05 Message: What is required for normal operation on most builds should be: "#{Gem.ruby} -rubygems #{Gem.bin_path('rake')}" ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-04-30 00:19 Message: The problem I see is that RakeBuild should use Gem.ruby + Gem.bin_path('rake') and not rake directly. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25734&group_id=126 From noreply at rubyforge.org Fri May 1 05:56:54 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 05:56:54 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25734 ] Gem::Ext::RakeBuilder fails under windows if ENV['rake'] not set Message-ID: <20090501095655.265DF1D787E1@rubyforge.org> Bugs item #25734, was opened at 2009-04-30 00:05 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25734&group_id=126 Category: `gem install` command Group: None >Status: Closed Resolution: Accepted Priority: 3 Submitted By: Paolo Angelini (pablito) Assigned to: James Tucker (raggi) Summary: Gem::Ext::RakeBuilder fails under windows if ENV['rake'] not set Initial Comment: line 22 of rake_builder.rb builds a rake command and defaults to Gem.bin_path('rake') if ENV['rake'] is not set: cmd = ENV['rake'] || Gem.bin_path('rake') rescue Gem.default_exec_format % 'rake' unfortunately under windows Gem.bin_path('rake') is not an executable file and line 26: run cmd, results raise an error: 'C:/Ruby/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake' is not recognized as an int ernal or external command, operable program or batch file. (see also this thread Including Gem.ruby in the command solves the problem: bin_path = /mswin/ =~ RUBY_PLATFORM ? "#{Gem.ruby} #{Gem.bin_path('rake')}" : Gem.bin_path('rake') cmd = ENV['rake'] || bin_path rescue Gem.default_exec_format % 'rake' I didn't file a patch because I couldn't test this under linux and I wanted to avoid any regression bug this is my environment RubyGems Environment: - RUBYGEMS VERSION: 1.3.2 - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] - INSTALLATION DIRECTORY: c:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: c:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: c:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - c:/ruby/lib/ruby/gems/1.8 - C:/Documents and Settings/Administrator/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- >Comment By: James Tucker (raggi) Date: 2009-05-01 09:56 Message: Gem.bin_path now escapes paths with spaces in r2183. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-05-01 09:43 Message: Gem.ruby already escapes correctly. I shall correct in Gem.bin_path. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-05-01 09:26 Message: Luis, good catch! ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-04-30 17:59 Message: James, take in consideration that "Gem.ruby" could be inside a PATH with spaces and it need to be handled properly. The same applies to rake. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-04-30 12:10 Message: Fixed in r2180. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-04-30 12:05 Message: What is required for normal operation on most builds should be: "#{Gem.ruby} -rubygems #{Gem.bin_path('rake')}" ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-04-30 00:19 Message: The problem I see is that RakeBuild should use Gem.ruby + Gem.bin_path('rake') and not rake directly. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25734&group_id=126 From noreply at rubyforge.org Fri May 1 12:00:11 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 12:00:11 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25748 ] Use of --source option seems to break default --include-dependencies option Message-ID: <20090501160014.EC46D1858201@rubyforge.org> Bugs item #25748, was opened at 01/05/2009 18:00 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25748&group_id=126 Category: `gem install` command Group: None Status: Open Resolution: None Priority: 3 Submitted By: S?bastien Luquet (sebastienluquet) Assigned to: Nobody (None) Summary: Use of --source option seems to break default --include-dependencies option Initial Comment: RubyGems Environment: - RUBYGEMS VERSION: 1.3.2 - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [i386-mswin32] - INSTALLATION DIRECTORY: H:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: H:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: H:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - H:/ruby/lib/ruby/gems/1.8 - H:/Documents and Settings/seb/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://gems.rubyforge.org", "http://gems.rubyonrails.org", "http://gems.github.com"] - "gem" => "--no-rdoc --no-ri" - REMOTE SOURCES: - http://gems.rubyforge.org - http://gems.rubyonrails.org - http://gems.github.com rcov should not be installed (dependency of jscruggs-metric_fu) gem install jscruggs-metric_fu --source http://gems.github.com --debug Exception `NameError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygem /command_manager.rb:161 - uninitialized constant Gem::Commands::InstallCommand Exception `Gem::LoadError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:805 - Could not find RubyGem test-unit (>= 0) Exception `Errno::EEXIST' at H:/ruby/lib/ruby/1.8/fileutils.rb:243 - File exists - H:\Documents and Settings\seb/.gem/specs/gems.github.com%80 Exception `IOError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygems/format.rb:50 - closed stream Exception `Errno::EEXIST' at H:/ruby/lib/ruby/1.8/fileutils.rb:243 - File exists - H:/ruby/lib/ruby/gems/1.8 Exception `Gem::InstallError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygem /installer.rb:255 - jscruggs-metric_fu requires rcov (> 0.8.1, runtime) ERROR: Error installing jscruggs-metric_fu: jscruggs-metric_fu requires rcov (> 0.8.1, runtime) gem install jscruggs-metric_fu works ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25748&group_id=126 From noreply at rubyforge.org Fri May 1 18:42:32 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 18:42:32 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25516 ] gem cleanup still dysfunctional in 1.3.2 Message-ID: <20090501224232.96A81197858B@rubyforge.org> Bugs item #25516, was opened at 2009-04-16 16:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25516&group_id=126 Category: `gem` commands (other) Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Brett Eisenberg (brett) >Assigned to: Eric Hodel (drbrain) Summary: gem cleanup still dysfunctional in 1.3.2 Initial Comment: [ruby at rubygems]:~% gem cleanup Cleaning up installed gems... Attempting to uninstall tzinfo-0.3.12 Unable to uninstall tzinfo-0.3.12: Gem::InstallError: cannot uninstall, check `gem list -d tzinfo` [ruby at rubygems]:~% gem list -d tzinfo *** LOCAL GEMS *** tzinfo (0.3.13, 0.3.12) Author: Philip Ross Rubyforge: http://rubyforge.org/projects/tzinfo Homepage: http://tzinfo.rubyforge.org/ Installed at (0.3.13): /Users/ruby/.gem/ruby/1.8 (0.3.12): /Users/ruby/.gem/ruby/1.8 Daylight-savings aware timezone library [ruby at rubygems]:~% gem uninstall tzinfo -v '= 0.3.12' Successfully uninstalled tzinfo-0.3.12 ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2009-05-01 15:42 Message: Fixed. ---------------------------------------------------------------------- Comment By: Brett Eisenberg (brett) Date: 2009-04-19 16:46 Message: [ruby at rubygems]:~% gem cleanup --debug Exception `NameError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:161 - uninitialized constant Gem::Commands::CleanupCommand Cleaning up installed gems... Attempting to uninstall memcache-client-1.7.1 Exception `Gem::InstallError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76 - cannot uninstall, check `gem list -d memcache-client` Unable to uninstall memcache-client-1.7.1: Gem::InstallError: cannot uninstall, check `gem list -d memcache-client` Attempting to uninstall ruby-openid-2.1.2 Exception `Gem::InstallError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76 - cannot uninstall, check `gem list -d ruby-openid` Unable to uninstall ruby-openid-2.1.2: Gem::InstallError: cannot uninstall, check `gem list -d ruby-openid` Attempting to uninstall rspec-1.2.2 Exception `Gem::InstallError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76 - cannot uninstall, check `gem list -d rspec` Unable to uninstall rspec-1.2.2: Gem::InstallError: cannot uninstall, check `gem list -d rspec` Attempting to uninstall fastthread-1.0.6 Exception `Gem::InstallError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76 - cannot uninstall, check `gem list -d fastthread` Unable to uninstall fastthread-1.0.6: Gem::InstallError: cannot uninstall, check `gem list -d fastthread` Attempting to uninstall json-1.1.3 Exception `Gem::InstallError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76 - cannot uninstall, check `gem list -d json` Unable to uninstall json-1.1.3: Gem::InstallError: cannot uninstall, check `gem list -d json` Attempting to uninstall cucumber-0.2.3 Exception `Gem::InstallError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76 - cannot uninstall, check `gem list -d cucumber` Unable to uninstall cucumber-0.2.3: Gem::InstallError: cannot uninstall, check `gem list -d cucumber` Attempting to uninstall hoe-1.12.1 Exception `Gem::InstallError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76 - cannot uninstall, check `gem list -d hoe` Unable to uninstall hoe-1.12.1: Gem::InstallError: cannot uninstall, check `gem list -d hoe` Attempting to uninstall thoughtbot-factory_girl-1.2.0 Exception `Gem::InstallError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76 - cannot uninstall, check `gem list -d thoughtbot-factory_girl` Unable to uninstall thoughtbot-factory_girl-1.2.0: Gem::InstallError: cannot uninstall, check `gem list -d thoughtbot-factory_girl` Attempting to uninstall rake-compiler-0.4.0 Exception `Gem::InstallError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:76 - cannot uninstall, check `gem list -d rake-compiler` Unable to uninstall rake-compiler-0.4.0: Gem::InstallError: cannot uninstall, check `gem list -d rake-compiler` Clean Up Complete ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-04-19 14:46 Message: Can you try running the exact same command with debug information turned on? gem cleanup --debug ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25516&group_id=126 From noreply at rubyforge.org Fri May 1 19:34:54 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 19:34:54 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25555 ] gem uninstall does not handle binaries in non-system locations Message-ID: <20090501233454.BAC71197857C@rubyforge.org> Bugs item #25555, was opened at 2009-04-20 11:15 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25555&group_id=126 Category: `gem` commands (other) >Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Brett Eisenberg (brett) >Assigned to: Eric Hodel (drbrain) Summary: gem uninstall does not handle binaries in non-system locations Initial Comment: [ruby at rubygems]:~% gem uninstall aws-s3 Remove executables: s3sh in addition to the gem? [Yn] Y ERROR: While executing gem ... (Gem::FilePermissionError) You don't have write permissions into the /opt/local/bin directory. [ruby at rubygems]:~% which s3sh /Users/ruby/.gem/ruby/1.8/bin/s3sh -- [ruby at rubygems]:~% gem uninstall aws-s3 --debug Exception `NameError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:161 - uninitialized constant Gem::Commands::UninstallCommand Remove executables: s3sh in addition to the gem? [Yn] Y Exception `Gem::FilePermissionError' at /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:154 - You don't have write permissions into the /opt/local/bin directory. ERROR: While executing gem ... (Gem::FilePermissionError) You don't have write permissions into the /opt/local/bin directory. /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:154:in `remove_executables' /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:109:in `uninstall_gem' /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:109:in `each' /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:109:in `uninstall_gem' /opt/local/lib/ruby/site_ruby/1.8/rubygems/uninstaller.rb:95:in `uninstall' /opt/local/lib/ruby/site_ruby/1.8/rubygems/commands/uninstall_command.rb:73:in `execute' /opt/local/lib/ruby/site_ruby/1.8/rubygems/commands/uninstall_command.rb:71:in `each' /opt/local/lib/ruby/site_ruby/1.8/rubygems/commands/uninstall_command.rb:71:in `execute' /opt/local/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke' /opt/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args' /opt/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run' /opt/local/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run' /opt/local/bin/gem:21 ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2009-05-01 16:34 Message: Fixed. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25555&group_id=126 From noreply at rubyforge.org Fri May 1 19:36:50 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 19:36:50 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25564 ] Time.today not working with 1.3.2 Message-ID: <20090501233650.9B1F61678211@rubyforge.org> Bugs item #25564, was opened at 2009-04-20 23:30 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25564&group_id=126 Category: other Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Emanuele Vicentini (emanuelev) >Assigned to: Eric Hodel (drbrain) Summary: Time.today not working with 1.3.2 Initial Comment: $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.2 - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [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/emanuele/.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 - REMOTE SOURCES: - http://gems.rubyforge.org/ Running the following gives problem: $ ruby -rubygems -e 'puts Time.today' /Library/Ruby/Site/1.8/rubygems/specification.rb:16:in `today': undefined local variable or method `location_of_caller' for Time:Class (NameError) from -e:1 Noted this even on an Ubuntu GNU/Linux box with Ruby 1.8.7. On both machines there are some gems (Rails, Rake, Rack and many others), but the load paths do not seem to be messed up: $ ruby -rubygems -e 'puts Time.today rescue nil; puts $:' /Library/Ruby/Site/1.8 /Library/Ruby/Site/1.8/powerpc-darwin9.0 /Library/Ruby/Site/1.8/universal-darwin9.0 /Library/Ruby/Site /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8 /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/powerpc-darwin9.0 /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin9.0 . ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2009-05-01 16:36 Message: I decided to remove Time.today, since there's no way to override it before RubyGems loads. Sorry. ---------------------------------------------------------------------- Comment By: Luke Ivers (technodolt1) Date: 2009-04-27 11:52 Message: Hey, I fixed this on my local install by changing the line in specification.rb to use Gem.location_of_caller instead of just location_of_caller in the Time.today function. Given that I'm using MacOS and the default install of Ruby, and also that I'm using an application (Tracks, specifically) which uses this function, I figured it'd be better to fix the bug rubygems 1.3.2 for now. Also going to report this to Tracks so they know to take out the deprecated code if they want this to work with Rubygems on 1.8.* ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-04-24 17:51 Message: Since Gem::Specification is always loaded with RubyGems and Time.today is defined in it, Time.today isn't easily overrideable to avoid the warning (its check for definition is useless). I think I should remove it outright. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-04-24 07:32 Message: It's not been removed, but it's broken due to a missing method in Kernel. Possibly worth noting that Kernel#location_of_caller move to Gem was not in the ChangeLog afaics. Diff: http://pastie.textmate.org/private/w2qtrafnu6s3zizkoolba ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-04-22 04:47 Message: Was under deprecation warning between 1.x and 1.3, now it got removed. ---------------------------------------------------------------------- Comment By: Emanuele Vicentini (emanuelev) Date: 2009-04-21 23:03 Message: Right; that's why I expected it to show a warning, not to raise a NameError exception. Anyway, I agree with you that it is a no-priority issue. Have a nice day. ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-04-21 06:03 Message: Time.today has been deprecated. See the release notes. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25564&group_id=126 From noreply at rubyforge.org Fri May 1 19:40:06 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 19:40:06 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25748 ] Use of --source option seems to break default --include-dependencies option Message-ID: <20090501234006.A71A818580FF@rubyforge.org> Bugs item #25748, was opened at 2009-05-01 09:00 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25748&group_id=126 Category: `gem install` command >Group: v1.3.x >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: S?bastien Luquet (sebastienluquet) >Assigned to: Eric Hodel (drbrain) Summary: Use of --source option seems to break default --include-dependencies option Initial Comment: RubyGems Environment: - RUBYGEMS VERSION: 1.3.2 - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [i386-mswin32] - INSTALLATION DIRECTORY: H:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: H:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: H:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - H:/ruby/lib/ruby/gems/1.8 - H:/Documents and Settings/seb/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://gems.rubyforge.org", "http://gems.rubyonrails.org", "http://gems.github.com"] - "gem" => "--no-rdoc --no-ri" - REMOTE SOURCES: - http://gems.rubyforge.org - http://gems.rubyonrails.org - http://gems.github.com rcov should not be installed (dependency of jscruggs-metric_fu) gem install jscruggs-metric_fu --source http://gems.github.com --debug Exception `NameError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygem /command_manager.rb:161 - uninitialized constant Gem::Commands::InstallCommand Exception `Gem::LoadError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:805 - Could not find RubyGem test-unit (>= 0) Exception `Errno::EEXIST' at H:/ruby/lib/ruby/1.8/fileutils.rb:243 - File exists - H:\Documents and Settings\seb/.gem/specs/gems.github.com%80 Exception `IOError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygems/format.rb:50 - closed stream Exception `Errno::EEXIST' at H:/ruby/lib/ruby/1.8/fileutils.rb:243 - File exists - H:/ruby/lib/ruby/gems/1.8 Exception `Gem::InstallError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygem /installer.rb:255 - jscruggs-metric_fu requires rcov (> 0.8.1, runtime) ERROR: Error installing jscruggs-metric_fu: jscruggs-metric_fu requires rcov (> 0.8.1, runtime) gem install jscruggs-metric_fu works ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2009-05-01 16:40 Message: There's no rcov gem on the github source, so I don't know why you expect this to work. The documentation states: --source URL Use URL as the remote source for gems Which may not be clear, but implies that the flag overrides the default sources rather than appends to them. If you can think of better wording, I will be glad to change it. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25748&group_id=126 From noreply at rubyforge.org Fri May 1 19:49:10 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 19:49:10 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25741 ] Gem::Specification#installation_path should raise a proper exception Message-ID: <20090501234910.5E76718580F9@rubyforge.org> Bugs item #25741, was opened at 2009-04-30 15:42 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25741&group_id=126 Category: other Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 2 Submitted By: Daniel Berger (djberg96) >Assigned to: Eric Hodel (drbrain) Summary: Gem::Specification#installation_path should raise a proper exception Initial Comment: Hi, The Gem::Specification#installation_path is a public method, but it isn't meant for direct use in a .gemspec file. If you try to call that method directly in a .gemspec file it will result in this error: /usr/local/lib/ruby/site_ruby/1.8/rubygems/specification.rb:624:in `dirname': can't convert nil into String (TypeError) Looking at the source we can see why: def installation_path File.expand_path(File.dirname(File.dirname(@loaded_from))) end The @loaded_from instance variable is nil, so it blows up. Instead, this should raise a proper exception of some sort to let people (like me) know that it isn't meant for direct use, but for inspection after installation. Regards, Dan ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2009-05-01 16:49 Message: Fixed, now raises Gem::Exception with the hopefully clear-enough exception 'spec a-1 is not from an installed gem' ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25741&group_id=126 From noreply at rubyforge.org Fri May 1 19:55:37 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 19:55:37 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25677 ] Gem::Specification#validate fails if homepage is unspecified Message-ID: <20090501235537.CA3A0197858A@rubyforge.org> Bugs item #25677, was opened at 2009-04-25 01:09 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25677&group_id=126 Category: other Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Mike Burrows (asplake) >Assigned to: Eric Hodel (drbrain) Summary: Gem::Specification#validate fails if homepage is unspecified Initial Comment: rubygems/specification.rb:886: unless homepage.empty? or homepage =~ /\A[a-z][a-z\d+.-]*:/i then The above line fails with undefined method `empty?' for nil:NilClass if homepage is nil, and the helpful "no #{attribute} specified" warning a few lines later is never reached. Perhaps someone assumed that everyone has #empty? defined on NilClass? I worked around this problem (and identified my missing homepage setting) by doing just that in my Rakefile. Thank you for an otherwise wonderful thing! Mike RubyGems Environment: - RUBYGEMS VERSION: 1.3.2 - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [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/asplake/.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 - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2009-05-01 16:55 Message: I decided on a simpler change of adding a nil check to homepage. Fixed. ---------------------------------------------------------------------- Comment By: Mike Burrows (asplake) Date: 2009-04-30 22:26 Message: Thanks, looks to me like the right change to make. URI.parse can be improved independently (via sporkmonger's Addressable::URI perhaps). ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-04-30 19:07 Message: BTW, the downside of my suggested patch is that URI.parse appears to be pretty liberal with what's legal and what isn't (including empty strings), compared to the current regex. Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-04-30 16:00 Message: Proposed change: --- specification.rb 2009-04-30 16:48:09.000000000 -0600 +++ specification.new 2009-04-30 16:47:56.000000000 -0600 @@ -883,9 +883,13 @@ '"FIXME" or "TODO" is not a summary' end - unless homepage.empty? or homepage =~ /\A[a-z][a-z\d+.-]*:/i then - raise Gem::InvalidSpecificationException, - "\#{homepage}\ is not a URI" + if homepage + begin + URI.parse(homepage) + rescue URI::InvalidURIError + raise Gem::InvalidSpecificationException, + "#{homepage} is not a valid URI" + end end # Warnings ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25677&group_id=126 From noreply at rubyforge.org Fri May 1 20:04:24 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 1 May 2009 20:04:24 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25748 ] Use of --source option seems to break default --include-dependencies option Message-ID: <20090502000424.19A04197858C@rubyforge.org> Bugs item #25748, was opened at 2009-05-01 09:00 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25748&group_id=126 Category: `gem install` command Group: v1.3.x Status: Closed Resolution: Rejected Priority: 3 Submitted By: S?bastien Luquet (sebastienluquet) Assigned to: Eric Hodel (drbrain) Summary: Use of --source option seems to break default --include-dependencies option Initial Comment: RubyGems Environment: - RUBYGEMS VERSION: 1.3.2 - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [i386-mswin32] - INSTALLATION DIRECTORY: H:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: H:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: H:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - H:/ruby/lib/ruby/gems/1.8 - H:/Documents and Settings/seb/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://gems.rubyforge.org", "http://gems.rubyonrails.org", "http://gems.github.com"] - "gem" => "--no-rdoc --no-ri" - REMOTE SOURCES: - http://gems.rubyforge.org - http://gems.rubyonrails.org - http://gems.github.com rcov should not be installed (dependency of jscruggs-metric_fu) gem install jscruggs-metric_fu --source http://gems.github.com --debug Exception `NameError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygem /command_manager.rb:161 - uninitialized constant Gem::Commands::InstallCommand Exception `Gem::LoadError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:805 - Could not find RubyGem test-unit (>= 0) Exception `Errno::EEXIST' at H:/ruby/lib/ruby/1.8/fileutils.rb:243 - File exists - H:\Documents and Settings\seb/.gem/specs/gems.github.com%80 Exception `IOError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygems/format.rb:50 - closed stream Exception `Errno::EEXIST' at H:/ruby/lib/ruby/1.8/fileutils.rb:243 - File exists - H:/ruby/lib/ruby/gems/1.8 Exception `Gem::InstallError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygem /installer.rb:255 - jscruggs-metric_fu requires rcov (> 0.8.1, runtime) ERROR: Error installing jscruggs-metric_fu: jscruggs-metric_fu requires rcov (> 0.8.1, runtime) gem install jscruggs-metric_fu works ---------------------------------------------------------------------- >Comment By: Chad Woolley (thewoolleyman) Date: 2009-05-01 17:04 Message: Here is a discussion Eric and I had (based on Josh Susser's idea) to make this less confusing. I don't think there's a specific feature in the tracker, if someone wants to create it... me: also having the --source option override any default or definition in .gemrc is annoying. Was talking with Josh Susser about it. eric.hodel: that's what it's for "no, I really want this" 6:30 PM if I change my mind on it, then people will complain for the opposite reason :/ me: but that is not intuitive. I was thiniking to have have --[no-]use-configured-sources, with --use-configured-sources being the default. eric.hodel: that could work me: so --source option would be additive by default ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-05-01 16:40 Message: There's no rcov gem on the github source, so I don't know why you expect this to work. The documentation states: --source URL Use URL as the remote source for gems Which may not be clear, but implies that the flag overrides the default sources rather than appends to them. If you can think of better wording, I will be glad to change it. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25748&group_id=126 From drbrain at segment7.net Fri May 1 20:32:32 2009 From: drbrain at segment7.net (Eric Hodel) Date: Fri, 1 May 2009 17:32:32 -0700 Subject: [Rubygems-developers] RubyGems 1.3.3? Message-ID: I've cleaned out most of the easy stuff in the bug and patch queue again, should we release a 1.3.3? The changes are small: * lib/rubygems.rb * Gem.bin_path now escapes paths with spaces. * lib/rubygems/commands/cleanup_command.rb * Clean up --user-install gems. Bug #25516 by Brett Eisenberg. * lib/rubygems/commands/install_command.rb * Replaced deprecated Gem::SourceIndex method 'search' with 'find_name' when using the -t option. Fixes bug # 25632 by Daniel Berger. * lib/rubygems/commands/specification_command.rb * Added requesting single fields from a spec. * lib/rubygems/ext/configure_builder.rb * Support Gem::Command.build_args. * lib/rubygems/ext/rake_builder.rb * Use explicit ruby command loading rubygems to invoke rake. * lib/rubygems/specification.rb * Check bindir for executables, not root. Bug reported by David Chelimsky. Remove Time.today, no way to override it before RubyGems loads. Raise Gem::Exception for #installation_path when not installed. Bug #25741 by Daniel Berger. Don't error in #validate when homepage is nil. Bug #25677 by Mike Burrows. * lib/rubygems/uninstaller.rb * Uninstall executables from the correct directory. Bug #25555 by Brett Eisenberg. From thewoolleyman at gmail.com Fri May 1 20:40:45 2009 From: thewoolleyman at gmail.com (Chad Woolley) Date: Fri, 1 May 2009 17:40:45 -0700 Subject: [Rubygems-developers] RubyGems 1.3.3? In-Reply-To: References: Message-ID: On Fri, May 1, 2009 at 5:32 PM, Eric Hodel wrote: > I've cleaned out most of the easy stuff in the bug and patch queue again, > should we release a 1.3.3? http://www.extremeprogramming.org/rules/releaseoften.html From hgs at dmu.ac.uk Fri May 1 21:08:00 2009 From: hgs at dmu.ac.uk (Hugh Sasse) Date: Sat, 2 May 2009 02:08:00 +0100 (BST) Subject: [Rubygems-developers] RubyGems 1.3.3? In-Reply-To: References: Message-ID: On Fri, 1 May 2009, Chad Woolley wrote: > On Fri, May 1, 2009 at 5:32 PM, Eric Hodel wrote: > > I've cleaned out most of the easy stuff in the bug and patch queue again, > > should we release a 1.3.3? > > http://www.extremeprogramming.org/rules/releaseoften.html :-) Pretty sure what that's about, but I have only one caution: How do we check for version numbers? If we assume /\d\.\d\.\d/ as Ruby has in the past we will run out. If we assume /\d+\.\d+\.\d+/ then roll on Rubygems 12.230.965 and so on. :-) Redcloth just ran into this I think. Hugh From djberg96 at gmail.com Fri May 1 23:00:28 2009 From: djberg96 at gmail.com (Daniel Berger) Date: Fri, 1 May 2009 21:00:28 -0600 Subject: [Rubygems-developers] RubyGems 1.3.3? In-Reply-To: References: Message-ID: <6037b70c0905012000t7a31bbbuae6738b43cfc9140@mail.gmail.com> On Fri, May 1, 2009 at 6:32 PM, Eric Hodel wrote: > I've cleaned out most of the easy stuff in the bug and patch queue again, > should we release a 1.3.3? I say yes. Regards, Dan From noreply at rubyforge.org Sat May 2 03:47:44 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 2 May 2009 03:47:44 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25748 ] Use of --source option seems to break default --include-dependencies option Message-ID: <20090502074745.11E6C1598075@rubyforge.org> Bugs item #25748, was opened at 01/05/2009 18:00 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25748&group_id=126 Category: `gem install` command Group: v1.3.x Status: Closed Resolution: Rejected Priority: 3 Submitted By: S?bastien Luquet (sebastienluquet) Assigned to: Eric Hodel (drbrain) Summary: Use of --source option seems to break default --include-dependencies option Initial Comment: RubyGems Environment: - RUBYGEMS VERSION: 1.3.2 - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [i386-mswin32] - INSTALLATION DIRECTORY: H:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: H:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: H:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - H:/ruby/lib/ruby/gems/1.8 - H:/Documents and Settings/seb/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://gems.rubyforge.org", "http://gems.rubyonrails.org", "http://gems.github.com"] - "gem" => "--no-rdoc --no-ri" - REMOTE SOURCES: - http://gems.rubyforge.org - http://gems.rubyonrails.org - http://gems.github.com rcov should not be installed (dependency of jscruggs-metric_fu) gem install jscruggs-metric_fu --source http://gems.github.com --debug Exception `NameError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygem /command_manager.rb:161 - uninitialized constant Gem::Commands::InstallCommand Exception `Gem::LoadError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygems.rb:805 - Could not find RubyGem test-unit (>= 0) Exception `Errno::EEXIST' at H:/ruby/lib/ruby/1.8/fileutils.rb:243 - File exists - H:\Documents and Settings\seb/.gem/specs/gems.github.com%80 Exception `IOError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygems/format.rb:50 - closed stream Exception `Errno::EEXIST' at H:/ruby/lib/ruby/1.8/fileutils.rb:243 - File exists - H:/ruby/lib/ruby/gems/1.8 Exception `Gem::InstallError' at H:/ruby/lib/ruby/site_ruby/1.8/rubygem /installer.rb:255 - jscruggs-metric_fu requires rcov (> 0.8.1, runtime) ERROR: Error installing jscruggs-metric_fu: jscruggs-metric_fu requires rcov (> 0.8.1, runtime) gem install jscruggs-metric_fu works ---------------------------------------------------------------------- >Comment By: S?bastien Luquet (sebastienluquet) Date: 02/05/2009 09:47 Message: > There's no rcov gem on the github source, so I don't know why you expect this to work. I didn't want to install rcov but jscruggs-metric_fu which is on the github source. rcov is just a dependency. > Which may not be clear, but implies that the flag overrides the default sources rather than appends to them. If you can think of better wording, I will be glad to change it. Sorry, I didn't read the documentation... Should it be : --source URL Use URL as the remote source for gems (and theirs dependencies) > me: so --source option would be additive by default It would be great ! ---------------------------------------------------------------------- Comment By: Chad Woolley (thewoolleyman) Date: 02/05/2009 02:04 Message: Here is a discussion Eric and I had (based on Josh Susser's idea) to make this less confusing. I don't think there's a specific feature in the tracker, if someone wants to create it... me: also having the --source option override any default or definition in .gemrc is annoying. Was talking with Josh Susser about it. eric.hodel: that's what it's for "no, I really want this" 6:30 PM if I change my mind on it, then people will complain for the opposite reason :/ me: but that is not intuitive. I was thiniking to have have --[no-]use-configured-sources, with --use-configured-sources being the default. eric.hodel: that could work me: so --source option would be additive by default ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 02/05/2009 01:40 Message: There's no rcov gem on the github source, so I don't know why you expect this to work. The documentation states: --source URL Use URL as the remote source for gems Which may not be clear, but implies that the flag overrides the default sources rather than appends to them. If you can think of better wording, I will be glad to change it. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25748&group_id=126 From noreply at rubyforge.org Sat May 2 12:57:16 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 2 May 2009 12:57:16 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25759 ] Prelease versions don't satisfy ~> with the intended release number Message-ID: <20090502165716.A72CE1D7841E@rubyforge.org> Bugs item #25759, was opened at 2009-05-02 11:57 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25759&group_id=126 Category: #gem and #require methods Group: None Status: Open Resolution: None Priority: 3 Submitted By: Yossef Mendelssohn (ymendel) Assigned to: Nobody (None) Summary: Prelease versions don't satisfy ~> with the intended release number Initial Comment: Right now, 2.0.pre is ~> 1.0 instead of ~> 2.0. No good. It seems the correct way to check a prerelease version against ~> is to use the intended release number (i.e. 2.0 for 2.0.pre). Patch (output from git show) available at http://gist.github.com/105621 ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25759&group_id=126 From luislavena at gmail.com Sat May 2 13:36:14 2009 From: luislavena at gmail.com (Luis Lavena) Date: Sat, 2 May 2009 14:36:14 -0300 Subject: [Rubygems-developers] RubyGems 1.3.3? In-Reply-To: References: Message-ID: <71166b3b0905021036v4ab5cb98ocad96092c2cd33e@mail.gmail.com> On Fri, May 1, 2009 at 10:08 PM, Hugh Sasse wrote: > > > On Fri, 1 May 2009, Chad Woolley wrote: > >> On Fri, May 1, 2009 at 5:32 PM, Eric Hodel wrote: >> > I've cleaned out most of the easy stuff in the bug and patch queue again, >> > should we release a 1.3.3? >> >> http://www.extremeprogramming.org/rules/releaseoften.html > > :-) Pretty sure what that's about, but I have only one caution: > > How do we check for version numbers? ?If we assume /\d\.\d\.\d/ as > Ruby has in the past we will run out. ?If we assume /\d+\.\d+\.\d+/ then > roll on Rubygems 12.230.965 and so on. :-) ?Redcloth just ran into this > I think. > irb(main):004:0> v1 = Gem::Version.new('12.230.965') => # irb(main):005:0> v2 = Gem::Version.new('12.230.875') => # irb(main):006:0> v1 > v2 => true irb(main):007:0> v1 < v2 => false -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry From luislavena at gmail.com Sat May 2 13:45:14 2009 From: luislavena at gmail.com (Luis Lavena) Date: Sat, 2 May 2009 14:45:14 -0300 Subject: [Rubygems-developers] RubyGems 1.3.3? In-Reply-To: References: Message-ID: <71166b3b0905021045o1b62f4eaqb65d1357e98f185f@mail.gmail.com> On Fri, May 1, 2009 at 9:32 PM, Eric Hodel wrote: > I've cleaned out most of the easy stuff in the bug and patch queue again, > should we release a 1.3.3? > About to run the test on Windows, will send reports after. Thinking: would you guys spin up an amazon image with windows and ruby pre-installed to test versions prior releases? Just a thought. -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry From drbrain at segment7.net Sat May 2 18:16:24 2009 From: drbrain at segment7.net (Eric Hodel) Date: Sat, 2 May 2009 15:16:24 -0700 Subject: [Rubygems-developers] RubyGems 1.3.3? In-Reply-To: References: <71166b3b0905021036v4ab5cb98ocad96092c2cd33e@mail.gmail.com> Message-ID: On May 2, 2009, at 13:25, Hugh Sasse wrote: > On Sat, 2 May 2009, Luis Lavena wrote: >> On Fri, May 1, 2009 at 10:08 PM, Hugh Sasse wrote: >>> On Fri, 1 May 2009, Chad Woolley wrote: >>> How do we check for version numbers? If we assume /\d\.\d\.\d/ as >>> Ruby has in the past we will run out. If we assume /\d+\.\d+\.\d >>> +/ then >> irb(main):004:0> v1 = Gem::Version.new('12.230.965') >> => # >> irb(main):005:0> v2 = Gem::Version.new('12.230.875') >> => # >> irb(main):006:0> v1 > v2 >> => true >> irb(main):007:0> v1 < v2 >> => false > > Then my remarks above can be compressed to one bit: YES. Thank you > for taking > the time to dig out that info. Not had chance to explore the source > lately. Don't forget RubyGems 0.8.11 (and .10) From noreply at rubyforge.org Sat May 2 18:52:49 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 2 May 2009 18:52:49 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25541 ] Ruby sqlite/gem error: Could not load sqlite adapter Message-ID: <20090502225249.C49FB1598078@rubyforge.org> Bugs item #25541, was opened at 2009-04-19 14:29 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25541&group_id=126 Category: None >Group: v1.3.x >Status: Closed Resolution: Rejected Priority: 3 Submitted By: John Spanton (jhs408) >Assigned to: Eric Hodel (drbrain) Summary: Ruby sqlite/gem error: Could not load sqlite adapter Initial Comment: Executing sample program on windows xp syste,. The sample "c:\tmp'Test_sequel.rb" generates the error: Could not load sqlite adapter. Yet, when the example is executed in the sequel directory, no error occur, sample gives the proper results. The sqlite3.dll is located in the PATH. It appears that rubygems is not able to locate sqlite.rb in the directory:C:\Ruby\lib\ruby\gems\1.8\gems\sequel-2.12.0\lib\sequel \adapters when the sample program is executed from c:\tmp Which leads me to suspect that rubygem is having a problem or the is a coding problem in sequel or rubygems. Any suggestion or changes to the sample to resolve the error. Thanks for the help, John email: jhs408 at gmail.com ------------------------------------ Windows XP SP3 Using ruby 1.8.7, gem 1.3.2, sqlite3-ruby 1.2.4, sequel 2.12.0 product Environment set: RUBYOPT=rubygems PATH=c:\tools\sqlite3 ... -----running sample----> c:\tmp\test_sqlite.rb -------------- require 'sequel' DB = Sequel.sqlite("test-sequel.db") # create an items table DB.create_table :items do primary_key :id column :name, :text column :price, :float end # create a dataset from the items table items = DB[:items] # populate the table items << {:name => 'abc', :price => rand * 100} items << {:name => 'def', :price => rand * 100} items << {:name => 'ghi', :price => rand * 100} # print out the number of records puts "Item count: #{ items.count }" # print out the records in descending order by price items.reverse_order(:price).print # print out the average price puts "The average price is: #{ items.avg :price }" ------Error Msg---- C:\tmp>test_sequel.rb C:/ruby/lib/ruby/gems/1.8/gems/sequel-2.11.0/lib/sequel_core/ database.rb:105:in `adapter_class': Could not load sqlite a dapter: (Sequel::Error::AdapterNotFound) no such file to load -- sqlite3 from C:/ruby/lib/ruby/gems/1.8/gems/sequel-2.11.0/lib/ sequel_core/database.rb:141:in `connect' from C:/ruby/lib/ruby/gems/1.8/gems/sequel-2.11.0/lib/ sequel_core.rb:68:in `connect' from C:/ruby/lib/ruby/gems/1.8/gems/sequel-2.11.0/lib/ sequel_core.rb:157:in `adapter_method' from (eval):1:in `sqlite' from C:/tmp/test_sequel.rb:7 ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2009-05-02 15:52 Message: Closing, since this works for us and doesn't seem to be a rubygems bug. ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-04-19 14:41 Message: First, this should have been reported to Sequel and Sqlite3 project, not rubygems. I'll check if sqlite3-ruby gem was compiled properly for your platform, since looks like you're using windows and there is no binary for sqlite3-ruby out there yet. I just did the exact same test: Luis at KEORE (D:\Users\Luis\Desktop) $ ruby test.rb Item count: 3 Sequel::Dataset#print is deprecated and will be removed in Sequel 3.0. require "sequel/extensions/pretty_table" first. D:/Users/Luis/.gem/ruby/1.8/gems/sequel-2.12.0/lib/sequel/deprecated.rb:245:in `print' test.rb:20 Sequel::PrettyTable#print is deprecated and will be removed in Sequel 3.0. require "sequel/extensions/pretty_table" first. D:/Users/Luis/.gem/ruby/1.8/gems/sequel-2.12.0/lib/sequel/deprecated.rb:304:in `print' D:/Users/Luis/.gem/ruby/1.8/gems/sequel-2.12.0/lib/sequel/deprecated.rb:246:in `print' test.rb:20 +--+----+----------------+ |id|name|price | +--+----+----------------+ | 3|ghi | 76.3733| | 2|def | 60.0457| | 1|abc | 26.7445| +--+----+----------------+ The average price is: 54.3878553800661 Luis at KEORE (D:\Users\Luis\Desktop) $ gem --version 1.3.2 Luis at KEORE (D:\Users\Luis\Desktop) $ ruby -v ruby 1.8.6 (2009-03-31 patchlevel 368) [i386-mingw32] sqlite3-ruby (1.2.4) sequel (2.12.0) ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25541&group_id=126 From noreply at rubyforge.org Sat May 2 18:53:18 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 2 May 2009 18:53:18 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-23429 ] gem cache goes to wrong drive in windows if ruby is run from a non C drive Message-ID: <20090502225318.52ED1159802C@rubyforge.org> Bugs item #23429, was opened at 2009-01-03 20:41 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=23429&group_id=126 Category: other >Group: v1.3.x >Status: Closed Resolution: None Priority: 3 Submitted By: Roger Pack (rogerdpack) Assigned to: Luis Lavena (luislavena) Summary: gem cache goes to wrong drive in windows if ruby is run from a non C drive Initial Comment: After running a rails project from g:\something I got this directory tree: G:\Documents and Settings\Melissa.BLACKY\.gem\ruby\1.8\specifications where C:\Documents and Settings\Melissa.BLACKY\.gem\ruby\1.8\specifications is I think where it actually wanted to save it. thoughts? -=r ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2009-05-02 15:53 Message: Closing since this works for us. ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-03-14 09:35 Message: Yes, my user profile and home is located there. This is my gem env information, after unsetting HOME, HOMEDRIVE and HOMEPATH: Luis at KEORE (D:\Users\Luis) $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.1 - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [i386-mingw32] - INSTALLATION DIRECTORY: C:/Ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/Ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/Ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mingw32 - GEM PATHS: - C:/Ruby/lib/ruby/gems/1.8 - C:/Documents and Settings/Luis/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://gems.rubyforge.org/ Installed progressbar gem in that drive: Luis at KEORE (D:\Users\Luis) $ gem install progressbar Successfully installed progressbar-0.0.3 1 gem installed Updating ri class cache with 153 classes... And took a look into the root of D:\ to see if a new folder was created: Luis at KEORE (D:\Users\Luis) $ dir d:\ Volume in drive D is Data Volume Serial Number is 54C3-9D4F Directory of d:\ [Downloads] [Temp] [Users] 0 File(s) 0 bytes 3 Dir(s) 98,614,943,744 bytes free So, if you provide the "gem env" output will be easier for me replicate your setup. ---------------------------------------------------------------------- Comment By: Roger Pack (rogerdpack) Date: 2009-03-14 09:24 Message: did you try installing a new gem within D: maybe? ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-03-14 09:22 Message: Can you provide the output of gem env here? I've put Ruby in C: and put a Rails application in D and couldn't replicate this. Thank you. ---------------------------------------------------------------------- Comment By: Roger Pack (rogerdpack) Date: 2009-01-05 07:39 Message: just copied a rails app from c:\something to g:\something, ran it from there [i.e. ruby script\server] and that directory popped up :) ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-01-04 05:52 Message: What do you mean by "running a rails project"? You mean you did a 'gem install rails' from the G:\ drive? Or simply running 'ruby script/server' within a Rails project caused that directory to be created? Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=23429&group_id=126 From noreply at rubyforge.org Sat May 2 18:53:59 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 2 May 2009 18:53:59 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-21325 ] Print message when no gems matching your platform are found Message-ID: <20090502225359.390601858257@rubyforge.org> Bugs item #21325, was opened at 2008-07-24 12:40 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=21325&group_id=126 Category: `gem install` command Group: v1.2.x Status: Open Resolution: None Priority: 3 Submitted By: Eric Hodel (drbrain) Assigned to: Wilson Bilkovich (wilson) Summary: Print message when no gems matching your platform are found Initial Comment: Instead of 'no gem to install' ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-03-13 16:11 Message: Added platforms to gem list -d ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=21325&group_id=126 From noreply at rubyforge.org Sat May 2 18:54:07 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 2 May 2009 18:54:07 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-21325 ] Print message when no gems matching your platform are found Message-ID: <20090502225407.C08141858253@rubyforge.org> Bugs item #21325, was opened at 2008-07-24 12:40 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=21325&group_id=126 Category: `gem install` command Group: v1.2.x Status: Open Resolution: None Priority: 3 Submitted By: Eric Hodel (drbrain) Assigned to: Wilson Bilkovich (wilson) Summary: Print message when no gems matching your platform are found Initial Comment: Instead of 'no gem to install' ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-03-13 16:11 Message: Added platforms to gem list -d ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=21325&group_id=126 From noreply at rubyforge.org Sat May 2 18:54:28 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 2 May 2009 18:54:28 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-21325 ] Print message when no gems matching your platform are found Message-ID: <20090502225429.0279A185825B@rubyforge.org> Bugs item #21325, was opened at 2008-07-24 12:40 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=21325&group_id=126 Category: `gem install` command Group: v1.2.x Status: Open >Resolution: Accepted Priority: 3 Submitted By: Eric Hodel (drbrain) Assigned to: Wilson Bilkovich (wilson) Summary: Print message when no gems matching your platform are found Initial Comment: Instead of 'no gem to install' ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-03-13 16:11 Message: Added platforms to gem list -d ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=21325&group_id=126 From luislavena at gmail.com Sun May 3 13:46:44 2009 From: luislavena at gmail.com (Luis Lavena) Date: Sun, 3 May 2009 14:46:44 -0300 Subject: [Rubygems-developers] Revision 2193, Windows Results Message-ID: <71166b3b0905031046s31afeb3dsb5333fb8ae0adb92@mail.gmail.com> Hey guys, The following are the results of RubyGems revision 2193 running against MinGW and VC6 versions of Ruby. http://pastie.org/466833 Just in case, if someone want to test the binary builds of new One-Click Installer, you can try downloading those form there: http://rubyinstaller.org/downloads/ Those are direct builds from rubyinstaller repository and includes a fresh sandbox with MinGW+MSYS to help you 'fake' a complete *nix environment. If you have a Windows VM (or real PC) please try those out, since new One-Click Installer will be built on top of that. Regards, -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry From hgs at dmu.ac.uk Sun May 3 14:12:31 2009 From: hgs at dmu.ac.uk (Hugh Sasse) Date: Sun, 3 May 2009 19:12:31 +0100 (BST) Subject: [Rubygems-developers] RubyGems 1.3.3? In-Reply-To: References: <71166b3b0905021036v4ab5cb98ocad96092c2cd33e@mail.gmail.com> Message-ID: On Sat, 2 May 2009, Eric Hodel wrote: > > Don't forget RubyGems 0.8.11 (and .10) I did exactly that. Forgot. Sorry for the noise. Hugh From djberg96 at gmail.com Mon May 4 09:39:10 2009 From: djberg96 at gmail.com (Daniel Berger) Date: Mon, 04 May 2009 07:39:10 -0600 Subject: [Rubygems-developers] Revision 2193, Windows Results In-Reply-To: <71166b3b0905031046s31afeb3dsb5333fb8ae0adb92@mail.gmail.com> References: <71166b3b0905031046s31afeb3dsb5333fb8ae0adb92@mail.gmail.com> Message-ID: <49FEEFFE.3030301@gmail.com> Luis Lavena wrote: > Hey guys, > > The following are the results of RubyGems revision 2193 running > against MinGW and VC6 versions of Ruby. > > http://pastie.org/466833 Looks like the one failure either needs to be skipped or the test itself needs to be adjusted. Regards, Dan From luislavena at gmail.com Mon May 4 10:11:59 2009 From: luislavena at gmail.com (Luis Lavena) Date: Mon, 4 May 2009 11:11:59 -0300 Subject: [Rubygems-developers] Revision 2193, Windows Results In-Reply-To: <49FEEFFE.3030301@gmail.com> References: <71166b3b0905031046s31afeb3dsb5333fb8ae0adb92@mail.gmail.com> <49FEEFFE.3030301@gmail.com> Message-ID: <71166b3b0905040711w4cb07612lb0f40ce0fc74c08e@mail.gmail.com> On Mon, May 4, 2009 at 10:39 AM, Daniel Berger wrote: > Luis Lavena wrote: >> >> Hey guys, >> >> The following are the results of RubyGems revision 2193 running >> against MinGW and VC6 versions of Ruby. >> >> http://pastie.org/466833 > > Looks like the one failure either needs to be skipped or the test itself > needs to be adjusted. > I see VC6 skips 6 tests while MinGW only 4, maybe there is a problem with the platform evaluation? -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry From djberg96 at gmail.com Mon May 4 12:35:52 2009 From: djberg96 at gmail.com (Daniel Berger) Date: Mon, 04 May 2009 10:35:52 -0600 Subject: [Rubygems-developers] Revision 2193, Windows Results In-Reply-To: <71166b3b0905040711w4cb07612lb0f40ce0fc74c08e@mail.gmail.com> References: <71166b3b0905031046s31afeb3dsb5333fb8ae0adb92@mail.gmail.com> <49FEEFFE.3030301@gmail.com> <71166b3b0905040711w4cb07612lb0f40ce0fc74c08e@mail.gmail.com> Message-ID: <49FF1968.2020109@gmail.com> Luis Lavena wrote: > On Mon, May 4, 2009 at 10:39 AM, Daniel Berger wrote: >> Luis Lavena wrote: >>> Hey guys, >>> >>> The following are the results of RubyGems revision 2193 running >>> against MinGW and VC6 versions of Ruby. >>> >>> http://pastie.org/466833 >> Looks like the one failure either needs to be skipped or the test itself >> needs to be adjusted. >> > > I see VC6 skips 6 tests while MinGW only 4, maybe there is a problem > with the platform evaluation? > Not entirely. The skipped messages that include "VC++" are only skipped for versions of Ruby built with Visual Studio, not the cygwin/mingw builds. Or rather, it looks for a platform match of "mswin". I thought that excluded cygwin and mingw. Is that not the case? I thought cygwin supported symlinks. Is that not true? Perhaps a better approach would be to inspect CONFIG['CC'], or one of the other attributes. Regards, Dan From drbrain at segment7.net Mon May 4 17:04:23 2009 From: drbrain at segment7.net (Eric Hodel) Date: Mon, 4 May 2009 14:04:23 -0700 Subject: [Rubygems-developers] Revision 2193, Windows Results In-Reply-To: <49FF1968.2020109@gmail.com> References: <71166b3b0905031046s31afeb3dsb5333fb8ae0adb92@mail.gmail.com> <49FEEFFE.3030301@gmail.com> <71166b3b0905040711w4cb07612lb0f40ce0fc74c08e@mail.gmail.com> <49FF1968.2020109@gmail.com> Message-ID: <058884BA-711C-42D7-BC1A-FB4A6FC61A11@segment7.net> On May 4, 2009, at 09:35, Daniel Berger wrote: > Luis Lavena wrote: >> On Mon, May 4, 2009 at 10:39 AM, Daniel Berger >> wrote: >>> Luis Lavena wrote: >>>> Hey guys, >>>> >>>> The following are the results of RubyGems revision 2193 running >>>> against MinGW and VC6 versions of Ruby. >>>> >>>> http://pastie.org/466833 >>> Looks like the one failure either needs to be skipped or the test >>> itself >>> needs to be adjusted. >>> >> I see VC6 skips 6 tests while MinGW only 4, maybe there is a problem >> with the platform evaluation? > > Not entirely. The skipped messages that include "VC++" are only > skipped for versions of Ruby built with Visual Studio, not the > cygwin/mingw builds. > > Or rather, it looks for a platform match of "mswin". I thought that > excluded cygwin and mingw. Is that not the case? > > I thought cygwin supported symlinks. Is that not true? > > Perhaps a better approach would be to inspect CONFIG['CC'], or one > of the other attributes. For now, I added a skip for the failing test with a reason. We can come back and evaluate it later. From drbrain at segment7.net Mon May 4 19:14:05 2009 From: drbrain at segment7.net (Eric Hodel) Date: Mon, 4 May 2009 16:14:05 -0700 Subject: [Rubygems-developers] [ANN] RubyGems 1.3.3 Message-ID: <73BD7228-6405-44EC-BDBF-582EFEC2F811@segment7.net> = Announce: RubyGems Release 1.3.3 NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no rubygems-update installed. You will need to follow the second set of update instructions if you see "Nothing to update". Release 1.3.3 fixes some bugs and adds some features. New Features: * `gem server` allows port names (from /etc/services) with --port. * `gem server` now has search that jumps to RDoc. Patch #22959 by Vladimir Dobriakov. * `gem spec` can retrieve single fields from a spec (like `gem spec rake authors`). * Gem::Specification#has_rdoc= is deprecated and ignored (defaults to true) * RDoc is now generated regardless of Gem::Specification#has_rdoc? Bug Fixes: * `gem clean` now cleans up --user-install gems. Bug #25516 by Brett Eisenberg. * Gem.bin_path now escapes paths with spaces. * Rake extension builder uses explicit correctly loads rubygems when invoking rake. * Prerelease versions now match "~>" correctly. Patch #25759 by Yossef Mendelssohn. * Check bindir for executables, not root when validating. Bug reported by David Chelimsky. * Remove Time.today, no way to override it before RubyGems loads. Bug #25564 by Emanuele Vicentini * Raise Gem::Exception for #installation_path when not installed. Bug #25741 by Daniel Berger. * Don't raise in Gem::Specification#validate when homepage is nil. Bug #25677 by Mike Burrows. * Uninstall executables from the correct directory. Bug #25555 by Brett Eisenberg. * Raise Gem::LoadError if Kernel#gem fails due to previously-loaded gem. Bug reported by Alf Mikula. Deprecation Notices: * Gem::manage_gems has been removed. * Time::today has been removed early. There was no way to make it warn and be easy to override with user code. For a full list of changes to RubyGems and the contributor for each change, see the ChangeLog file. == How can I get RubyGems? NOTE: If you have installed RubyGems using a package system you may want to install a new RubyGems through the same packaging system. If you have a recent version of RubyGems (0.8.5 or later), then all you need to do is: $ gem update --system (you might need to be admin/root) NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no rubygems-update installed. You will need to follow the second set of update instructions if you see "Nothing to update". NOTE: You may have to run the command twice if you have any previosly installed rubygems-update gems. If you have an older version of RubyGems installed, then you can still do it in two steps: $ gem install rubygems-update (again, might need to be admin/root) $ update_rubygems (... here too) If you don't have any gems install, there is still the pre-gem approach to getting software ... doing it manually: 1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126 2. UNPACK INTO A DIRECTORY AND CD THERE 3. INSTALL WITH: ruby setup.rb (you may need admin/root privilege) == To File Bugs The RubyGems bug tracker can be found on RubyForge at: http://rubyforge.org/tracker/?func=add&group_id=126&atid=575 When filing a bug, `gem env` output will be helpful in diagnosing the issue. If you find a bug where RubyGems crashes, please provide debug output. You can do that with `gem --debug the_command`. == Thanks Keep those gems coming! -- The RubyGems team From noreply at rubyforge.org Mon May 4 20:11:16 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 4 May 2009 20:11:16 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25777 ] RDoc & Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Message-ID: <20090505001116.400A11858201@rubyforge.org> Bugs item #25777, was opened at 2009-05-04 17:11 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 Category: RubyGems installer (setup.rb) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Bryan Soto (bsoto) Assigned to: Nobody (None) Summary: RDoc & Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Initial Comment: Microsoft Windows [Version 6.0.6001] Copyright (c) 2006 Microsoft Corporation. All rights reserved. ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem --version 1.3.2 ----- C:\Users\bryan>gem update --system Updating RubyGems Updating rubygems-update Successfully installed rubygems-update-1.3.3 C:/ruby/lib/ruby/site_ruby/1.8/rubygems/commands/update_command.rb:103:Warning: Gem::SourceIndex#search support for String patterns is deprecated Updating RubyGems to 1.3.3 Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/Commands/cdesc-Commands.yaml ----- C:\Users\bryan>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby setup.rb Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/cdesc-Gem.yaml ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem list --local rdoc *** LOCAL GEMS *** rdoc (2.4.3) rdoc_html_templates (2.3.0) C:\Users\bryan\Desktop\rubygems-1.3.3>gem uninstall rdoc rdoc_html_templates Remove executables: rdoc, ri in addition to the gem? [Yn] y Removing rdoc Removing ri You have requested to uninstall the gem: rdoc-2.4.3 rdoc_html_templates-2.3.0 depends on [rdoc (~> 2.3)] If you remove this gems, one or more dependencies will not be met. Continue with Uninstall? [Yn] y Successfully uninstalled rdoc-2.4.3 Successfully uninstalled rdoc_html_templates-2.3.0 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>update_rubygems Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri Installing rubygems-1.3.3 rdoc into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/rdoc ------------------------------------------------------------------------------ = Announce: RubyGems Release 1.3.3 ... snipped ... RubyGems installed the following executables: C:/ruby/bin/gem ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] - INSTALLATION DIRECTORY: C:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/ruby/lib/ruby/gems/1.8 - C:/Users/bryan/.gem/ruby/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", "http://gems.github.com"] - REMOTE SOURCES: - http://gems.rubyforge.org/ - http://gems.github.com - http://gems.github.com ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 From noreply at rubyforge.org Mon May 4 20:19:42 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 4 May 2009 20:19:42 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25777 ] RDoc & Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Message-ID: <20090505001942.8B0A418581FF@rubyforge.org> Bugs item #25777, was opened at 2009-05-04 17:11 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 Category: RubyGems installer (setup.rb) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Bryan Soto (bsoto) Assigned to: Nobody (None) Summary: RDoc & Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Initial Comment: Microsoft Windows [Version 6.0.6001] Copyright (c) 2006 Microsoft Corporation. All rights reserved. ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem --version 1.3.2 ----- C:\Users\bryan>gem update --system Updating RubyGems Updating rubygems-update Successfully installed rubygems-update-1.3.3 C:/ruby/lib/ruby/site_ruby/1.8/rubygems/commands/update_command.rb:103:Warning: Gem::SourceIndex#search support for String patterns is deprecated Updating RubyGems to 1.3.3 Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/Commands/cdesc-Commands.yaml ----- C:\Users\bryan>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby setup.rb Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/cdesc-Gem.yaml ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem list --local rdoc *** LOCAL GEMS *** rdoc (2.4.3) rdoc_html_templates (2.3.0) C:\Users\bryan\Desktop\rubygems-1.3.3>gem uninstall rdoc rdoc_html_templates Remove executables: rdoc, ri in addition to the gem? [Yn] y Removing rdoc Removing ri You have requested to uninstall the gem: rdoc-2.4.3 rdoc_html_templates-2.3.0 depends on [rdoc (~> 2.3)] If you remove this gems, one or more dependencies will not be met. Continue with Uninstall? [Yn] y Successfully uninstalled rdoc-2.4.3 Successfully uninstalled rdoc_html_templates-2.3.0 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>update_rubygems Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri Installing rubygems-1.3.3 rdoc into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/rdoc ------------------------------------------------------------------------------ = Announce: RubyGems Release 1.3.3 ... snipped ... RubyGems installed the following executables: C:/ruby/bin/gem ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] - INSTALLATION DIRECTORY: C:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/ruby/lib/ruby/gems/1.8 - C:/Users/bryan/.gem/ruby/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", "http://gems.github.com"] - REMOTE SOURCES: - http://gems.rubyforge.org/ - http://gems.github.com - http://gems.github.com ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2009-05-04 17:19 Message: Odd. I was able to update on my Windows Vista box with no issues. RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] - INSTALLATION DIRECTORY: C:/Ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/Ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/Ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/Ruby/lib/ruby/gems/1.8 - C:/Users/djberge/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 From noreply at rubyforge.org Mon May 4 20:20:07 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 4 May 2009 20:20:07 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25777 ] RDoc & Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Message-ID: <20090505002007.C390F1678111@rubyforge.org> Bugs item #25777, was opened at 2009-05-04 17:11 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 Category: RubyGems installer (setup.rb) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Bryan Soto (bsoto) Assigned to: Nobody (None) Summary: RDoc & Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Initial Comment: Microsoft Windows [Version 6.0.6001] Copyright (c) 2006 Microsoft Corporation. All rights reserved. ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem --version 1.3.2 ----- C:\Users\bryan>gem update --system Updating RubyGems Updating rubygems-update Successfully installed rubygems-update-1.3.3 C:/ruby/lib/ruby/site_ruby/1.8/rubygems/commands/update_command.rb:103:Warning: Gem::SourceIndex#search support for String patterns is deprecated Updating RubyGems to 1.3.3 Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/Commands/cdesc-Commands.yaml ----- C:\Users\bryan>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby setup.rb Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/cdesc-Gem.yaml ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem list --local rdoc *** LOCAL GEMS *** rdoc (2.4.3) rdoc_html_templates (2.3.0) C:\Users\bryan\Desktop\rubygems-1.3.3>gem uninstall rdoc rdoc_html_templates Remove executables: rdoc, ri in addition to the gem? [Yn] y Removing rdoc Removing ri You have requested to uninstall the gem: rdoc-2.4.3 rdoc_html_templates-2.3.0 depends on [rdoc (~> 2.3)] If you remove this gems, one or more dependencies will not be met. Continue with Uninstall? [Yn] y Successfully uninstalled rdoc-2.4.3 Successfully uninstalled rdoc_html_templates-2.3.0 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>update_rubygems Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri Installing rubygems-1.3.3 rdoc into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/rdoc ------------------------------------------------------------------------------ = Announce: RubyGems Release 1.3.3 ... snipped ... RubyGems installed the following executables: C:/ruby/bin/gem ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] - INSTALLATION DIRECTORY: C:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/ruby/lib/ruby/gems/1.8 - C:/Users/bryan/.gem/ruby/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", "http://gems.github.com"] - REMOTE SOURCES: - http://gems.rubyforge.org/ - http://gems.github.com - http://gems.github.com ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2009-05-04 17:20 Message: BTW, I have rdoc 2.4.3 installed. ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-04 17:19 Message: Odd. I was able to update on my Windows Vista box with no issues. RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] - INSTALLATION DIRECTORY: C:/Ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/Ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/Ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/Ruby/lib/ruby/gems/1.8 - C:/Users/djberge/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 From rick.denatale at gmail.com Tue May 5 13:21:59 2009 From: rick.denatale at gmail.com (Rick DeNatale) Date: Tue, 5 May 2009 13:21:59 -0400 Subject: [Rubygems-developers] Alternate dependencies? Message-ID: I just unofficially released my new ri_cal gem to github, then signed up for a runcoderun account which exposed an issue. My gem needs TZInfo, but it's carefully crafted to use either the implementation in the tzinfo gem OR the one provided by activesupport since Rails 2.2. I don't want to dictate which one gets used, and as far as I can see there's no way to put an either/or dependency in the gemspec. Everything works except that since the dependency on tzinfo isn't declared, runcode run doesn't load it and fails. I've brought this up on the runcoderun support site, but I was wondering if this is something that rubygems should think about addressing. Or maybe I'm missing something and there already is a way to do this. -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Twitter: http://twitter.com/RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale From drbrain at segment7.net Tue May 5 14:02:03 2009 From: drbrain at segment7.net (Eric Hodel) Date: Tue, 5 May 2009 11:02:03 -0700 Subject: [Rubygems-developers] Alternate dependencies? In-Reply-To: References: Message-ID: On May 5, 2009, at 10:21, Rick DeNatale wrote: > I just unofficially released my new ri_cal gem to github, then signed > up for a runcoderun account which exposed an issue. > > My gem needs TZInfo, but it's carefully crafted to use either the > implementation in the tzinfo gem OR the one provided by activesupport > since Rails 2.2. I don't want to dictate which one gets used, and as > far as I can see there's no way to put an either/or dependency in the > gemspec. > > Everything works except that since the dependency on tzinfo isn't > declared, runcode run doesn't load it and fails. > > I've brought this up on the runcoderun support site, but I was > wondering if this is something that rubygems should think about > addressing. > > Or maybe I'm missing something and there already is a way to do this. This has been a long-standing feature request, but nobody's been interested enough in actually implementing it. This Could Be You!!! PS: In my opinion, Rails bundling libraries doesn't help matters, they should depend on a specific version of tzinfo and be done with it. From thewoolleyman at gmail.com Tue May 5 14:53:29 2009 From: thewoolleyman at gmail.com (Chad Woolley) Date: Tue, 5 May 2009 11:53:29 -0700 Subject: [Rubygems-developers] Alternate dependencies? In-Reply-To: References: Message-ID: On Tue, May 5, 2009 at 11:02 AM, Eric Hodel wrote: > PS: In my opinion, Rails bundling libraries doesn't help matters, they > should depend on a specific version of tzinfo and be done with it. Yep. From rick.denatale at gmail.com Tue May 5 15:06:59 2009 From: rick.denatale at gmail.com (Rick DeNatale) Date: Tue, 5 May 2009 15:06:59 -0400 Subject: [Rubygems-developers] Alternate dependencies? In-Reply-To: References: Message-ID: On Tue, May 5, 2009 at 2:53 PM, Chad Woolley wrote: > On Tue, May 5, 2009 at 11:02 AM, Eric Hodel wrote: >> PS: In my opinion, Rails bundling libraries doesn't help matters, they >> should depend on a specific version of tzinfo and be done with it. > > Yep. Well that's something that I don't have much control over. -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Twitter: http://twitter.com/RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale From noreply at rubyforge.org Tue May 5 17:54:05 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 5 May 2009 17:54:05 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25777 ] RDoc & Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Message-ID: <20090505215405.EF91018581E9@rubyforge.org> Bugs item #25777, was opened at 2009-05-04 17:11 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 Category: RubyGems installer (setup.rb) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Bryan Soto (bsoto) Assigned to: Nobody (None) Summary: RDoc & Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Initial Comment: Microsoft Windows [Version 6.0.6001] Copyright (c) 2006 Microsoft Corporation. All rights reserved. ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem --version 1.3.2 ----- C:\Users\bryan>gem update --system Updating RubyGems Updating rubygems-update Successfully installed rubygems-update-1.3.3 C:/ruby/lib/ruby/site_ruby/1.8/rubygems/commands/update_command.rb:103:Warning: Gem::SourceIndex#search support for String patterns is deprecated Updating RubyGems to 1.3.3 Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/Commands/cdesc-Commands.yaml ----- C:\Users\bryan>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby setup.rb Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/cdesc-Gem.yaml ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem list --local rdoc *** LOCAL GEMS *** rdoc (2.4.3) rdoc_html_templates (2.3.0) C:\Users\bryan\Desktop\rubygems-1.3.3>gem uninstall rdoc rdoc_html_templates Remove executables: rdoc, ri in addition to the gem? [Yn] y Removing rdoc Removing ri You have requested to uninstall the gem: rdoc-2.4.3 rdoc_html_templates-2.3.0 depends on [rdoc (~> 2.3)] If you remove this gems, one or more dependencies will not be met. Continue with Uninstall? [Yn] y Successfully uninstalled rdoc-2.4.3 Successfully uninstalled rdoc_html_templates-2.3.0 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>update_rubygems Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri Installing rubygems-1.3.3 rdoc into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/rdoc ------------------------------------------------------------------------------ = Announce: RubyGems Release 1.3.3 ... snipped ... RubyGems installed the following executables: C:/ruby/bin/gem ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] - INSTALLATION DIRECTORY: C:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/ruby/lib/ruby/gems/1.8 - C:/Users/bryan/.gem/ruby/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", "http://gems.github.com"] - REMOTE SOURCES: - http://gems.rubyforge.org/ - http://gems.github.com - http://gems.github.com ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2009-05-05 14:54 Message: What are your permissions for: C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri/Gem/Commands/cdesc-Commands.yaml ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-04 17:20 Message: BTW, I have rdoc 2.4.3 installed. ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-04 17:19 Message: Odd. I was able to update on my Windows Vista box with no issues. RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] - INSTALLATION DIRECTORY: C:/Ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/Ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/Ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/Ruby/lib/ruby/gems/1.8 - C:/Users/djberge/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 From noreply at rubyforge.org Tue May 5 18:47:35 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 5 May 2009 18:47:35 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25777 ] RDoc & Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Message-ID: <20090505224736.049BE1678111@rubyforge.org> Bugs item #25777, was opened at 2009-05-04 17:11 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 Category: RubyGems installer (setup.rb) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Bryan Soto (bsoto) Assigned to: Nobody (None) >Summary: RDoc & Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Initial Comment: Microsoft Windows [Version 6.0.6001] Copyright (c) 2006 Microsoft Corporation. All rights reserved. ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem --version 1.3.2 ----- C:\Users\bryan>gem update --system Updating RubyGems Updating rubygems-update Successfully installed rubygems-update-1.3.3 C:/ruby/lib/ruby/site_ruby/1.8/rubygems/commands/update_command.rb:103:Warning: Gem::SourceIndex#search support for String patterns is deprecated Updating RubyGems to 1.3.3 Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/Commands/cdesc-Commands.yaml ----- C:\Users\bryan>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby setup.rb Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/cdesc-Gem.yaml ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem list --local rdoc *** LOCAL GEMS *** rdoc (2.4.3) rdoc_html_templates (2.3.0) C:\Users\bryan\Desktop\rubygems-1.3.3>gem uninstall rdoc rdoc_html_templates Remove executables: rdoc, ri in addition to the gem? [Yn] y Removing rdoc Removing ri You have requested to uninstall the gem: rdoc-2.4.3 rdoc_html_templates-2.3.0 depends on [rdoc (~> 2.3)] If you remove this gems, one or more dependencies will not be met. Continue with Uninstall? [Yn] y Successfully uninstalled rdoc-2.4.3 Successfully uninstalled rdoc_html_templates-2.3.0 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>update_rubygems Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri Installing rubygems-1.3.3 rdoc into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/rdoc ------------------------------------------------------------------------------ = Announce: RubyGems Release 1.3.3 ... snipped ... RubyGems installed the following executables: C:/ruby/bin/gem ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] - INSTALLATION DIRECTORY: C:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/ruby/lib/ruby/gems/1.8 - C:/Users/bryan/.gem/ruby/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", "http://gems.github.com"] - REMOTE SOURCES: - http://gems.rubyforge.org/ - http://gems.github.com - http://gems.github.com ---------------------------------------------------------------------- >Comment By: Bryan Soto (bsoto) Date: 2009-05-05 15:47 Message: Full Control, Modify, Read & Execute, Read and Write. My apologies. I forgot to note that the above command line session was run from a command prompt as Administrator. I originally received the error message as my normal user and thought it was a permission error, so I tried again with the elevated privileges. For what it's worth, my normal user has no problems editing that file through Vim or deleting it from the command prompt. Since it worked for Daniel with the rdoc gem installed, I'm curious if it was the rdoc_html_templates. I'll see if I can duplicate the error and narrow it down a bit more. There doesn't seem to be a huge outcry on this, so I'm obviously an edge case. ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-05-05 14:54 Message: What are your permissions for: C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri/Gem/Commands/cdesc-Commands.yaml ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-04 17:20 Message: BTW, I have rdoc 2.4.3 installed. ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-04 17:19 Message: Odd. I was able to update on my Windows Vista box with no issues. RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] - INSTALLATION DIRECTORY: C:/Ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/Ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/Ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/Ruby/lib/ruby/gems/1.8 - C:/Users/djberge/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 From noreply at rubyforge.org Tue May 5 19:07:23 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 5 May 2009 19:07:23 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Feature Requests-25791 ] Shebang of executables should not expand symlinks Message-ID: <20090505230723.7CD6718581E2@rubyforge.org> Feature Requests item #25791, was opened at 2009-05-06 01:07 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=25791&group_id=126 Category: `gem install` command Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Sven Schwyn (sschwyn) Assigned to: Nobody (None) Summary: Shebang of executables should not expand symlinks Initial Comment: Some distros (such as Gentoo or Debian) allow Ruby 1.8 and 1.9 to be installed both at the same time. Gentoo for instance creates the following files: /usr/bin/ruby18 /usr/bin/ruby19 /usr/bin/ruby -> ruby18 or ruby19 In other words: /usr/bin/ruby is a symlink to the actual version of the ruby interpreter used. Unfortunately, when "gem install" installs a gem with executable scripts, the Ruby interpreter written to the shebang is not the symlink (/usr/bin/ruby) but the expanded symlink (i.e. /usr/bin/ruby18). Is there a reason for this? If not, it would be a great help for package maintainers like me if you could teach RubyGems to use /usr/bin/ruby for the shebang even if it is a symlink. Thanks a lot for considering this. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=25791&group_id=126 From noreply at rubyforge.org Tue May 5 23:32:17 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 5 May 2009 23:32:17 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25777 ] RDoc & amp; Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Message-ID: <20090506033217.8872318581DD@rubyforge.org> Bugs item #25777, was opened at 2009-05-04 17:11 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 Category: RubyGems installer (setup.rb) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Bryan Soto (bsoto) Assigned to: Nobody (None) >Summary: RDoc &amp; Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Initial Comment: Microsoft Windows [Version 6.0.6001] Copyright (c) 2006 Microsoft Corporation. All rights reserved. ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem --version 1.3.2 ----- C:\Users\bryan>gem update --system Updating RubyGems Updating rubygems-update Successfully installed rubygems-update-1.3.3 C:/ruby/lib/ruby/site_ruby/1.8/rubygems/commands/update_command.rb:103:Warning: Gem::SourceIndex#search support for String patterns is deprecated Updating RubyGems to 1.3.3 Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/Commands/cdesc-Commands.yaml ----- C:\Users\bryan>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby setup.rb Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/cdesc-Gem.yaml ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem list --local rdoc *** LOCAL GEMS *** rdoc (2.4.3) rdoc_html_templates (2.3.0) C:\Users\bryan\Desktop\rubygems-1.3.3>gem uninstall rdoc rdoc_html_templates Remove executables: rdoc, ri in addition to the gem? [Yn] y Removing rdoc Removing ri You have requested to uninstall the gem: rdoc-2.4.3 rdoc_html_templates-2.3.0 depends on [rdoc (~> 2.3)] If you remove this gems, one or more dependencies will not be met. Continue with Uninstall? [Yn] y Successfully uninstalled rdoc-2.4.3 Successfully uninstalled rdoc_html_templates-2.3.0 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>update_rubygems Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri Installing rubygems-1.3.3 rdoc into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/rdoc ------------------------------------------------------------------------------ = Announce: RubyGems Release 1.3.3 ... snipped ... RubyGems installed the following executables: C:/ruby/bin/gem ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] - INSTALLATION DIRECTORY: C:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/ruby/lib/ruby/gems/1.8 - C:/Users/bryan/.gem/ruby/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", "http://gems.github.com"] - REMOTE SOURCES: - http://gems.rubyforge.org/ - http://gems.github.com - http://gems.github.com ---------------------------------------------------------------------- >Comment By: Bryan Soto (bsoto) Date: 2009-05-05 20:32 Message: No luck reproducing... Just one of those odd things, I suppose. Unless you have any ideas, I guess there's nothing more to be done. ---------------------------------------------------------------------- Comment By: Bryan Soto (bsoto) Date: 2009-05-05 15:47 Message: Full Control, Modify, Read & Execute, Read and Write. My apologies. I forgot to note that the above command line session was run from a command prompt as Administrator. I originally received the error message as my normal user and thought it was a permission error, so I tried again with the elevated privileges. For what it's worth, my normal user has no problems editing that file through Vim or deleting it from the command prompt. Since it worked for Daniel with the rdoc gem installed, I'm curious if it was the rdoc_html_templates. I'll see if I can duplicate the error and narrow it down a bit more. There doesn't seem to be a huge outcry on this, so I'm obviously an edge case. ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-05-05 14:54 Message: What are your permissions for: C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri/Gem/Commands/cdesc-Commands.yaml ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-04 17:20 Message: BTW, I have rdoc 2.4.3 installed. ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-04 17:19 Message: Odd. I was able to update on my Windows Vista box with no issues. RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] - INSTALLATION DIRECTORY: C:/Ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/Ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/Ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/Ruby/lib/ruby/gems/1.8 - C:/Users/djberge/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 From noreply at rubyforge.org Tue May 5 23:38:42 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 5 May 2009 23:38:42 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25777 ] RDoc & amp; Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Message-ID: <20090506033842.DF5DB1858102@rubyforge.org> Bugs item #25777, was opened at 2009-05-04 17:11 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 Category: RubyGems installer (setup.rb) >Group: v1.3.x >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: Bryan Soto (bsoto) >Assigned to: Daniel Berger (djberg96) Summary: RDoc &amp; Ri fail on both gem update and ruby setup.rb when using rdoc gem on MS Vista. Initial Comment: Microsoft Windows [Version 6.0.6001] Copyright (c) 2006 Microsoft Corporation. All rights reserved. ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem --version 1.3.2 ----- C:\Users\bryan>gem update --system Updating RubyGems Updating rubygems-update Successfully installed rubygems-update-1.3.3 C:/ruby/lib/ruby/site_ruby/1.8/rubygems/commands/update_command.rb:103:Warning: Gem::SourceIndex#search support for String patterns is deprecated Updating RubyGems to 1.3.3 Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/Commands/cdesc-Commands.yaml ----- C:\Users\bryan>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>ruby setup.rb Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri ERROR: While executing gem ... (Errno::EACCES) Permission denied - ./Gem/cdesc-Gem.yaml ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem list --local rdoc *** LOCAL GEMS *** rdoc (2.4.3) rdoc_html_templates (2.3.0) C:\Users\bryan\Desktop\rubygems-1.3.3>gem uninstall rdoc rdoc_html_templates Remove executables: rdoc, ri in addition to the gem? [Yn] y Removing rdoc Removing ri You have requested to uninstall the gem: rdoc-2.4.3 rdoc_html_templates-2.3.0 depends on [rdoc (~> 2.3)] If you remove this gems, one or more dependencies will not be met. Continue with Uninstall? [Yn] y Successfully uninstalled rdoc-2.4.3 Successfully uninstalled rdoc_html_templates-2.3.0 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>rmdir /s /q C:\ruby\lib\ruby\gems\1.8\doc\rubygems-1.3.3 ----- C:\Users\bryan\Desktop\rubygems-1.3.3>update_rubygems Installing RubyGems 1.3.3 Installing RubyGems Installing gem executable Removing old source_cache files Removing old RubyGems RDoc and ri Installing rubygems-1.3.3 ri into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri Installing rubygems-1.3.3 rdoc into C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/rdoc ------------------------------------------------------------------------------ = Announce: RubyGems Release 1.3.3 ... snipped ... RubyGems installed the following executables: C:/ruby/bin/gem ----- C:\Users\bryan\Desktop\rubygems-1.3.3>gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] - INSTALLATION DIRECTORY: C:/ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/ruby/lib/ruby/gems/1.8 - C:/Users/bryan/.gem/ruby/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", "http://gems.github.com"] - REMOTE SOURCES: - http://gems.rubyforge.org/ - http://gems.github.com - http://gems.github.com ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2009-05-05 20:38 Message: The only thing I can think of is that some other process had the file open when you tried to update rubygems, which would cause the same error. I'm going to close this one out for now. If it pops up again and you can narrow it down, go ahead and re-open it. Regards, Dan ---------------------------------------------------------------------- Comment By: Bryan Soto (bsoto) Date: 2009-05-05 20:32 Message: No luck reproducing... Just one of those odd things, I suppose. Unless you have any ideas, I guess there's nothing more to be done. ---------------------------------------------------------------------- Comment By: Bryan Soto (bsoto) Date: 2009-05-05 15:47 Message: Full Control, Modify, Read & Execute, Read and Write. My apologies. I forgot to note that the above command line session was run from a command prompt as Administrator. I originally received the error message as my normal user and thought it was a permission error, so I tried again with the elevated privileges. For what it's worth, my normal user has no problems editing that file through Vim or deleting it from the command prompt. Since it worked for Daniel with the rdoc gem installed, I'm curious if it was the rdoc_html_templates. I'll see if I can duplicate the error and narrow it down a bit more. There doesn't seem to be a huge outcry on this, so I'm obviously an edge case. ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-05-05 14:54 Message: What are your permissions for: C:/ruby/lib/ruby/gems/1.8/doc/rubygems-1.3.3/ri/Gem/Commands/cdesc-Commands.yaml ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-04 17:20 Message: BTW, I have rdoc 2.4.3 installed. ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-04 17:19 Message: Odd. I was able to update on my Windows Vista box with no issues. RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] - INSTALLATION DIRECTORY: C:/Ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: C:/Ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: C:/Ruby/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/Ruby/lib/ruby/gems/1.8 - C:/Users/djberge/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25777&group_id=126 From noreply at rubyforge.org Tue May 5 23:39:43 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 5 May 2009 23:39:43 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25509 ] exception using new generate_index in 1.3.2 Message-ID: <20090506033943.809E01678111@rubyforge.org> Bugs item #25509, was opened at 2009-04-16 13:15 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25509&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: Accepted Priority: 3 Submitted By: Johnathan Conley (jconley) Assigned to: Eric Hodel (drbrain) Summary: exception using new generate_index in 1.3.2 Initial Comment: After upgrading to 1.3.2, I wiped out my old indexes, and build a full index from scratch. Everything worked fine... but afterwards I rsyned with the upstream server, one new gem was available... and then I ran generate_index with the --update option and received this error... receiving file list ... done Onion-0.0.2.gem sent 240 bytes received 623761 bytes 83200.13 bytes/sec total size is 4929983101 speedup is 7900.60 $ gem generate_index --no-legacy --update -d /home/mirror/www --backtrace Loading 1 gems from /home/mirror/www . Loaded all gems loaded: 0.004s Generating Marshal quick index gemspecs for 1 gems . Complete Generated Marshal quick index gemspecs: 0.001s ERROR: While executing gem ... (NoMethodError) undefined method `<=>' for nil:NilClass /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `<=>' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `sort' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `update_specs_index' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:656:in `update_index' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems.rb:966:in `time' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:655:in `update_index' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/commands/generate_index_command.rb:125:in `execute' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run' /opt/ruby/bin/gem:21 Below is the output from the first full index build... likely won't help since it completed without errors. Complete Generated Marshal quick index gemspecs: 11.859s Generating specs index WARNING: Skipping invalid platform in gem: win32-api-1.0.4-x86-mswin32-60 Generated specs index: 0.483s Generating latest specs index Generated latest specs index: 0.094s Generating prerelease specs index Generated prerelease specs index: 0.000s Compressing indicies Compressed indicies: 0.068s ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2009-05-05 20:39 Message: Still happening with 1.3.3? ---------------------------------------------------------------------- Comment By: Johnathan Conley (jconley) Date: 2009-04-16 17:24 Message: Here is my latest run with -V $ ./mirror-rubygems.sh receiving file list ... done ./ gem_tools-0.2.0.gem graph-1.1.0.gem hoe-1.12.2.gem mingle-macro-development-toolkit-1.2.gem provisional-1.2.5.gem rforce-0.3.gem unicorn-0.5.2.gem sent 378 bytes received 796293 bytes 75873.43 bytes/sec total size is 4930164349 speedup is 6188.46 Loading 8 gems from /home/mirror/www 1/8: mingle-macro-development-toolkit-1.2 2/8: hoe-1.12.2 3/8: graph-1.1.0 4/8: gem_tools-0.2.0 5/8: unicorn-0.5.2 6/8: Onion-0.0.2 7/8: provisional-1.2.5 8/8: rforce-0.3 Loaded all gems loaded: 0.097s Generating Marshal quick index gemspecs for 8 gems 1/8: gem_tools-0.2.0 2/8: provisional-1.2.5 3/8: graph-1.1.0 4/8: rforce-0.3 5/8: hoe-1.12.2 6/8: unicorn-0.5.2 7/8: Onion-0.0.2 8/8: mingle-macro-development-toolkit-1.2 Complete Generated Marshal quick index gemspecs: 0.030s ERROR: While executing gem ... (NoMethodError) undefined method `<=>' for nil:NilClass /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `<=>' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `sort' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `update_specs_index' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:656:in `update_index' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems.rb:966:in `time' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:655:in `update_index' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/commands/generate_index_command.rb:125:in `execute' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run' /opt/ruby/bin/gem:21 ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-04-16 13:40 Message: Can you run with -V as well? gem generate_index --no-legacy --update -d /home/mirror/www --backtrace -V This should give the gem that's causing the problem. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25509&group_id=126 From djberg96 at gmail.com Wed May 6 09:40:10 2009 From: djberg96 at gmail.com (Daniel Berger) Date: Wed, 6 May 2009 07:40:10 -0600 Subject: [Rubygems-developers] Question about test_gem_commands_install_command.rb Message-ID: <6037b70c0905060640v659854a0s4799485f145bab4d@mail.gmail.com> Hi, Ruby 1.8.6-p111 I was running the rubygems tests on Vista tonight and I hit this one: C:\Users\djberge\workspace\rubygems>ruby -Ilib test\test_gem_commands_install_command.rb Loaded suite test/test_gem_commands_install_command Started ....F...... Finished in 4.055000 seconds. 1) Failure: test_no_user_install(TestGemCommandsInstallCommand) [test/test_gem_commands_install_command.rb:122]: [Gem::FilePermissionError] exception expected, not Class: Message: <"Exiting RubyGems with exit_code 0"> ---Backtrace--- C:/Users/djberge/workspace/rubygems/test/../lib/rubygems/commands/install_co mmand.rb:130:in `execute' test/test_gem_commands_install_command.rb:123:in `test_no_user_install' C:/Ruby/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:135:in `assert_raises' test/test_gem_commands_install_command.rb:122:in `test_no_user_install' ./lib/rubygems/user_interaction.rb:40:in `use_ui' ./lib/rubygems/user_interaction.rb:63:in `use_ui' test/test_gem_commands_install_command.rb:115:in `test_no_user_install' C:/Ruby/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:434:in `__send__' C:/Ruby/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:434:in `run' C:/Ruby/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:413:in `run_test_suites' C:/Ruby/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:407:in `each' C:/Ruby/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:407:in `run_test_suites' C:/Ruby/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:406:in `each' C:/Ruby/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:406:in `run_test_suites' C:/Ruby/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:386:in `run' C:/Ruby/lib/ruby/gems/1.8/gems/minitest-1.3.1/lib/minitest/unit.rb:327:in `autorun' test/test_gem_commands_install_command.rb:227 --------------- 11 tests, 50 assertions, 1 failures, 0 errors, 0 skips The test itself should probably be skipped on Windows since it's based on a 0755/0555 perm setting, which Windows won't understand (it only understands 0644 and 0444). What's confusing me is how this test -ever- passed on Windows, but I don't see a change to the file since March 7th, 2009. Any ideas why it would suddenly start failing? And shouldn't we just skip it on Windows? Regards, Dan From noreply at rubyforge.org Wed May 6 16:03:55 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 6 May 2009 16:03:55 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25810 ] undefined method `manage_gems' Message-ID: <20090506200355.C58491858104@rubyforge.org> Bugs item #25810, was opened at 06/05/2009 22:03 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25810&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: J?r?my Lecour (eboss) Assigned to: Nobody (None) Summary: undefined method `manage_gems' Initial Comment: Hello, On a debian Etch, I suddenly get this error : /usr/bin/gem:11: undefined method `manage_gems' for Gem:Module (NoMethodError) ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25810&group_id=126 From noreply at rubyforge.org Wed May 6 16:25:36 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 6 May 2009 16:25:36 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25810 ] undefined method `manage_gems' Message-ID: <20090506202536.AE9AD1D787EA@rubyforge.org> Bugs item #25810, was opened at 2009-05-06 13:03 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25810&group_id=126 Category: `gem` commands (other) Group: v1.3.x >Status: Closed >Resolution: Out of Date Priority: 3 Submitted By: J?r?my Lecour (eboss) >Assigned to: Daniel Berger (djberg96) Summary: undefined method `manage_gems' Initial Comment: Hello, On a debian Etch, I suddenly get this error : /usr/bin/gem:11: undefined method `manage_gems' for Gem:Module (NoMethodError) ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2009-05-06 13:25 Message: The manage_gems method had been deprecated for quite some time and was finally removed. It should be removed from your gemspec. Or, if you prefer to maintain backwards compatibility, you can do this: Gem.manage_gems if Gem::RubyGemsVersion.to_f < 1.0 Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25810&group_id=126 From noreply at rubyforge.org Wed May 6 16:42:49 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 6 May 2009 16:42:49 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25810 ] undefined method `manage_gems' Message-ID: <20090506204249.E43751D78801@rubyforge.org> Bugs item #25810, was opened at 06/05/2009 22:03 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25810&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Closed Resolution: Out of Date Priority: 3 Submitted By: J?r?my Lecour (eboss) Assigned to: Daniel Berger (djberg96) Summary: undefined method `manage_gems' Initial Comment: Hello, On a debian Etch, I suddenly get this error : /usr/bin/gem:11: undefined method `manage_gems' for Gem:Module (NoMethodError) ---------------------------------------------------------------------- >Comment By: J?r?my Lecour (eboss) Date: 06/05/2009 22:42 Message: Hi Dan, Thanks for the quick answer. I get this error when I do a simple "$ sudo gem list" or "$ sudo gem update". I don't maintain any gem so I don't really get what you mean by "It should be removed from your gemspec". Cheers J?r?my ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 06/05/2009 22:25 Message: The manage_gems method had been deprecated for quite some time and was finally removed. It should be removed from your gemspec. Or, if you prefer to maintain backwards compatibility, you can do this: Gem.manage_gems if Gem::RubyGemsVersion.to_f < 1.0 Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25810&group_id=126 From noreply at rubyforge.org Wed May 6 17:11:21 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 6 May 2009 17:11:21 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25810 ] undefined method `manage_gems' Message-ID: <20090506211121.3CBD118580F8@rubyforge.org> Bugs item #25810, was opened at 2009-05-06 13:03 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25810&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Closed Resolution: Out of Date Priority: 3 Submitted By: J?r?my Lecour (eboss) Assigned to: Daniel Berger (djberg96) Summary: undefined method `manage_gems' Initial Comment: Hello, On a debian Etch, I suddenly get this error : /usr/bin/gem:11: undefined method `manage_gems' for Gem:Module (NoMethodError) ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2009-05-06 14:11 Message: You haven't been paying attention to the install messages, at the end it printed out where it installed gem, which was likely `gem1.8` or `gem18` at the end of the upgrade, not `gem`. The last half of this blog post will help you out: http://blog.segment7.net/articles/2009/01/15/usr-bin-gems-reports-gem-manage_gems-is-deprecated ---------------------------------------------------------------------- Comment By: J?r?my Lecour (eboss) Date: 2009-05-06 13:42 Message: Hi Dan, Thanks for the quick answer. I get this error when I do a simple "$ sudo gem list" or "$ sudo gem update". I don't maintain any gem so I don't really get what you mean by "It should be removed from your gemspec". Cheers J?r?my ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-06 13:25 Message: The manage_gems method had been deprecated for quite some time and was finally removed. It should be removed from your gemspec. Or, if you prefer to maintain backwards compatibility, you can do this: Gem.manage_gems if Gem::RubyGemsVersion.to_f < 1.0 Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25810&group_id=126 From noreply at rubyforge.org Wed May 6 17:58:20 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 6 May 2009 17:58:20 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25810 ] undefined method `manage_gems' Message-ID: <20090506215820.F274518581F2@rubyforge.org> Bugs item #25810, was opened at 06/05/2009 22:03 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25810&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Closed Resolution: Out of Date Priority: 3 Submitted By: J?r?my Lecour (eboss) Assigned to: Daniel Berger (djberg96) Summary: undefined method `manage_gems' Initial Comment: Hello, On a debian Etch, I suddenly get this error : /usr/bin/gem:11: undefined method `manage_gems' for Gem:Module (NoMethodError) ---------------------------------------------------------------------- >Comment By: J?r?my Lecour (eboss) Date: 06/05/2009 23:58 Message: Thank you Eric, it's obviously working right now. I'm sorry I didn't read your install message this time. I know that you take it seriously and always make them clear and complete and I than you for that too. ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 06/05/2009 23:11 Message: You haven't been paying attention to the install messages, at the end it printed out where it installed gem, which was likely `gem1.8` or `gem18` at the end of the upgrade, not `gem`. The last half of this blog post will help you out: http://blog.segment7.net/articles/2009/01/15/usr-bin-gems-reports-gem-manage_gems-is-deprecated ---------------------------------------------------------------------- Comment By: J?r?my Lecour (eboss) Date: 06/05/2009 22:42 Message: Hi Dan, Thanks for the quick answer. I get this error when I do a simple "$ sudo gem list" or "$ sudo gem update". I don't maintain any gem so I don't really get what you mean by "It should be removed from your gemspec". Cheers J?r?my ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 06/05/2009 22:25 Message: The manage_gems method had been deprecated for quite some time and was finally removed. It should be removed from your gemspec. Or, if you prefer to maintain backwards compatibility, you can do this: Gem.manage_gems if Gem::RubyGemsVersion.to_f < 1.0 Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25810&group_id=126 From noreply at rubyforge.org Wed May 6 22:42:12 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 6 May 2009 22:42:12 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25816 ] misleading error message when one of many sources unreachable. Message-ID: <20090507024212.35D691D78804@rubyforge.org> Bugs item #25816, was opened at 2009-05-07 02:42 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25816&group_id=126 Category: `gem install` command Group: None Status: Open Resolution: None Priority: 3 Submitted By: Larry Kyrala (coldnebo) Assigned to: Nobody (None) Summary: misleading error message when one of many sources unreachable. Initial Comment: I puzzled over the following for about half an hour: $ sudo gem install hoe ERROR: While executing gem ... (Zlib::GzipFile::Error) not in gzip format Until I finally figured out that one of my sources (aka 'gem sources') was a address only accessible on my company's VPN. (I wasn't on the VPN at the time.) e.g: $ gem sources *** CURRENT SOURCES *** http://gems.rubyforge.org/ http://rubygems.xxx.xxx/ <-- vpn address This error was confusing, because I was attempting to get 'hoe' which is clearly at gems.rubyforge.org, however apparently gem attempts to ping ALL the sources, even if one isn't available, it croaks with this obscure error. At least this should be documented. At most, gem should return a meaningful error if one of the gem sources is unreachable. Ideally, if the install name is found in one of the gem sources that IS available, it shouldn't matter, and should simply install the gem from the available source. Other info: using Mac OSX 10.5 Macports: $ port installed | grep ruby rb-rubygems @1.3.1_0 (active) ruby @1.8.7-p72_2+thread_hooks ruby @1.8.7-p160_1+thread_hooks (active) ruby186 @1.8.6-p287_0+darwin_9+thread_hooks Hope this helps! -lk ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25816&group_id=126 From noreply at rubyforge.org Wed May 6 22:43:29 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 6 May 2009 22:43:29 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25816 ] misleading error message when one of many sources unreachable. Message-ID: <20090507024329.9B8C81D78801@rubyforge.org> Bugs item #25816, was opened at 2009-05-07 02:42 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25816&group_id=126 Category: `gem install` command Group: None Status: Open Resolution: None Priority: 3 Submitted By: Larry Kyrala (coldnebo) Assigned to: Nobody (None) Summary: misleading error message when one of many sources unreachable. Initial Comment: I puzzled over the following for about half an hour: $ sudo gem install hoe ERROR: While executing gem ... (Zlib::GzipFile::Error) not in gzip format Until I finally figured out that one of my sources (aka 'gem sources') was a address only accessible on my company's VPN. (I wasn't on the VPN at the time.) e.g: $ gem sources *** CURRENT SOURCES *** http://gems.rubyforge.org/ http://rubygems.xxx.xxx/ <-- vpn address This error was confusing, because I was attempting to get 'hoe' which is clearly at gems.rubyforge.org, however apparently gem attempts to ping ALL the sources, even if one isn't available, it croaks with this obscure error. At least this should be documented. At most, gem should return a meaningful error if one of the gem sources is unreachable. Ideally, if the install name is found in one of the gem sources that IS available, it shouldn't matter, and should simply install the gem from the available source. Other info: using Mac OSX 10.5 Macports: $ port installed | grep ruby rb-rubygems @1.3.1_0 (active) ruby @1.8.7-p72_2+thread_hooks ruby @1.8.7-p160_1+thread_hooks (active) ruby186 @1.8.6-p287_0+darwin_9+thread_hooks Hope this helps! -lk ---------------------------------------------------------------------- >Comment By: Larry Kyrala (coldnebo) Date: 2009-05-07 02:43 Message: BTW, I forgot to mention the workaround: Simply remove the source that is unreachable and gem works fine. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25816&group_id=126 From thewoolleyman at gmail.com Thu May 7 01:21:43 2009 From: thewoolleyman at gmail.com (Chad Woolley) Date: Wed, 6 May 2009 22:21:43 -0700 Subject: [Rubygems-developers] Latest and greatest instructions for setting up a public gem server? In-Reply-To: <5795D810-2914-41BA-B8A6-4C9FBB839DD1@segment7.net> References: <5795D810-2914-41BA-B8A6-4C9FBB839DD1@segment7.net> Message-ID: On Tue, Mar 31, 2009 at 1:51 PM, Eric Hodel wrote: > On Mar 31, 2009, at 10:45, Chad Woolley wrote: > >> Any suggestions? ?Including example scripts, cron jobs, etc? > > gem help generate_index Here's my cron job - assumes user can write to nginx-default and nginx-default/gems exists: * * * * * gem generate_index --directory=/var/www/nginx-default >> /home/user/gem_generate_index.log 2>&1 From noreply at rubyforge.org Thu May 7 06:43:33 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 7 May 2009 06:43:33 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25826 ] Uninstalling executables created with --format-executable Message-ID: <20090507104333.53D1418580F5@rubyforge.org> Bugs item #25826, was opened at 2009-05-07 12:43 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25826&group_id=126 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Sven Schwyn (sschwyn) Assigned to: Nobody (None) Summary: Uninstalling executables created with --format-executable Initial Comment: Here's an example: gem install --format-executable rake ==> Installs executable "rake18". ln -s rake18 rake ==> This step is performed by most Linux distros. gem uninstall rake ==> Asks whether to uninstall "rake", but not "rake18". ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25826&group_id=126 From noreply at rubyforge.org Thu May 7 17:03:01 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 7 May 2009 17:03:01 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25509 ] exception using new generate_index in 1.3.2 Message-ID: <20090507210301.1C1EA18581E4@rubyforge.org> Bugs item #25509, was opened at 2009-04-16 15:15 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25509&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: Accepted Priority: 3 Submitted By: Johnathan Conley (jconley) Assigned to: Eric Hodel (drbrain) Summary: exception using new generate_index in 1.3.2 Initial Comment: After upgrading to 1.3.2, I wiped out my old indexes, and build a full index from scratch. Everything worked fine... but afterwards I rsyned with the upstream server, one new gem was available... and then I ran generate_index with the --update option and received this error... receiving file list ... done Onion-0.0.2.gem sent 240 bytes received 623761 bytes 83200.13 bytes/sec total size is 4929983101 speedup is 7900.60 $ gem generate_index --no-legacy --update -d /home/mirror/www --backtrace Loading 1 gems from /home/mirror/www . Loaded all gems loaded: 0.004s Generating Marshal quick index gemspecs for 1 gems . Complete Generated Marshal quick index gemspecs: 0.001s ERROR: While executing gem ... (NoMethodError) undefined method `<=>' for nil:NilClass /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `<=>' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `sort' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `update_specs_index' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:656:in `update_index' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems.rb:966:in `time' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:655:in `update_index' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/commands/generate_index_command.rb:125:in `execute' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run' /opt/ruby/bin/gem:21 Below is the output from the first full index build... likely won't help since it completed without errors. Complete Generated Marshal quick index gemspecs: 11.859s Generating specs index WARNING: Skipping invalid platform in gem: win32-api-1.0.4-x86-mswin32-60 Generated specs index: 0.483s Generating latest specs index Generated latest specs index: 0.094s Generating prerelease specs index Generated prerelease specs index: 0.000s Compressing indicies Compressed indicies: 0.068s ---------------------------------------------------------------------- >Comment By: Johnathan Conley (jconley) Date: 2009-05-07 16:03 Message: yes, still happening... same error and line ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-05 22:39 Message: Still happening with 1.3.3? ---------------------------------------------------------------------- Comment By: Johnathan Conley (jconley) Date: 2009-04-16 19:24 Message: Here is my latest run with -V $ ./mirror-rubygems.sh receiving file list ... done ./ gem_tools-0.2.0.gem graph-1.1.0.gem hoe-1.12.2.gem mingle-macro-development-toolkit-1.2.gem provisional-1.2.5.gem rforce-0.3.gem unicorn-0.5.2.gem sent 378 bytes received 796293 bytes 75873.43 bytes/sec total size is 4930164349 speedup is 6188.46 Loading 8 gems from /home/mirror/www 1/8: mingle-macro-development-toolkit-1.2 2/8: hoe-1.12.2 3/8: graph-1.1.0 4/8: gem_tools-0.2.0 5/8: unicorn-0.5.2 6/8: Onion-0.0.2 7/8: provisional-1.2.5 8/8: rforce-0.3 Loaded all gems loaded: 0.097s Generating Marshal quick index gemspecs for 8 gems 1/8: gem_tools-0.2.0 2/8: provisional-1.2.5 3/8: graph-1.1.0 4/8: rforce-0.3 5/8: hoe-1.12.2 6/8: unicorn-0.5.2 7/8: Onion-0.0.2 8/8: mingle-macro-development-toolkit-1.2 Complete Generated Marshal quick index gemspecs: 0.030s ERROR: While executing gem ... (NoMethodError) undefined method `<=>' for nil:NilClass /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `<=>' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `sort' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:703:in `update_specs_index' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:656:in `update_index' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems.rb:966:in `time' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/indexer.rb:655:in `update_index' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/commands/generate_index_command.rb:125:in `execute' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run' /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run' /opt/ruby/bin/gem:21 ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-04-16 15:40 Message: Can you run with -V as well? gem generate_index --no-legacy --update -d /home/mirror/www --backtrace -V This should give the gem that's causing the problem. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25509&group_id=126 From noreply at rubyforge.org Sat May 9 13:16:02 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 9 May 2009 13:16:02 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Patches-25854 ] Import/Export Patch Message-ID: <20090509171603.12E821858134@rubyforge.org> Patches item #25854, was opened at 2009-05-09 12:16 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=25854&group_id=126 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Peer Allan (pallan) Assigned to: Nobody (None) Summary: Import/Export Patch Initial Comment: This patch is not fully complete, but I was not sure how else I could get developers who are more in the know to get a look at i before I went too far. There are a couple parts to this patch. First I added a "--format" option to the query command. The only valid option at the moment is 'yaml' - added "--format" to the query command, accepted options right now is 'yaml' - when the --format is set to yaml it also includes the sources in the dump - added "export" command that basically does a list with the yaml format - added "import" command that reads a list of supplied gems from a yaml file and installs them TODOs: - complete tests, there are some, but I was not sure exactly how to test some parts of it - move the sources dump to the export command - add sources support to the import command, i.e. make sure all the sources in the yaml file are available, and if not add them The idea behind this patch would be for user to be able to create gem templates so that when they are setting up a new system all they have to do is supply the yaml file to the import command with the supplied Yaml file to install all the gems they require. Let me know what you think. Thanks Peer ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=25854&group_id=126 From noreply at rubyforge.org Tue May 12 08:01:19 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 12 May 2009 08:01:19 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25882 ] Handling of Windows paths broken in 1.3.3 Message-ID: <20090512120119.9D51918580E9@rubyforge.org> Bugs item #25882, was opened at 2009-05-12 14:01 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 Category: `gem install` command Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Lars Christensen (larsch) Assigned to: Nobody (None) Summary: Handling of Windows paths broken in 1.3.3 Initial Comment: Installing gems from local drives other than the current is broken on Windows. RubyGems strips the drive letter (through using the URI class for something which isn't an URI). C:\> gem install p:\path\to\mygem-2.1.18.gem ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - /path/to/mygem-2.1.18.gem Then I tried to pass a valid URI: C:\> gem install file:///p:/path/to/mygem-2.1.18.gem But that doesn't work either; ERROR: could not find gem file:///p:/path/to/mygem-2.1.18.gem locally or in a repository I believe this is because URI#path returns "/p:/path/to/mygem..." (with leading slash), which is not a valid path on Windows. Finally, I attempted to hack RubyGems to prefix file:/// itself, but I don't understand the reason for this line of code in remote_fetcher.rb: remote_gem_path = File.join(path, 'gems', gem_file_name) That causes this error instead: ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - p:/path/to/gems/mygem-2.1.18.gem Notice the extra /gems/ path. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 From noreply at rubyforge.org Tue May 12 08:20:29 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 12 May 2009 08:20:29 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25882 ] Handling of Windows paths broken in 1.3.3 Message-ID: <20090512122107.6612218580F6@rubyforge.org> Bugs item #25882, was opened at 2009-05-12 05:01 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 Category: `gem install` command Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Lars Christensen (larsch) Assigned to: Nobody (None) Summary: Handling of Windows paths broken in 1.3.3 Initial Comment: Installing gems from local drives other than the current is broken on Windows. RubyGems strips the drive letter (through using the URI class for something which isn't an URI). C:\> gem install p:\path\to\mygem-2.1.18.gem ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - /path/to/mygem-2.1.18.gem Then I tried to pass a valid URI: C:\> gem install file:///p:/path/to/mygem-2.1.18.gem But that doesn't work either; ERROR: could not find gem file:///p:/path/to/mygem-2.1.18.gem locally or in a repository I believe this is because URI#path returns "/p:/path/to/mygem..." (with leading slash), which is not a valid path on Windows. Finally, I attempted to hack RubyGems to prefix file:/// itself, but I don't understand the reason for this line of code in remote_fetcher.rb: remote_gem_path = File.join(path, 'gems', gem_file_name) That causes this error instead: ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - p:/path/to/gems/mygem-2.1.18.gem Notice the extra /gems/ path. ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2009-05-12 05:20 Message: The use of file urls is meant for use with the --source flag (i.e. from a local repository), which is why the method includes the 'gems' directory. However, the "gem install p:\path\to\mygem-2.1.18.gem" should work. I'll take a look. Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 From noreply at rubyforge.org Tue May 12 09:22:15 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 12 May 2009 09:22:15 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25882 ] Handling of Windows paths broken in 1.3.3 Message-ID: <20090512132215.B678C18580E2@rubyforge.org> Bugs item #25882, was opened at 2009-05-12 05:01 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 Category: `gem install` command Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Lars Christensen (larsch) Assigned to: Nobody (None) Summary: Handling of Windows paths broken in 1.3.3 Initial Comment: Installing gems from local drives other than the current is broken on Windows. RubyGems strips the drive letter (through using the URI class for something which isn't an URI). C:\> gem install p:\path\to\mygem-2.1.18.gem ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - /path/to/mygem-2.1.18.gem Then I tried to pass a valid URI: C:\> gem install file:///p:/path/to/mygem-2.1.18.gem But that doesn't work either; ERROR: could not find gem file:///p:/path/to/mygem-2.1.18.gem locally or in a repository I believe this is because URI#path returns "/p:/path/to/mygem..." (with leading slash), which is not a valid path on Windows. Finally, I attempted to hack RubyGems to prefix file:/// itself, but I don't understand the reason for this line of code in remote_fetcher.rb: remote_gem_path = File.join(path, 'gems', gem_file_name) That causes this error instead: ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - p:/path/to/gems/mygem-2.1.18.gem Notice the extra /gems/ path. ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2009-05-12 06:22 Message: Well, this is odd. I tried installing from an explicit path using "C:\Documents and Settings\djberge". That worked fine. But, when I tried to install from a drive other than "C:", things went bad: C:\Documents and Settings\djberge>gem install "z:\djberge on my mac\documents\workspace\ptools\ptools-1.1.7.gem" --verbose --debug Exception `NameError' at C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:161 - uninitialized constant Gem::Commands::InstallCommand Exception `IOError' at C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/format.rb:50 - closed stream Installing gem ptools-1.1.7 Exception `Errno::ENOENT' at C:/Ruby/lib/ruby/1.8/fileutils.rb:1200 - No such file or directory - /djberge on my mac/documents/workspace/ptools/ptools-1.1.7.gem ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - /djberge on my mac/documents/workspace/ptools/ptools-1.1.7.gem C:/Ruby/lib/ruby/1.8/fileutils.rb:1200:in `stat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1200:in `lstat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1178:in `stat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1260:in `copy_file' C:/Ruby/lib/ruby/1.8/fileutils.rb:463:in `copy_file' C:/Ruby/lib/ruby/1.8/fileutils.rb:383:in `cp' C:/Ruby/lib/ruby/1.8/fileutils.rb:1395:in `fu_each_src_dest' C:/Ruby/lib/ruby/1.8/fileutils.rb:1411:in `fu_each_src_dest0' C:/Ruby/lib/ruby/1.8/fileutils.rb:1393:in `fu_each_src_dest' C:/Ruby/lib/ruby/1.8/fileutils.rb:382:in `cp' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/remote_fetcher.rb:142:in `download' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:232:in `install' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:222:in `each' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:222:in `install' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:78:in `execute' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:75:in `each' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:75:in `execute' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run' C:/Ruby/bin/gem:21 I'll have to investigate further to determine if this is a bug in rubygems or fileutils. Regards, Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 05:20 Message: The use of file urls is meant for use with the --source flag (i.e. from a local repository), which is why the method includes the 'gems' directory. However, the "gem install p:\path\to\mygem-2.1.18.gem" should work. I'll take a look. Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 From noreply at rubyforge.org Tue May 12 09:46:55 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 12 May 2009 09:46:55 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25882 ] Handling of Windows paths broken in 1.3.3 Message-ID: <20090512134655.833B718580EB@rubyforge.org> Bugs item #25882, was opened at 2009-05-12 05:01 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 Category: `gem install` command Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Lars Christensen (larsch) Assigned to: Nobody (None) Summary: Handling of Windows paths broken in 1.3.3 Initial Comment: Installing gems from local drives other than the current is broken on Windows. RubyGems strips the drive letter (through using the URI class for something which isn't an URI). C:\> gem install p:\path\to\mygem-2.1.18.gem ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - /path/to/mygem-2.1.18.gem Then I tried to pass a valid URI: C:\> gem install file:///p:/path/to/mygem-2.1.18.gem But that doesn't work either; ERROR: could not find gem file:///p:/path/to/mygem-2.1.18.gem locally or in a repository I believe this is because URI#path returns "/p:/path/to/mygem..." (with leading slash), which is not a valid path on Windows. Finally, I attempted to hack RubyGems to prefix file:/// itself, but I don't understand the reason for this line of code in remote_fetcher.rb: remote_gem_path = File.join(path, 'gems', gem_file_name) That causes this error instead: ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - p:/path/to/gems/mygem-2.1.18.gem Notice the extra /gems/ path. ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2009-05-12 06:46 Message: Looks like a bug in line 142 of remote_fetcher.rb related to the URI class and the fact that we're stripping the scheme off of Windows paths. It works for "C:" because, iirc, certain Ruby core File methods assume "C:" if no drive is found. We'll have to fix this. Regards, Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 06:22 Message: Well, this is odd. I tried installing from an explicit path using "C:\Documents and Settings\djberge". That worked fine. But, when I tried to install from a drive other than "C:", things went bad: C:\Documents and Settings\djberge>gem install "z:\djberge on my mac\documents\workspace\ptools\ptools-1.1.7.gem" --verbose --debug Exception `NameError' at C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:161 - uninitialized constant Gem::Commands::InstallCommand Exception `IOError' at C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/format.rb:50 - closed stream Installing gem ptools-1.1.7 Exception `Errno::ENOENT' at C:/Ruby/lib/ruby/1.8/fileutils.rb:1200 - No such file or directory - /djberge on my mac/documents/workspace/ptools/ptools-1.1.7.gem ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - /djberge on my mac/documents/workspace/ptools/ptools-1.1.7.gem C:/Ruby/lib/ruby/1.8/fileutils.rb:1200:in `stat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1200:in `lstat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1178:in `stat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1260:in `copy_file' C:/Ruby/lib/ruby/1.8/fileutils.rb:463:in `copy_file' C:/Ruby/lib/ruby/1.8/fileutils.rb:383:in `cp' C:/Ruby/lib/ruby/1.8/fileutils.rb:1395:in `fu_each_src_dest' C:/Ruby/lib/ruby/1.8/fileutils.rb:1411:in `fu_each_src_dest0' C:/Ruby/lib/ruby/1.8/fileutils.rb:1393:in `fu_each_src_dest' C:/Ruby/lib/ruby/1.8/fileutils.rb:382:in `cp' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/remote_fetcher.rb:142:in `download' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:232:in `install' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:222:in `each' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:222:in `install' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:78:in `execute' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:75:in `each' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:75:in `execute' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run' C:/Ruby/bin/gem:21 I'll have to investigate further to determine if this is a bug in rubygems or fileutils. Regards, Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 05:20 Message: The use of file urls is meant for use with the --source flag (i.e. from a local repository), which is why the method includes the 'gems' directory. However, the "gem install p:\path\to\mygem-2.1.18.gem" should work. I'll take a look. Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 From noreply at rubyforge.org Tue May 12 11:51:32 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 12 May 2009 11:51:32 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25882 ] Handling of Windows paths broken in 1.3.3 Message-ID: <20090512155132.A8A1D18580F5@rubyforge.org> Bugs item #25882, was opened at 2009-05-12 05:01 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 Category: `gem install` command Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Lars Christensen (larsch) Assigned to: Nobody (None) Summary: Handling of Windows paths broken in 1.3.3 Initial Comment: Installing gems from local drives other than the current is broken on Windows. RubyGems strips the drive letter (through using the URI class for something which isn't an URI). C:\> gem install p:\path\to\mygem-2.1.18.gem ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - /path/to/mygem-2.1.18.gem Then I tried to pass a valid URI: C:\> gem install file:///p:/path/to/mygem-2.1.18.gem But that doesn't work either; ERROR: could not find gem file:///p:/path/to/mygem-2.1.18.gem locally or in a repository I believe this is because URI#path returns "/p:/path/to/mygem..." (with leading slash), which is not a valid path on Windows. Finally, I attempted to hack RubyGems to prefix file:/// itself, but I don't understand the reason for this line of code in remote_fetcher.rb: remote_gem_path = File.join(path, 'gems', gem_file_name) That causes this error instead: ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - p:/path/to/gems/mygem-2.1.18.gem Notice the extra /gems/ path. ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2009-05-12 08:51 Message: I think this patch does what we want: --- remote_fetcher.orig Sun Apr 12 13:52:46 2009 +++ remote_fetcher.rb Tue May 12 09:35:30 2009 @@ -139,7 +139,11 @@ Gem.configuration.really_verbose when nil then # TODO test for local overriding cache begin - FileUtils.cp URI.unescape(source_uri.path), local_gem_path + if Gem.win_platform? + FileUtils.cp URI.unescape(source_uri.scheme + ':' + source_uri.path), local_gem_path + else + FileUtils.cp URI.unescape(source_uri.path), local_gem_path + end rescue Errno::EACCES local_gem_path = source_uri.to_s end ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 06:46 Message: Looks like a bug in line 142 of remote_fetcher.rb related to the URI class and the fact that we're stripping the scheme off of Windows paths. It works for "C:" because, iirc, certain Ruby core File methods assume "C:" if no drive is found. We'll have to fix this. Regards, Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 06:22 Message: Well, this is odd. I tried installing from an explicit path using "C:\Documents and Settings\djberge". That worked fine. But, when I tried to install from a drive other than "C:", things went bad: C:\Documents and Settings\djberge>gem install "z:\djberge on my mac\documents\workspace\ptools\ptools-1.1.7.gem" --verbose --debug Exception `NameError' at C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:161 - uninitialized constant Gem::Commands::InstallCommand Exception `IOError' at C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/format.rb:50 - closed stream Installing gem ptools-1.1.7 Exception `Errno::ENOENT' at C:/Ruby/lib/ruby/1.8/fileutils.rb:1200 - No such file or directory - /djberge on my mac/documents/workspace/ptools/ptools-1.1.7.gem ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - /djberge on my mac/documents/workspace/ptools/ptools-1.1.7.gem C:/Ruby/lib/ruby/1.8/fileutils.rb:1200:in `stat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1200:in `lstat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1178:in `stat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1260:in `copy_file' C:/Ruby/lib/ruby/1.8/fileutils.rb:463:in `copy_file' C:/Ruby/lib/ruby/1.8/fileutils.rb:383:in `cp' C:/Ruby/lib/ruby/1.8/fileutils.rb:1395:in `fu_each_src_dest' C:/Ruby/lib/ruby/1.8/fileutils.rb:1411:in `fu_each_src_dest0' C:/Ruby/lib/ruby/1.8/fileutils.rb:1393:in `fu_each_src_dest' C:/Ruby/lib/ruby/1.8/fileutils.rb:382:in `cp' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/remote_fetcher.rb:142:in `download' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:232:in `install' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:222:in `each' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:222:in `install' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:78:in `execute' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:75:in `each' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:75:in `execute' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run' C:/Ruby/bin/gem:21 I'll have to investigate further to determine if this is a bug in rubygems or fileutils. Regards, Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 05:20 Message: The use of file urls is meant for use with the --source flag (i.e. from a local repository), which is why the method includes the 'gems' directory. However, the "gem install p:\path\to\mygem-2.1.18.gem" should work. I'll take a look. Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 From noreply at rubyforge.org Tue May 12 11:59:28 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 12 May 2009 11:59:28 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25882 ] Handling of Windows paths broken in 1.3.3 Message-ID: <20090512155928.C0FBD18580F6@rubyforge.org> Bugs item #25882, was opened at 2009-05-12 05:01 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 Category: `gem install` command Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Lars Christensen (larsch) Assigned to: Nobody (None) Summary: Handling of Windows paths broken in 1.3.3 Initial Comment: Installing gems from local drives other than the current is broken on Windows. RubyGems strips the drive letter (through using the URI class for something which isn't an URI). C:\> gem install p:\path\to\mygem-2.1.18.gem ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - /path/to/mygem-2.1.18.gem Then I tried to pass a valid URI: C:\> gem install file:///p:/path/to/mygem-2.1.18.gem But that doesn't work either; ERROR: could not find gem file:///p:/path/to/mygem-2.1.18.gem locally or in a repository I believe this is because URI#path returns "/p:/path/to/mygem..." (with leading slash), which is not a valid path on Windows. Finally, I attempted to hack RubyGems to prefix file:/// itself, but I don't understand the reason for this line of code in remote_fetcher.rb: remote_gem_path = File.join(path, 'gems', gem_file_name) That causes this error instead: ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - p:/path/to/gems/mygem-2.1.18.gem Notice the extra /gems/ path. ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2009-05-12 08:59 Message: Oops, let's update that to "if Gem.win_platform && source_uri.scheme" Regards, Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 08:51 Message: I think this patch does what we want: --- remote_fetcher.orig Sun Apr 12 13:52:46 2009 +++ remote_fetcher.rb Tue May 12 09:35:30 2009 @@ -139,7 +139,11 @@ Gem.configuration.really_verbose when nil then # TODO test for local overriding cache begin - FileUtils.cp URI.unescape(source_uri.path), local_gem_path + if Gem.win_platform? + FileUtils.cp URI.unescape(source_uri.scheme + ':' + source_uri.path), local_gem_path + else + FileUtils.cp URI.unescape(source_uri.path), local_gem_path + end rescue Errno::EACCES local_gem_path = source_uri.to_s end ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 06:46 Message: Looks like a bug in line 142 of remote_fetcher.rb related to the URI class and the fact that we're stripping the scheme off of Windows paths. It works for "C:" because, iirc, certain Ruby core File methods assume "C:" if no drive is found. We'll have to fix this. Regards, Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 06:22 Message: Well, this is odd. I tried installing from an explicit path using "C:\Documents and Settings\djberge". That worked fine. But, when I tried to install from a drive other than "C:", things went bad: C:\Documents and Settings\djberge>gem install "z:\djberge on my mac\documents\workspace\ptools\ptools-1.1.7.gem" --verbose --debug Exception `NameError' at C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:161 - uninitialized constant Gem::Commands::InstallCommand Exception `IOError' at C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/format.rb:50 - closed stream Installing gem ptools-1.1.7 Exception `Errno::ENOENT' at C:/Ruby/lib/ruby/1.8/fileutils.rb:1200 - No such file or directory - /djberge on my mac/documents/workspace/ptools/ptools-1.1.7.gem ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - /djberge on my mac/documents/workspace/ptools/ptools-1.1.7.gem C:/Ruby/lib/ruby/1.8/fileutils.rb:1200:in `stat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1200:in `lstat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1178:in `stat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1260:in `copy_file' C:/Ruby/lib/ruby/1.8/fileutils.rb:463:in `copy_file' C:/Ruby/lib/ruby/1.8/fileutils.rb:383:in `cp' C:/Ruby/lib/ruby/1.8/fileutils.rb:1395:in `fu_each_src_dest' C:/Ruby/lib/ruby/1.8/fileutils.rb:1411:in `fu_each_src_dest0' C:/Ruby/lib/ruby/1.8/fileutils.rb:1393:in `fu_each_src_dest' C:/Ruby/lib/ruby/1.8/fileutils.rb:382:in `cp' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/remote_fetcher.rb:142:in `download' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:232:in `install' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:222:in `each' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:222:in `install' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:78:in `execute' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:75:in `each' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:75:in `execute' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run' C:/Ruby/bin/gem:21 I'll have to investigate further to determine if this is a bug in rubygems or fileutils. Regards, Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 05:20 Message: The use of file urls is meant for use with the --source flag (i.e. from a local repository), which is why the method includes the 'gems' directory. However, the "gem install p:\path\to\mygem-2.1.18.gem" should work. I'll take a look. Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 From noreply at rubyforge.org Tue May 12 13:55:01 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 12 May 2009 13:55:01 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25882 ] Handling of Windows paths broken in 1.3.3 Message-ID: <20090512175501.48A42159802C@rubyforge.org> Bugs item #25882, was opened at 2009-05-12 05:01 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 Category: `gem install` command Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Lars Christensen (larsch) >Assigned to: Daniel Berger (djberg96) Summary: Handling of Windows paths broken in 1.3.3 Initial Comment: Installing gems from local drives other than the current is broken on Windows. RubyGems strips the drive letter (through using the URI class for something which isn't an URI). C:\> gem install p:\path\to\mygem-2.1.18.gem ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - /path/to/mygem-2.1.18.gem Then I tried to pass a valid URI: C:\> gem install file:///p:/path/to/mygem-2.1.18.gem But that doesn't work either; ERROR: could not find gem file:///p:/path/to/mygem-2.1.18.gem locally or in a repository I believe this is because URI#path returns "/p:/path/to/mygem..." (with leading slash), which is not a valid path on Windows. Finally, I attempted to hack RubyGems to prefix file:/// itself, but I don't understand the reason for this line of code in remote_fetcher.rb: remote_gem_path = File.join(path, 'gems', gem_file_name) That causes this error instead: ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - p:/path/to/gems/mygem-2.1.18.gem Notice the extra /gems/ path. ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2009-05-12 10:55 Message: Fixed in SVN. Thanks for the report. Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 08:59 Message: Oops, let's update that to "if Gem.win_platform && source_uri.scheme" Regards, Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 08:51 Message: I think this patch does what we want: --- remote_fetcher.orig Sun Apr 12 13:52:46 2009 +++ remote_fetcher.rb Tue May 12 09:35:30 2009 @@ -139,7 +139,11 @@ Gem.configuration.really_verbose when nil then # TODO test for local overriding cache begin - FileUtils.cp URI.unescape(source_uri.path), local_gem_path + if Gem.win_platform? + FileUtils.cp URI.unescape(source_uri.scheme + ':' + source_uri.path), local_gem_path + else + FileUtils.cp URI.unescape(source_uri.path), local_gem_path + end rescue Errno::EACCES local_gem_path = source_uri.to_s end ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 06:46 Message: Looks like a bug in line 142 of remote_fetcher.rb related to the URI class and the fact that we're stripping the scheme off of Windows paths. It works for "C:" because, iirc, certain Ruby core File methods assume "C:" if no drive is found. We'll have to fix this. Regards, Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 06:22 Message: Well, this is odd. I tried installing from an explicit path using "C:\Documents and Settings\djberge". That worked fine. But, when I tried to install from a drive other than "C:", things went bad: C:\Documents and Settings\djberge>gem install "z:\djberge on my mac\documents\workspace\ptools\ptools-1.1.7.gem" --verbose --debug Exception `NameError' at C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:161 - uninitialized constant Gem::Commands::InstallCommand Exception `IOError' at C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/format.rb:50 - closed stream Installing gem ptools-1.1.7 Exception `Errno::ENOENT' at C:/Ruby/lib/ruby/1.8/fileutils.rb:1200 - No such file or directory - /djberge on my mac/documents/workspace/ptools/ptools-1.1.7.gem ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - /djberge on my mac/documents/workspace/ptools/ptools-1.1.7.gem C:/Ruby/lib/ruby/1.8/fileutils.rb:1200:in `stat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1200:in `lstat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1178:in `stat' C:/Ruby/lib/ruby/1.8/fileutils.rb:1260:in `copy_file' C:/Ruby/lib/ruby/1.8/fileutils.rb:463:in `copy_file' C:/Ruby/lib/ruby/1.8/fileutils.rb:383:in `cp' C:/Ruby/lib/ruby/1.8/fileutils.rb:1395:in `fu_each_src_dest' C:/Ruby/lib/ruby/1.8/fileutils.rb:1411:in `fu_each_src_dest0' C:/Ruby/lib/ruby/1.8/fileutils.rb:1393:in `fu_each_src_dest' C:/Ruby/lib/ruby/1.8/fileutils.rb:382:in `cp' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/remote_fetcher.rb:142:in `download' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:232:in `install' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:222:in `each' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:222:in `install' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:78:in `execute' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:75:in `each' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:75:in `execute' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command.rb:254:in `invoke' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run' C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run' C:/Ruby/bin/gem:21 I'll have to investigate further to determine if this is a bug in rubygems or fileutils. Regards, Dan ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-05-12 05:20 Message: The use of file urls is meant for use with the --source flag (i.e. from a local repository), which is why the method includes the 'gems' directory. However, the "gem install p:\path\to\mygem-2.1.18.gem" should work. I'll take a look. Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25882&group_id=126 From noreply at rubyforge.org Fri May 15 21:58:34 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 15 May 2009 21:58:34 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Feature Requests-25925 ] Default rubyforge_project if homepage is rubyforge Message-ID: <20090516015834.354B11858111@rubyforge.org> Feature Requests item #25925, was opened at 2009-05-15 18:58 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=25925&group_id=126 Category: other Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Daniel Berger (djberg96) Assigned to: Daniel Berger (djberg96) Summary: Default rubyforge_project if homepage is rubyforge Initial Comment: Hi, If a user sets the project homepage to a URL that contains "rubyforge.org" and the rubyforge_project is not set, then automatically set the rubyforge_project to the basename of the URL instead of issuing a warning. Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=25925&group_id=126 From noreply at rubyforge.org Sat May 16 09:40:42 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 16 May 2009 09:40:42 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25935 ] module installed by gem does not load when installation directory path contains space Message-ID: <20090516134042.992BB1858113@rubyforge.org> Bugs item #25935, was opened at 2009-05-16 22:40 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25935&group_id=126 Category: RubyGems installer (setup.rb) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: bazz bazz (bazz) Assigned to: Nobody (None) Summary: module installed by gem does not load when installation directory path contains space Initial Comment: * The following is example. I install RoR through gem. "rails" command does not work. --- C:\>rails C:/Program Files/ruby-1.8/bin/rails:19:in `load': no such file to load -- "C:/Pr ogram Files/ruby-1.8/lib/ruby/gems/1.8/gems/rails-2.3.2/bin/rails" (LoadError) from C:/Program Files/ruby-1.8/bin/rails:19 --- * The investigation line #386 in "rubygems.rb" File.join(spec.full_gem_path, spec.bindir, exec_name).sub(/.*\s.*/m, '"\&"') #=> Gem.bin_path returns "\C:/Program Files/ruby-1.8/lib/ruby/gems/1.8/gems/rails-2.3.2/bin/rails\" line #19 in "rails" this file is installed by gem load Gem.bin_path('rails', 'rails', version) #=> Load error * Workaround line #386 in "rubygems.rb" -File.join(spec.full_gem_path, spec.bindir, exec_name).sub(/.*\s.*/m, '"\&"') +File.join(spec.full_gem_path, spec.bindir, exec_name) This way was confirmed only my environment. * The following is my environment. --- RubyGems Environment: - RUBYGEMS VERSION: 1.3.3 - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [i386-mswin32] - INSTALLATION DIRECTORY: C:/Program Files/ruby-1.8/lib/ruby/gems/1.8 - RUBY EXECUTABLE: "C:/Program Files/ruby-1.8/bin/ruby.exe" - EXECUTABLE DIRECTORY: C:/Program Files/ruby-1.8/bin - RUBYGEMS PLATFORMS: - ruby - x86-mswin32-60 - GEM PATHS: - C:/Program Files/ruby-1.8/lib/ruby/gems/1.8 - C:/Documents and Settings/Administrator/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://gems.rubyforge.org/ --- ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25935&group_id=126 From drbrain at segment7.net Wed May 20 20:47:26 2009 From: drbrain at segment7.net (Eric Hodel) Date: Wed, 20 May 2009 17:47:26 -0700 Subject: [Rubygems-developers] RubyGems 1.3.4 Soon Message-ID: Can I get some people to run the tests on various versions of Ruby (1.8.6+) and otherwise play with it? I fixed up some warnings from ruby trunk (1.9.2dev) which involved removing a bunch of requires. From thewoolleyman at gmail.com Wed May 20 20:52:19 2009 From: thewoolleyman at gmail.com (Chad Woolley) Date: Wed, 20 May 2009 17:52:19 -0700 Subject: [Rubygems-developers] RubyGems 1.3.4 Soon In-Reply-To: References: Message-ID: On Wed, May 20, 2009 at 5:47 PM, Eric Hodel wrote: > Can I get some people to run the tests on various versions of Ruby (1.8.6+) > and otherwise play with it? > > I fixed up some warnings from ruby trunk (1.9.2dev) which involved removing > a bunch of requires. I can give it try in all the MRIs, I've been playing with automated setup of multiple ruby environments: http://github.com/thewoolleyman/cinabox/blob/master/bootstrap_ruby.sh From luislavena at gmail.com Thu May 21 07:44:33 2009 From: luislavena at gmail.com (Luis Lavena) Date: Thu, 21 May 2009 08:44:33 -0300 Subject: [Rubygems-developers] RubyGems 1.3.4 Soon In-Reply-To: References: Message-ID: <71166b3b0905210444vbda612eq71725faae34fb38f@mail.gmail.com> On Wed, May 20, 2009 at 9:47 PM, Eric Hodel wrote: > Can I get some people to run the tests on various versions of Ruby (1.8.6+) > and otherwise play with it? > http://pastie.org/pastes/48522 > I fixed up some warnings from ruby trunk (1.9.2dev) which involved removing > a bunch of requires. I'm going to get 1.9.2dev build on MinGW and get back to you. BTW: I'm no longer testing against VC6 builds of Ruby, so if anyone with VC6 and Ruby mswin32 platform code out there can do it, will be much appreciated. -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry From thewoolleyman at gmail.com Thu May 21 12:01:51 2009 From: thewoolleyman at gmail.com (Chad Woolley) Date: Thu, 21 May 2009 09:01:51 -0700 Subject: [Rubygems-developers] RubyGems 1.3.4 Soon In-Reply-To: References: Message-ID: On Wed, May 20, 2009 at 5:52 PM, Chad Woolley wrote: >> I fixed up some warnings from ruby trunk (1.9.2dev) which involved removing >> a bunch of requires. > > I can give it try in all the MRIs, I've been playing with automated > setup of multiple ruby environments: > http://github.com/thewoolleyman/cinabox/blob/master/bootstrap_ruby.sh I'm seeing some test failures, but I'm not sure if they are real, or due to the way the interpreter/rake suffixes and versions are behaving under multiple interpreters. If you want, I can give you access to the test box with the versions installed and let you look. If I've set something up incorrectly I'd like to know. -- Chad From technomancy at gmail.com Thu May 21 12:16:02 2009 From: technomancy at gmail.com (Phil Hagelberg) Date: Thu, 21 May 2009 09:16:02 -0700 Subject: [Rubygems-developers] RubyGems 1.3.4 Soon In-Reply-To: (Eric Hodel's message of "Wed, 20 May 2009 17:47:26 -0700") References: Message-ID: <87my96xwhp.fsf@hagelb.org> Eric Hodel writes: > Can I get some people to run the tests on various versions of Ruby > (1.8.6+) and otherwise play with it? > > I fixed up some warnings from ruby trunk (1.9.2dev) which involved > removing a bunch of requires. Any chance we could remove the auto-fallback to ~/.gem for this version, or did you want to wait till 1.4.0 for that? -Phil From noreply at rubyforge.org Thu May 21 14:02:01 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 21 May 2009 14:02:01 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Patches-25982 ] gem rdoc --no-overwrite Message-ID: <20090521180202.05A461858109@rubyforge.org> Patches item #25982, was opened at 2009-05-22 03:02 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=25982&group_id=126 Category: `gem` commands (other) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Akinori MUSHA (knu) Assigned to: Nobody (None) Summary: gem rdoc --no-overwrite Initial Comment: What about adding a --[no-]overwrite option to gem rdoc? It is very useful when you want to generate documents of gems installed with --no-rdoc/--no-ri set. $ gem install --all --no-overwrite The option is defaulted to true in the attached patch to keep the current behavior as default, but you may want to default it to false. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=25982&group_id=126 From noreply at rubyforge.org Fri May 22 04:34:15 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 22 May 2009 04:34:15 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-25998 ] Had > instead of ~> in docs for specifying a pessimist Message-ID: <20090522083416.16EB618580F0@rubyforge.org> Bugs item #25998, was opened at 2009-05-22 18:34 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25998&group_id=126 Category: documentation Group: None Status: Open Resolution: None Priority: 3 Submitted By: David Miani (nanothief) Assigned to: Nobody (None) Summary: Had > instead of ~> in docs for specifying a pessimist Initial Comment: While reading chapter 5 of the user guide (http://rubygems.org/read/chapter/16), in the section about PessimisticVersionContraints, I came across this: ----- ...Doing this is cumbersome, so RubyGems provides a pessimistic operator ~~> (read: approximately greater than). Using the pessimistic operator, we get: gem 'library', '> 2.2' ----- The pessimistic operators is first said to be '~~>', but the example uses '>'. From trying these examples in irb, I think both are wrong, and the correct operator is '~>'. So I think the section should read: ----- ...Doing this is cumbersome, so RubyGems provides a pessimistic operator ~> (read: approximately greater than). Using the pessimistic operator, we get: gem 'library', '~> 2.2' ----- Also there is a minor formatting problem, the text "(read: approximately greater than). Using the pessimistic operator, we get:" uses the coding style instead of the normal style. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25998&group_id=126 From drbrain at segment7.net Fri May 22 17:55:02 2009 From: drbrain at segment7.net (Eric Hodel) Date: Fri, 22 May 2009 14:55:02 -0700 Subject: [Rubygems-developers] RubyGems 1.3.4 Soon In-Reply-To: <71166b3b0905210444vbda612eq71725faae34fb38f@mail.gmail.com> References: <71166b3b0905210444vbda612eq71725faae34fb38f@mail.gmail.com> Message-ID: <8C876626-6ABA-456E-8762-1C7D0565EADC@segment7.net> On May 21, 2009, at 04:44, Luis Lavena wrote: > On Wed, May 20, 2009 at 9:47 PM, Eric Hodel > wrote: >> Can I get some people to run the tests on various versions of Ruby >> (1.8.6+) >> and otherwise play with it? > > http://pastie.org/pastes/48522 I think your paste failed, as this link shows nothing. From drbrain at segment7.net Fri May 22 17:55:27 2009 From: drbrain at segment7.net (Eric Hodel) Date: Fri, 22 May 2009 14:55:27 -0700 Subject: [Rubygems-developers] RubyGems 1.3.4 Soon In-Reply-To: <87my96xwhp.fsf@hagelb.org> References: <87my96xwhp.fsf@hagelb.org> Message-ID: <7AA95502-AB12-4BE6-8B1B-669C3B6CFD48@segment7.net> On May 21, 2009, at 09:16, Phil Hagelberg wrote: > Eric Hodel writes: >> Can I get some people to run the tests on various versions of Ruby >> (1.8.6+) and otherwise play with it? >> >> I fixed up some warnings from ruby trunk (1.9.2dev) which involved >> removing a bunch of requires. > > Any chance we could remove the auto-fallback to ~/.gem for this > version, > or did you want to wait till 1.4.0 for that? 1.4. From luislavena at gmail.com Fri May 22 18:03:48 2009 From: luislavena at gmail.com (Luis Lavena) Date: Fri, 22 May 2009 19:03:48 -0300 Subject: [Rubygems-developers] RubyGems 1.3.4 Soon In-Reply-To: <8C876626-6ABA-456E-8762-1C7D0565EADC@segment7.net> References: <71166b3b0905210444vbda612eq71725faae34fb38f@mail.gmail.com> <8C876626-6ABA-456E-8762-1C7D0565EADC@segment7.net> Message-ID: <71166b3b0905221503k406231b8pb6b4903c0675417c@mail.gmail.com> On Fri, May 22, 2009 at 6:55 PM, Eric Hodel wrote: > On May 21, 2009, at 04:44, Luis Lavena wrote: >> >> On Wed, May 20, 2009 at 9:47 PM, Eric Hodel wrote: >>> >>> Can I get some people to run the tests on various versions of Ruby >>> (1.8.6+) >>> and otherwise play with it? >> >> http://pastie.org/pastes/48522 > > I think your paste failed, as this link shows nothing. Oh well, the pastie showed no test failed on Windows MinGW builds of 1.8.6-p368 or 1.9.1-p0 :D Will run the same for 1.9.1-p129, but I guess will be the same. Cheers, -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exup?ry From noreply at rubyforge.org Sat May 23 11:44:21 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 23 May 2009 11:44:21 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-26000 ] Type in requirements documentation Message-ID: <20090523154421.9E1881D787E9@rubyforge.org> Bugs item #26000, was opened at 2009-05-23 10:44 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26000&group_id=126 Category: documentation Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Mike Gunderloy (mikeg1) Assigned to: Nobody (None) Summary: Type in requirements documentation Initial Comment: RDoc for 1.3.3 for Gem::Requirement#parse says "The requirement can be a String or a Gem::Version. A String can be an operator (<, <=, =, =>, >, !=, ~>), a version number, or both, operator first." That should actually read "The requirement can be a String or a Gem::Version. A String can be an operator (<, <=, =, >=, >, !=, ~>), a version number, or both, operator first." Note transposition of characters - we love hashrockets in Ruby, but not as comparison operators. I could submit a patch for this, but that seems more trouble than it's worth. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26000&group_id=126 From vladimir at geekq.net Mon May 25 07:23:19 2009 From: vladimir at geekq.net (Vladimir Dobriakov) Date: Mon, 25 May 2009 13:23:19 +0200 Subject: [Rubygems-developers] Working on a fork of a ruby gem - installing gems in a special way Message-ID: <2dcedd820905250423p1a0c1967s31ca6a20959ac524@mail.gmail.com> Hi Eric, hi all, I have a question not about developing, but about using rubygems. Sorry if it is kind of offtopic. But this question can be only answered by real rubygems gurus. USECASE: working on an own fork of a ruby gem Imagine, you are using a particular gem within your application and found some bug or missing feature and wish to improve the gem. The source code of a gem is hosted at github. So it is easy to clone the source code. What next? I've tried following approaches. All of them are either cumbersome or error prone or both: ## Repeatedly reinstall 1. uninstall the current gem version `sudo gem uninstall foo` 2. switch to my version `cd myversion_of_foo` 3. edit the source code (apply the changes) 4. create a gem from my sources `rake gem` 5. install my version of the gem `sudo gem install pkg/foo-1.0.0.gem` 6. try out in connection with my (bigger) project 7. repeat all the steps for each change OK, one should work on a feature in a test-driven way and in isolation, which should reduce the amount of install/uninstall iterations, but still ... ## symbolic links 1. install the gem 2. goto to the system wide folder for installed gems `cd /usr/lib/ruby/gems/1.8/gems/foo-1.0.0` 3. remove or backup the lib folder `rm -rf lib` 4. create a symbolic link to your implementation's lib folder Editing the source code of the gem will have an immediate effect on the using application. ## load path explicitly change the load path in the client application `$:.unshift 'myversion_of_foo/lib'` or put a require statement with explicit full path. Now imagine there is a chain of libraries with dependencies ClientApp -> A -> B -> C -> D and you are going to improve the library B. Changing require statements leads to a real mess. # Perfect solution Is there a better/perfect way? How the tools of rubygems support this or could support this in the future? Thanks and Best Regards, Vladimir Dobriakov AKA geekQ From ryand-ruby at zenspider.com Wed May 27 02:42:21 2009 From: ryand-ruby at zenspider.com (Ryan Davis) Date: Tue, 26 May 2009 23:42:21 -0700 Subject: [Rubygems-developers] Working on a fork of a ruby gem - installing gems in a special way In-Reply-To: <2dcedd820905250423p1a0c1967s31ca6a20959ac524@mail.gmail.com> References: <2dcedd820905250423p1a0c1967s31ca6a20959ac524@mail.gmail.com> Message-ID: On May 25, 2009, at 04:23 , Vladimir Dobriakov wrote: > I've tried following approaches. All of them are either cumbersome or > error prone or both: > > ## Repeatedly reinstall > > 1. uninstall the current gem version `sudo gem uninstall foo` > 2. switch to my version `cd myversion_of_foo` > 3. edit the source code (apply the changes) > 4. create a gem from my sources `rake gem` > 5. install my version of the gem `sudo gem install pkg/foo-1.0.0.gem` > 6. try out in connection with my (bigger) project > 7. repeat all the steps for each change > > OK, one should work on a feature in a test-driven way and in > isolation, which should reduce the amount of install/uninstall > iterations, but still ... I start with modifying $: on the dependent side to do the quickest back and forth. Once I have that flushed out, I update the version number on the dependency and `rake install_gem` (assuming it is a hoe empowered gem) and clean up any hacks I've put in on the dependent side. When I'm working with student's code and I don't want to install a dependency, I'll frequently `gem fetch; gem unpack` it and then `mv gem-1.0.0/lib/* lib`. Totally cheating, I know, but it works fine for throwaway stuff. From noreply at rubyforge.org Wed May 27 14:13:29 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 27 May 2009 14:13:29 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-26046 ] doesn't allow to differentiate between 1.8 and 1.9 binaries Message-ID: <20090527181329.C19AE18580FA@rubyforge.org> Bugs item #26046, was opened at 2009-05-27 18:13 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26046&group_id=126 Category: #gem and #require methods Group: None Status: Open Resolution: None Priority: 3 Submitted By: Roger Pack (rogerdpack) Assigned to: Nobody (None) Summary: doesn't allow to differentiate between 1.8 and 1.9 binaries Initial Comment: currently it appears that currently we "can't build one gem targeting 1.8 and one gem targeting 1.9, and have rubygems differentiate the two" http://tenderlovemaking.com/2009/05/07/fat-binary-gems-make-the-rockin-world-go-round/ Thanks! -=r ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26046&group_id=126 From noreply at rubyforge.org Wed May 27 14:20:25 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 27 May 2009 14:20:25 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-26046 ] doesn't allow to differentiate between 1.8 and 1.9 binaries Message-ID: <20090527182025.233281858102@rubyforge.org> Bugs item #26046, was opened at 2009-05-27 15:13 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26046&group_id=126 Category: #gem and #require methods Group: None Status: Open Resolution: None Priority: 3 Submitted By: Roger Pack (rogerdpack) Assigned to: Nobody (None) Summary: doesn't allow to differentiate between 1.8 and 1.9 binaries Initial Comment: currently it appears that currently we "can't build one gem targeting 1.8 and one gem targeting 1.9, and have rubygems differentiate the two" http://tenderlovemaking.com/2009/05/07/fat-binary-gems-make-the-rockin-world-go-round/ Thanks! -=r ---------------------------------------------------------------------- >Comment By: Luis Lavena (luislavena) Date: 2009-05-27 15:20 Message: This has been discussed here: http://rubyforge.org/pipermail/rubygems-developers/2009-April/004522.html One suggestion is make smarter servers, but there is a RubyForge and RubyGems limitation, not only RubyGems. HTH, -- Luis Lavena ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26046&group_id=126 From noreply at rubyforge.org Wed May 27 14:22:12 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 27 May 2009 14:22:12 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-26046 ] doesn't allow to differentiate between 1.8 and 1.9 binaries Message-ID: <20090527182212.D268918580FA@rubyforge.org> Bugs item #26046, was opened at 2009-05-27 18:13 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26046&group_id=126 Category: #gem and #require methods Group: None Status: Open Resolution: None Priority: 3 Submitted By: Roger Pack (rogerdpack) Assigned to: Nobody (None) Summary: doesn't allow to differentiate between 1.8 and 1.9 binaries Initial Comment: currently it appears that currently we "can't build one gem targeting 1.8 and one gem targeting 1.9, and have rubygems differentiate the two" http://tenderlovemaking.com/2009/05/07/fat-binary-gems-make-the-rockin-world-go-round/ Thanks! -=r ---------------------------------------------------------------------- >Comment By: Roger Pack (rogerdpack) Date: 2009-05-27 18:22 Message: glad to know works been done toward it. -=r ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-05-27 18:20 Message: This has been discussed here: http://rubyforge.org/pipermail/rubygems-developers/2009-April/004522.html One suggestion is make smarter servers, but there is a RubyForge and RubyGems limitation, not only RubyGems. HTH, -- Luis Lavena ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26046&group_id=126 From drbrain at segment7.net Wed May 27 16:21:01 2009 From: drbrain at segment7.net (Eric Hodel) Date: Wed, 27 May 2009 13:21:01 -0700 Subject: [Rubygems-developers] Working on a fork of a ruby gem - installing gems in a special way In-Reply-To: <2dcedd820905250423p1a0c1967s31ca6a20959ac524@mail.gmail.com> References: <2dcedd820905250423p1a0c1967s31ca6a20959ac524@mail.gmail.com> Message-ID: <0E208F03-F221-4401-A8D5-3C19103D53EE@segment7.net> On May 25, 2009, at 04:23, Vladimir Dobriakov wrote: > ## load path > > explicitly change the load path in the client application > `$:.unshift 'myversion_of_foo/lib'` or put a require statement with > explicit full path. > > Now imagine there is a chain of libraries with dependencies > ClientApp -> A -> B -> C -> D and you are going to improve the > library B. Changing require statements leads to a real mess. I usually use ruby -I for this, rather than editing files. It seems to work alright. From noreply at rubyforge.org Wed May 27 17:20:27 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 27 May 2009 17:20:27 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-26046 ] doesn't allow to differentiate between 1.8 and 1.9 binaries Message-ID: <20090527212027.398C61678111@rubyforge.org> Bugs item #26046, was opened at 2009-05-27 11:13 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26046&group_id=126 Category: #gem and #require methods >Group: v1.3.x >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: Roger Pack (rogerdpack) >Assigned to: Eric Hodel (drbrain) Summary: doesn't allow to differentiate between 1.8 and 1.9 binaries Initial Comment: currently it appears that currently we "can't build one gem targeting 1.8 and one gem targeting 1.9, and have rubygems differentiate the two" http://tenderlovemaking.com/2009/05/07/fat-binary-gems-make-the-rockin-world-go-round/ Thanks! -=r ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2009-05-27 14:20 Message: The URL you've given provides an easy solution to this bug that doesn't involve any changes to RubyGems. I don't see any reason to make any changes to RubyGems to support separate 1.8 and 1.9 gems. ---------------------------------------------------------------------- Comment By: Roger Pack (rogerdpack) Date: 2009-05-27 11:22 Message: glad to know works been done toward it. -=r ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-05-27 11:20 Message: This has been discussed here: http://rubyforge.org/pipermail/rubygems-developers/2009-April/004522.html One suggestion is make smarter servers, but there is a RubyForge and RubyGems limitation, not only RubyGems. HTH, -- Luis Lavena ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26046&group_id=126 From noreply at rubyforge.org Wed May 27 18:19:46 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 27 May 2009 18:19:46 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-26046 ] doesn't allow to differentiate between 1.8 and 1.9 binaries Message-ID: <20090527221946.38A0B1678111@rubyforge.org> Bugs item #26046, was opened at 2009-05-27 15:13 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26046&group_id=126 Category: #gem and #require methods Group: v1.3.x Status: Closed Resolution: Rejected Priority: 3 Submitted By: Roger Pack (rogerdpack) Assigned to: Eric Hodel (drbrain) Summary: doesn't allow to differentiate between 1.8 and 1.9 binaries Initial Comment: currently it appears that currently we "can't build one gem targeting 1.8 and one gem targeting 1.9, and have rubygems differentiate the two" http://tenderlovemaking.com/2009/05/07/fat-binary-gems-make-the-rockin-world-go-round/ Thanks! -=r ---------------------------------------------------------------------- >Comment By: Luis Lavena (luislavena) Date: 2009-05-27 19:19 Message: Hi Eric, While modifications to RubyGems implementation are things to talk with precaution, this clearly exposes a limitation to RubyGems itself. Again, this renders required_ruby_version kind of useless, since you are targeting 2 ruby versions with the same gem. Anyhow, working on making rake-compiler more smart on how to deal with multiple versions (which partial work is already on GitHub). ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-05-27 18:20 Message: The URL you've given provides an easy solution to this bug that doesn't involve any changes to RubyGems. I don't see any reason to make any changes to RubyGems to support separate 1.8 and 1.9 gems. ---------------------------------------------------------------------- Comment By: Roger Pack (rogerdpack) Date: 2009-05-27 15:22 Message: glad to know works been done toward it. -=r ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-05-27 15:20 Message: This has been discussed here: http://rubyforge.org/pipermail/rubygems-developers/2009-April/004522.html One suggestion is make smarter servers, but there is a RubyForge and RubyGems limitation, not only RubyGems. HTH, -- Luis Lavena ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26046&group_id=126 From noreply at rubyforge.org Wed May 27 19:20:59 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 27 May 2009 19:20:59 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-26050 ] gem links native extensions against wrong version of ruby Message-ID: <20090527232059.1F9261858124@rubyforge.org> Bugs item #26050, was opened at 2009-05-27 16:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26050&group_id=126 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Aaron Turner (synfinatic) Assigned to: Nobody (None) Summary: gem links native extensions against wrong version of ruby Initial Comment: I have ruby 1.8 (/usr/bin/ruby) and 1.9.1 (/usr/bin/ruby1.9) installed. I downloaded rubygems 1.3.3 and ran: ruby1.9 setup.rb which correctly installed rubygems in /usr/lib/ruby/site_ruby/1.9.1 but did not honor the default --format-executable flag since it created /usr/bin/gem rather then /usr/bin/gem1.9 I then copied over /usr/bin/gem -> /usr/bin/gem1.9 and edited the shebang appropriately and tried installing hpricot: gem1.9 install hpricot which built, but was incorrectly linked against ruby 1.8: ldd /usr/lib/ruby/gems/1.9.1/gems/hpricot-0.8.1/lib/hpricot_scan.so libruby.so.1.8 => /usr/lib/libruby.so.1.8 (0x0049b000) libc.so.6 => /lib/tls/libc.so.6 (0x00ca1000) libdl.so.2 => /lib/libdl.so.2 (0x008d5000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x00b6f000) libm.so.6 => /lib/tls/libm.so.6 (0x0032f000) /lib/ld-linux.so.2 (0x46843000) This results in hpricot segfaulting immediately upon require. Extras: output of gem1.9 install -V hpricot: http://pastie.org/492109 hpricot Makefile: http://pastie.org/492106 Note: I (synfinatic) was working with drbrain on #ruby-lang on this issue. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26050&group_id=126 From rick.denatale at gmail.com Thu May 28 12:10:53 2009 From: rick.denatale at gmail.com (Rick DeNatale) Date: Thu, 28 May 2009 12:10:53 -0400 Subject: [Rubygems-developers] Hoe, Rubyforge, and name confusion Message-ID: I'm having trouble getting rake release to work. I posted the following to Dr Nic's forum on newgem, but since it's probably really a misunderstanding on my part of rubyforge and hoe, I thought I might get an answer here: So I'm finally ready to release my gem on rubyforge (It has been maturing on github for some weeks). When I tried to rake release, I first ran into the issue of having to specify the version as an environment variable, then I ran into the "no configured for Googling around for an answer, it seemed that I'd originally messed up in naming the ruby forge project rical when the gem name is ri_cal. So not finding a way to rename a project I created another one. But I'm still running into the same issues. I did the rubyforge config incantations but when I rake release $rake release VERSION=0.5.0 ..... lots of output cd - Successfully built RubyGem Name: ri_cal Version: 0.5.0 File: ri_cal-0.5.0.gem mv ri_cal-0.5.0.gem pkg/ri_cal-0.5.0.gem Logging in Releasing ri_cal v. 0.5.0 rake aborted! no configured for $cat ~/.rubyforge/auto-config.yml $ cat ~/.rubyforge/auto-config.yml --- processor_ids: {} release_ids: ri-cal: {} rical: {} group_ids: ri-cal: 8408 rical: 8234 type_ids: .deb: 1000 .zip: 3000 .gz: 3110 .src.rpm: 5100 .jpg: 8000 .htm: 8200 .src.bz2: 5010 .html: 8200 .oth: 9999 .pem: 1500 .src.gz: 5020 .src: 5900 .pgp: 8150 .rpm: 2000 .bz2: 3100 .text: 8100 .ebuild: 1300 .gem: 1400 .txt: 8100 .src.tar.bz2: 5010 .tgz: 5000 .sig: 8150 .pdf: 8300 .exe: 1100 .src.zip: 5000 .src.tar.gz: 5020 .dmg: 1200 .tar.gz: 5000 package_ids: ri-cal: 11330 rical: 11041 ri_cal (master)? $ So now it seems that the problem is that there's a discrepency between ri_cal, and ri-cal which is the 'unix name' of the project and which according to the rubyforge instruction can't contain an underscore but can contain a dash. So how do I straighten this mess out? -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Twitter: http://twitter.com/RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale From jbarnette at gmail.com Thu May 28 14:10:13 2009 From: jbarnette at gmail.com (John Barnette) Date: Thu, 28 May 2009 11:10:13 -0700 Subject: [Rubygems-developers] Hoe, Rubyforge, and name confusion In-Reply-To: References: Message-ID: <02ADBA94-A295-493F-9BAB-4ABB9B7B4E5D@gmail.com> Hi, On May 28, 2009, at 9:10 AM, Rick DeNatale wrote: > I'm having trouble getting rake release to work. I posted the > following to Dr Nic's forum on newgem, but since it's probably really > a misunderstanding on my part of rubyforge and hoe, I thought I might > get an answer here: [snip] > So now it seems that the problem is that there's a discrepency between > ri_cal, and ri-cal which is the 'unix name' of the project and which > according to the rubyforge instruction can't contain an underscore but > can contain a dash. > So how do I straighten this mess out? Hoe allows you to specify the rubyforge_name of a project independently. Have you tried this? ~ j. From rick.denatale at gmail.com Thu May 28 14:20:41 2009 From: rick.denatale at gmail.com (Rick DeNatale) Date: Thu, 28 May 2009 14:20:41 -0400 Subject: [Rubygems-developers] Hoe, Rubyforge, and name confusion In-Reply-To: <02ADBA94-A295-493F-9BAB-4ABB9B7B4E5D@gmail.com> References: <02ADBA94-A295-493F-9BAB-4ABB9B7B4E5D@gmail.com> Message-ID: How? I've found the 'documentation' for hoe rather ephemeral. On Thu, May 28, 2009 at 2:10 PM, John Barnette wrote: > Hi, > > On May 28, 2009, at 9:10 AM, Rick DeNatale wrote: >> >> I'm having trouble getting rake release to work. ?I posted the >> following to Dr Nic's forum on newgem, but since it's probably really >> a misunderstanding on my part of rubyforge and hoe, I thought I might >> get an answer here: > > [snip] > >> So now it seems that the problem is that there's a discrepency between >> ri_cal, and ri-cal which is the 'unix name' of the project and which >> according to the rubyforge instruction can't contain an underscore but >> can contain a dash. >> So how do I straighten this mess out? > > Hoe allows you to specify the rubyforge_name of a project independently. > Have you tried this? > > > ~ j. > > > > _______________________________________________ > Rubygems-developers mailing list > http://rubyforge.org/projects/rubygems > Rubygems-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers > -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Twitter: http://twitter.com/RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale From rick.denatale at gmail.com Thu May 28 15:52:43 2009 From: rick.denatale at gmail.com (Rick DeNatale) Date: Thu, 28 May 2009 15:52:43 -0400 Subject: [Rubygems-developers] Hoe, Rubyforge, and name confusion In-Reply-To: References: <02ADBA94-A295-493F-9BAB-4ABB9B7B4E5D@gmail.com> Message-ID: I'm getting nowhere fast. I'm still getting "invalid package_id" when I try to release. I tried rubyforge create_package <> ri_cal which added a new package number to my autoconfig.yml, but when I try to release THAT is the new number which comes up as invalid. I guess I'm going to have to manually upload the gem through the web interface AGAIN. I'd sure love to get some advice, it's not that I haven't already been pulling my hair out with google and reading the code in the hoe and rubyforge gems. On Thu, May 28, 2009 at 2:20 PM, Rick DeNatale wrote: > How? ?I've found the 'documentation' for hoe rather ephemeral. > > On Thu, May 28, 2009 at 2:10 PM, John Barnette wrote: >> Hi, >> >> On May 28, 2009, at 9:10 AM, Rick DeNatale wrote: >>> >>> I'm having trouble getting rake release to work. ?I posted the >>> following to Dr Nic's forum on newgem, but since it's probably really >>> a misunderstanding on my part of rubyforge and hoe, I thought I might >>> get an answer here: >> >> [snip] >> >>> So now it seems that the problem is that there's a discrepency between >>> ri_cal, and ri-cal which is the 'unix name' of the project and which >>> according to the rubyforge instruction can't contain an underscore but >>> can contain a dash. >>> So how do I straighten this mess out? >> >> Hoe allows you to specify the rubyforge_name of a project independently. >> Have you tried this? >> >> >> ~ j. >> >> >> >> _______________________________________________ >> Rubygems-developers mailing list >> http://rubyforge.org/projects/rubygems >> Rubygems-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/rubygems-developers >> > > > > -- > Rick DeNatale > > Blog: http://talklikeaduck.denhaven2.com/ > Twitter: http://twitter.com/RickDeNatale > WWR: http://www.workingwithrails.com/person/9021-rick-denatale > LinkedIn: http://www.linkedin.com/in/rickdenatale > -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Twitter: http://twitter.com/RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale From drbrain at segment7.net Thu May 28 16:57:04 2009 From: drbrain at segment7.net (Eric Hodel) Date: Thu, 28 May 2009 13:57:04 -0700 Subject: [Rubygems-developers] Hoe, Rubyforge, and name confusion In-Reply-To: References: <02ADBA94-A295-493F-9BAB-4ABB9B7B4E5D@gmail.com> Message-ID: On May 28, 2009, at 12:52, Rick DeNatale wrote: > I'm getting nowhere fast. > > I'm still getting "invalid package_id" when I try to release. > > I tried > > rubyforge create_package <> ri_cal > > which added a new package number to my autoconfig.yml, but when I try > to release THAT is the new number which comes up as invalid. > > I guess I'm going to have to manually upload the gem through the web > interface AGAIN. > > I'd sure love to get some advice, it's not that I haven't already been > pulling my hair out with google and reading the code in the hoe and > rubyforge gems. I've found an rical package under the rical project: http://rubyforge.org/frs/?group_id=8234 but no ri_cal project: http://rubyforge.org/projects/ri_cal (which is 404) If you want to release as the rical project, this should do it: $ rubyforge config rical $ rake release Usually rubyforge correctly adds the package_id, but sometimes it seems to forget. Check your rubyforge_project under `rake debug_gem` to make sure it matches. From jbarnette at gmail.com Thu May 28 17:23:03 2009 From: jbarnette at gmail.com (John Barnette) Date: Thu, 28 May 2009 14:23:03 -0700 Subject: [Rubygems-developers] Hoe, Rubyforge, and name confusion In-Reply-To: References: <02ADBA94-A295-493F-9BAB-4ABB9B7B4E5D@gmail.com> Message-ID: <3DB9C772-0D5D-4757-BBE4-80504CF933E0@gmail.com> On May 28, 2009, at 11:20 AM, Rick DeNatale wrote: > How? I've found the 'documentation' for hoe rather ephemeral. Have you tried the basics? "ri Hoe" was how I found rubyforge_project, and it looks like pretty complete docs to me. Is there a bad website out there somewhere we need to update? ~ j. > > On Thu, May 28, 2009 at 2:10 PM, John Barnette > wrote: >> Hi, >> >> On May 28, 2009, at 9:10 AM, Rick DeNatale wrote: >>> >>> I'm having trouble getting rake release to work. I posted the >>> following to Dr Nic's forum on newgem, but since it's probably >>> really >>> a misunderstanding on my part of rubyforge and hoe, I thought I >>> might >>> get an answer here: >> >> [snip] >> >>> So now it seems that the problem is that there's a discrepency >>> between >>> ri_cal, and ri-cal which is the 'unix name' of the project and which >>> according to the rubyforge instruction can't contain an underscore >>> but >>> can contain a dash. >>> So how do I straighten this mess out? >> >> Hoe allows you to specify the rubyforge_name of a project >> independently. >> Have you tried this? >> >> >> ~ j. >> >> >> >> _______________________________________________ >> Rubygems-developers mailing list >> http://rubyforge.org/projects/rubygems >> Rubygems-developers at rubyforge.org >> http://rubyforge.org/mailman/listinfo/rubygems-developers >> > > > > -- > Rick DeNatale > > Blog: http://talklikeaduck.denhaven2.com/ > Twitter: http://twitter.com/RickDeNatale > WWR: http://www.workingwithrails.com/person/9021-rick-denatale > LinkedIn: http://www.linkedin.com/in/rickdenatale > _______________________________________________ > Rubygems-developers mailing list > http://rubyforge.org/projects/rubygems > Rubygems-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers From rick.denatale at gmail.com Thu May 28 17:25:46 2009 From: rick.denatale at gmail.com (Rick DeNatale) Date: Thu, 28 May 2009 17:25:46 -0400 Subject: [Rubygems-developers] Hoe, Rubyforge, and name confusion In-Reply-To: References: <02ADBA94-A295-493F-9BAB-4ABB9B7B4E5D@gmail.com> Message-ID: The rical project was abandoned when I couldn't get that to work since the gem is named ri_cal. So I created the ri_cal project, and I've manually release three versions there: http://rubyforge.org/frs/?group_id=8408 That's also the one which had been published to the world, so I really want to get that project working with hoe. On Thu, May 28, 2009 at 4:57 PM, Eric Hodel wrote: > On May 28, 2009, at 12:52, Rick DeNatale wrote: > >> I'm getting nowhere fast. >> >> I'm still getting "invalid package_id" when I try to release. >> >> I tried >> >> rubyforge create_package <> ri_cal >> >> which added a new package number to my autoconfig.yml, but when I try >> to release THAT is the new number which comes up as invalid. >> >> I guess I'm going to have to manually upload the gem through the web >> interface AGAIN. >> >> I'd sure love to get some advice, it's not that I haven't already been >> pulling my hair out with google and reading the code in the hoe and >> rubyforge gems. > > I've found an rical package under the rical project: > > http://rubyforge.org/frs/?group_id=8234 > > but no ri_cal project: > > http://rubyforge.org/projects/ri_cal (which is 404) > > If you want to release as the rical project, this should do it: > > $ rubyforge config rical > $ rake release > > Usually rubyforge correctly adds the package_id, but sometimes it seems to > forget. > > Check your rubyforge_project under `rake debug_gem` to make sure it matches. > _______________________________________________ > Rubygems-developers mailing list > http://rubyforge.org/projects/rubygems > Rubygems-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers > -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Twitter: http://twitter.com/RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale From rick.denatale at gmail.com Thu May 28 17:50:36 2009 From: rick.denatale at gmail.com (Rick DeNatale) Date: Thu, 28 May 2009 17:50:36 -0400 Subject: [Rubygems-developers] Hoe, Rubyforge, and name confusion In-Reply-To: <3DB9C772-0D5D-4757-BBE4-80504CF933E0@gmail.com> References: <02ADBA94-A295-493F-9BAB-4ABB9B7B4E5D@gmail.com> <3DB9C772-0D5D-4757-BBE4-80504CF933E0@gmail.com> Message-ID: On Thu, May 28, 2009 at 5:23 PM, John Barnette wrote: > On May 28, 2009, at 11:20 AM, Rick DeNatale wrote: >> >> How? ?I've found the 'documentation' for hoe rather ephemeral. > > Have you tried the basics? "ri Hoe" was how I found rubyforge_project, and > it looks like pretty complete docs to me. Is there a bad website out there > somewhere we need to update? Yes, the problem is that I'm finding stuff too abstract and I can't map to what I'm seeing on the Rubyforge web api. As I said, I think that my project name is ri_cal, but rubyforge had me also give a unix name which couldn't have underscores, so I made that ri-cal. For example, from the ri Hoe.new("project_name", Project::VERSION) do |p| p.rubyforge_name = "rf_project" p.developer("Joe Blow", "joe at example.com") # add other details here end What's the difference here between "project_name" and "rf_project", how do I map those to RubyForge? Right now I've got: $hoe = Hoe.new('ri_cal', RiCal::VERSION) do |p| p.developer('author=Rick DeNatale', 'rick.denatale at gmail.com') p.changes = p.paragraphs_of("History.txt", 0..1).join("\n\n") p.rubyforge_name = 'ri-cal' p.extra_dev_deps = [ ['newgem', ">= #{::Newgem::VERSION}"] ] p.clean_globs |= %w[**/.DS_Store tmp *.log] path = (p.rubyforge_name == p.name) ? p.rubyforge_name : "\#{p.rubyforge_name}/\#{p.name}" p.remote_rdoc_dir = File.join(path.gsub(/^#{p.rubyforge_name}\/?/,''), 'rdoc') p.rsync_args = '-av --delete --ignore-errors' end The last thing I changed was p.rubyforge_name from 'ri_cal' to 'ri-cal' And now when I try to release it ends with: no configured for I'm generally pretty good at figuring my way through configuration issues like this, but for whatever reason, I'm stymied and a bit frustrated here. -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Twitter: http://twitter.com/RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale From drbrain at segment7.net Thu May 28 20:08:20 2009 From: drbrain at segment7.net (Eric Hodel) Date: Thu, 28 May 2009 17:08:20 -0700 Subject: [Rubygems-developers] Hoe, Rubyforge, and name confusion In-Reply-To: References: <02ADBA94-A295-493F-9BAB-4ABB9B7B4E5D@gmail.com> Message-ID: <23DB40B5-023C-462A-B1B9-F9C85116C173@segment7.net> On May 28, 2009, at 14:25, Rick DeNatale wrote: > On Thu, May 28, 2009 at 4:57 PM, Eric Hodel > wrote: >> On May 28, 2009, at 12:52, Rick DeNatale wrote: >> >>> I'm getting nowhere fast. >>> >>> I'm still getting "invalid package_id" when I try to release. >>> >>> I tried >>> >>> rubyforge create_package <> ri_cal >>> >>> which added a new package number to my autoconfig.yml, but when I >>> try >>> to release THAT is the new number which comes up as invalid. >>> >>> I guess I'm going to have to manually upload the gem through the web >>> interface AGAIN. >>> >>> I'd sure love to get some advice, it's not that I haven't already >>> been >>> pulling my hair out with google and reading the code in the hoe and >>> rubyforge gems. >> >> I've found an rical package under the rical project: >> >> http://rubyforge.org/frs/?group_id=8234 >> >> but no ri_cal project: >> >> http://rubyforge.org/projects/ri_cal (which is 404) >> >> If you want to release as the rical project, this should do it: >> >> $ rubyforge config rical >> $ rake release >> >> Usually rubyforge correctly adds the package_id, but sometimes it >> seems to >> forget. >> >> Check your rubyforge_project under `rake debug_gem` to make sure it >> matches. > > The rical project was abandoned when I couldn't get that to work since > the gem is named ri_cal. > > So I created the ri_cal project, and I've manually release three > versions there: > > http://rubyforge.org/frs/?group_id=8408 > > That's also the one which had been published to the world, so I really > want to get that project working with hoe. No, that's the ri-cal project, not ri_cal. ri-cal works: http://rubyforge.org/projects/ri-cal ri_cal is invalid: http://rubyforge.org/projects/ri_cal Switching everything to ri-cal should work out of the box. PS: Don't top post. From noreply at rubyforge.org Thu May 28 20:13:26 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 28 May 2009 20:13:26 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-26000 ] Typo in requirements documentation Message-ID: <20090529001326.D7396159802E@rubyforge.org> Bugs item #26000, was opened at 2009-05-23 08:44 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26000&group_id=126 Category: documentation Group: v1.3.x >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Mike Gunderloy (mikeg1) >Assigned to: Eric Hodel (drbrain) >Summary: Typo in requirements documentation Initial Comment: RDoc for 1.3.3 for Gem::Requirement#parse says "The requirement can be a String or a Gem::Version. A String can be an operator (<, <=, =, =>, >, !=, ~>), a version number, or both, operator first." That should actually read "The requirement can be a String or a Gem::Version. A String can be an operator (<, <=, =, >=, >, !=, ~>), a version number, or both, operator first." Note transposition of characters - we love hashrockets in Ruby, but not as comparison operators. I could submit a patch for this, but that seems more trouble than it's worth. ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2009-05-28 17:13 Message: Fixed, thanks! PS: If you submit a patch, you get "Patch by" instead of "Bug by" in the ChangeLog, which is far more prestigious! ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26000&group_id=126 From rick.denatale at gmail.com Thu May 28 20:38:10 2009 From: rick.denatale at gmail.com (Rick DeNatale) Date: Thu, 28 May 2009 20:38:10 -0400 Subject: [Rubygems-developers] Hoe, Rubyforge, and name confusion In-Reply-To: <23DB40B5-023C-462A-B1B9-F9C85116C173@segment7.net> References: <02ADBA94-A295-493F-9BAB-4ABB9B7B4E5D@gmail.com> <23DB40B5-023C-462A-B1B9-F9C85116C173@segment7.net> Message-ID: On Thu, May 28, 2009 at 8:08 PM, Eric Hodel wrote: > On May 28, 2009, at 14:25, Rick DeNatale wrote: >> >> On Thu, May 28, 2009 at 4:57 PM, Eric Hodel wrote: >>> >>> On May 28, 2009, at 12:52, Rick DeNatale wrote: >>> >>>> I'm getting nowhere fast. >>>> >>>> I'm still getting "invalid package_id" when I try to release. >>>> >>>> I tried >>>> >>>> rubyforge create_package <> ri_cal >>>> >>>> which added a new package number to my autoconfig.yml, but when I try >>>> to release THAT is the new number which comes up as invalid. >>>> >>>> I guess I'm going to have to manually upload the gem through the web >>>> interface AGAIN. >>>> >>>> I'd sure love to get some advice, it's not that I haven't already been >>>> pulling my hair out with google and reading the code in the hoe and >>>> rubyforge gems. >>> >>> I've found an rical package under the rical project: >>> >>> http://rubyforge.org/frs/?group_id=8234 >>> >>> but no ri_cal project: >>> >>> http://rubyforge.org/projects/ri_cal (which is 404) >>> >>> If you want to release as the rical project, this should do it: >>> >>> $ rubyforge config rical >>> $ rake release >>> >>> Usually rubyforge correctly adds the package_id, but sometimes it seems >>> to >>> forget. >>> >>> Check your rubyforge_project under `rake debug_gem` to make sure it >>> matches. >> >> The rical project was abandoned when I couldn't get that to work since >> the gem is named ri_cal. >> >> So I created the ri_cal project, and I've manually release three versions >> there: >> >> http://rubyforge.org/frs/?group_id=8408 >> >> That's also the one which had been published to the world, so I really >> want to get that project working with hoe. > > No, that's the ri-cal project, not ri_cal. > > ri-cal works: http://rubyforge.org/projects/ri-cal > > ri_cal is invalid: http://rubyforge.org/projects/ri_cal > > Switching everything to ri-cal should work out of the box. Well assuming it will, which it didn't (at least where I thought to switch) how was I to interpret what I got from RubyForge Your project registration for RubyForge has been approved! Project Full Name: ri_cal Project Unix Name: ri-cal Virtual host: ri-cal.rubyforge.org To hoe settings? Now in my rake file I've now got: $hoe = Hoe.new('ri-cal', RiCal::VERSION) do |p| p.developer('author=Rick DeNatale', 'rick.denatale at gmail.com') p.changes = p.paragraphs_of("History.txt", 0..1).join("\n\n") p.rubyforge_name = 'ri-cal' p.extra_dev_deps = [ ['newgem', ">= #{::Newgem::VERSION}"] ] p.clean_globs |= %w[**/.DS_Store tmp *.log] path = (p.rubyforge_name == p.name) ? p.rubyforge_name : "\#{p.rubyforge_name}/\#{p.name}" p.remote_rdoc_dir = File.join(path.gsub(/^#{p.rubyforge_name}\/?/,''), 'rdoc') p.rsync_args = '-av --delete --ignore-errors' end And when I do rake release I get: ... Gem build output supressed Successfully built RubyGem Name: ri-cal Version: 0.5.2 File: ri-cal-0.5.2.gem mv ri-cal-0.5.2.gem pkg/ri-cal-0.5.2.gem Logging in Releasing ri-cal v. 0.5.2 rake aborted! no configured for (See full trace by running task with --trace) And it's now building the gem with the name ri-cal rather than ri_cal which is problematic since it's rubhredrick-ri_cal on github AND ri_cal in the RubyForge project for the three versions I've already manually released. Is there a way to tell hoe that the gem's name is ri_cal. -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Twitter: http://twitter.com/RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale From ryand-ruby at zenspider.com Fri May 29 14:36:30 2009 From: ryand-ruby at zenspider.com (Ryan Davis) Date: Fri, 29 May 2009 11:36:30 -0700 Subject: [Rubygems-developers] Hoe, Rubyforge, and name confusion In-Reply-To: References: <02ADBA94-A295-493F-9BAB-4ABB9B7B4E5D@gmail.com> Message-ID: On May 28, 2009, at 11:20 , Rick DeNatale wrote: > How? I've found the 'documentation' for hoe rather ephemeral. even when I try ppl bitch. :P > ephemeral |??fem(?)r?l| > adjective > lasting for a very short time : fashions are ephemeral. See note at > temporary .? (chiefly of plants) having a very short life cycle. um. no. > % ri Hoe | lc -l > 309 I hardly think that ephemeral is the right word for the following. I've had this fairly well documented since 1.0.3 (Sep 23 2006). > % ri Hoe > ---------------------------------------------------- Class: Hoe < > Object > hoe - a tool to help rake > > Hoe is a simple rake/rubygems helper for project Rakefiles. It > generates all the usual tasks for projects including rdoc > generation, testing, packaging, and deployment. > > > Using Hoe > --------- > > Basics > > Use this as a minimal starting point: > > require 'hoe' > require './lib/project.rb' > > Hoe.new("project_name", Project::VERSION) do |p| > p.rubyforge_name = "rf_project" > p.developer("Joe Blow", "joe at example.com") > # add other details here > end > > # add other tasks here > > Tasks Provided: > > announce: Create news email file and post to rubyforge. > > audit: Run ZenTest against the package. > > check_extra_deps: Install missing dependencies. > > check_manifest: Verify the manifest. > > clean: Clean up all the extras. > > config_hoe: Create a fresh ~/.hoerc file. > > debug_gem: Show information about the gem. > > default: Run the default task(s). > > deps:email: Print a contact list for gems dependent on this > gem > > deps:fetch: Fetch all the dependent gems of this gem into > tarballs > > deps:list: List all the dependent gems of this gem > > docs: Build the docs HTML Files > > email: Generate email announcement file. > > flay: Analyze for code duplication. > > flog: Analyze code complexity. > > gem: Build the gem file hoe-1.9.0.gem > > generate_key: Generate a key for signing your gems. > > install_gem: Install the package as a gem. > > multi: Run the test suite using multiruby. > > package: Build all the packages > > post_blog: Post announcement to blog. > > post_news: Post announcement to rubyforge. > > publish_docs: Publish RDoc to RubyForge. > > rcov: Analyze code coverage with tests > > release: Package and upload the release to rubyforge. > > ridocs: Generate ri locally for testing. > > tasks: Generate a list of tasks for doco. > > test: Run the test suite. > > test_deps: Show which test files fail when run alone. > > Extra Configuration Options: > > Run +config_hoe+ to generate a new ~/.hoerc file. The file is a > YAML formatted config file with the following settings: > > exclude: A regular expression of files to exclude > from > +check_manifest+. > > publish_on_announce: Run +publish_docs+ when you run +release+. > > signing_key_file: Signs your gems with this private key. > > signing_cert_file: Signs your gem with this certificate. > > blogs: An array of hashes of blog settings. > > Run +config_hoe+ and see ~/.hoerc for examples. > > Signing Gems: > > Run the 'generate_key' task. This will: > > 1. Configure your ~/.hoerc. > > 2. Generate a signing key and certificate. > > 3. Install the private key and public certificate files into > ~/.gem. > > 4. Upload the certificate to RubyForge. > > Hoe will now generate signed gems when the package task is run. > If > you have multiple machines you build gems on, be sure to install > your key and certificate on each machine. > > Keep your private key secret! Keep your private key safe! > > To make sure your gems are signed run: > > rake package; tar tf pkg/yourproject-1.2.3.gem > > If your gem is signed you will see: > > data.tar.gz > data.tar.gz.sig > metadata.gz > metadata.gz.sig > > Platform awareness > > Hoe allows bundling of pre-compiled extensions in the +package+ > task. > > To create a package for your current platform: > > rake package INLINE=1 > > This will force Hoe analize your +Inline+ already compiled > extensions and include them in your gem. > > If somehow you need to force a specific platform: > > rake package INLINE=1 FORCE_PLATFORM=mswin32 > > This will set the +Gem::Specification+ platform to the one > indicated in +FORCE_PLATFORM+ (instead of default > Gem::Platform::CURRENT) > > ------------------------------------------------------------------------ > > > Constants: > ---------- > > FILTER = ENV['FILTER'] || ENV['TESTOPTS'] > Used to add flags to test_unit (e.g., -n test_borked). > > eg FILTER="-n test_blah" > > GEMURL = URI.parse 'http://gems.rubyforge.org' > RUBY_DEBUG = ENV['RUBY_DEBUG'] > Used to add extra flags to RUBY_FLAGS. > > RUBY_FLAGS = ENV['RUBY_FLAGS'] || default_ruby_flags > Used to specify flags to ruby [has smart default]. > > SUPPORTED_TEST_FRAMEWORKS = { :testunit => "test/unit", > :minitest => "minitest/autorun", } > Configuration for the supported test frameworks for test > task. > > VERSION = '1.12.2' > > > Attributes: > ----------- > > author (RW): > *MANDATORY*: The author(s) of the package. (can be array) > > blog_categories (RW): > *Optional*: An array of the project's blog categories. > Defaults to project name. > > changes (RW): > Optional: A description of the release's latest changes. > Auto-populates. > > clean_globs (RW): > Optional: An array of file patterns to delete on clean. > > description (RW): > Optional: A description of the project. Auto-populates. > > description_sections (RW): > Optional: What sections from the readme to use for > auto-description. Defaults to %w(description). > > email (RW): > *MANDATORY*: The author's email address(es). (can be array) > > extra_deps (RW): > Optional: An array of rubygem dependencies. > > extra_dev_deps (RW): > Optional: An array of rubygem developer dependencies. > > extra_rdoc_files (RW): > Optional: Extra files you want to add to RDoc. > > .txt files are automatically included (excluding the > obvious). > > flay_threshold (RW): > Optional: flay threshold to determine threshold failure. > [default: 1200-100] > > flog_threshold (RW): > Optional: flog threshold to determine threshold failure. > [default: 1500-200] > > history_file (RW): > Optional: The filename for the project history. [default: > History.txt] > > multiruby_skip (RW): > Optional: Array of incompatible versions for multiruby > filtering. Used as a regex. > > name (RW): > *MANDATORY*: The name of the release. > > need_tar (RW): > Optional: Should package create a tarball? [default: true] > > need_zip (RW): > Optional: Should package create a zipfile? [default: false] > > post_install_message (RW): > Optional: A post-install message to be displayed when gem is > installed. > > readme_file (RW): > Optional: The filename for the project readme. [default: > README.txt] > > remote_rdoc_dir (RW): > Optional: Name of RDoc destination directory on Rubyforge. > [default: +name+] > > rspec_dirs (RW): > Optional: RSpec dirs. [default: %w(spec lib)] > > rspec_options (RW): > Optional: RSpec options. [default: []] > > rsync_args (RW): > Optional: Flags for RDoc rsync. [default: "-av --delete"] > > rubyforge_name (RW): > Optional: The name of the rubyforge project. [default: > name.downcase] > > spec_extras (RW): > Optional: A hash of extra values to set in the gemspec. > Value > may be a proc. > > summary (RW): > Optional: A short summary of the project. Auto-populates. > > summary_sentences (RW): > Optional: Number of sentences from description for summary. > Defaults to 1. > > test_globs (RW): > Optional: An array of test file patterns [default: > test/**/test_*.rb] > > testlib (RW): > Optional: What test library to require [default: :testunit] > > url (RW): > Optional: The url(s) of the project. (can be array). > Auto-populates. > > version (RW): > *MANDATORY*: The version. Don't hardcode! use a constant in > the project. > > > > Class methods: > -------------- > > add_include_dirs, dependent_upon, get_gems_by_name, > get_latest_gems, get_source_index, normalize_names > > > Instance methods: > ----------------- > > developer, install_gem, missing, normalize_deps, paragraphs_of, > timebomb From ryand-ruby at zenspider.com Fri May 29 15:07:06 2009 From: ryand-ruby at zenspider.com (Ryan Davis) Date: Fri, 29 May 2009 12:07:06 -0700 Subject: [Rubygems-developers] Hoe, Rubyforge, and name confusion In-Reply-To: References: Message-ID: On May 28, 2009, at 09:10 , Rick DeNatale wrote: > no configured for > $ cat ~/.rubyforge/auto-config.yml > --- [...] > group_ids: > ri-cal: 8408 > rical: 8234 > package_ids: > ri-cal: 11330 > rical: 11041 you've got a registered package of "ri-cal" and "rical" but not "ri_cal" which is what you configured > $hoe = Hoe.new('ri_cal', RiCal::VERSION) do |p| > p.developer('author=Rick DeNatale', 'rick.denatale at gmail.com') > p.changes = p.paragraphs_of("History.txt", > 0..1).join("\n\n") > p.rubyforge_name = 'ri-cal' > p.extra_dev_deps = [ > ['newgem', ">= #{::Newgem::VERSION}"] > ] > > p.clean_globs |= %w[**/.DS_Store tmp *.log] > path = (p.rubyforge_name == p.name) ? p.rubyforge_name : > "\#{p.rubyforge_name}/\#{p.name}" > p.remote_rdoc_dir = File.join(path.gsub(/^#{p.rubyforge_name} > \/?/,''), 'rdoc') > p.rsync_args = '-av --delete --ignore-errors' > end I have no idea what all that crap in there is... I'm going to assume that is from newgem and ignore it. This should suffice: > Hoe.new('ri_cal', RiCal::VERSION) do |p| > p.rubyforge_name = 'ri-cal' > > p.developer('Rick DeNatale', 'rick.denatale at gmail.com') > end isn't that prettier? this means: the gem name is "ri_cal" and it is published under the "ri- cal" rubyforge project. This appears to be the case: https://rubyforge.org/projects/ri-cal/ has: https://rubyforge.org/frs/monitor.php?filemodule_id=11330&group_id=8408&start=1 and: https://rubyforge.org/frs/download.php/57553/ri_cal-0.5.2.gem I have to admit, I have very few rubyforge projects with "-" in the name AND discrepancies against the gem name... I've done test-unit but that had the same name on both. If the above snippet doesn't work, there is quite possibly a bug somewhere and you'll have to try to track it down with "ruby -d". I'd start with the rubyforge gem as your target. From noreply at rubyforge.org Fri May 29 16:07:18 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 29 May 2009 16:07:18 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-26050 ] gem links native extensions against wrong version of ruby Message-ID: <20090529200718.46DAD1598086@rubyforge.org> Bugs item #26050, was opened at 2009-05-27 16:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26050&group_id=126 Category: None Group: None >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: Aaron Turner (synfinatic) Assigned to: Nobody (None) Summary: gem links native extensions against wrong version of ruby Initial Comment: I have ruby 1.8 (/usr/bin/ruby) and 1.9.1 (/usr/bin/ruby1.9) installed. I downloaded rubygems 1.3.3 and ran: ruby1.9 setup.rb which correctly installed rubygems in /usr/lib/ruby/site_ruby/1.9.1 but did not honor the default --format-executable flag since it created /usr/bin/gem rather then /usr/bin/gem1.9 I then copied over /usr/bin/gem -> /usr/bin/gem1.9 and edited the shebang appropriately and tried installing hpricot: gem1.9 install hpricot which built, but was incorrectly linked against ruby 1.8: ldd /usr/lib/ruby/gems/1.9.1/gems/hpricot-0.8.1/lib/hpricot_scan.so libruby.so.1.8 => /usr/lib/libruby.so.1.8 (0x0049b000) libc.so.6 => /lib/tls/libc.so.6 (0x00ca1000) libdl.so.2 => /lib/libdl.so.2 (0x008d5000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x00b6f000) libm.so.6 => /lib/tls/libm.so.6 (0x0032f000) /lib/ld-linux.so.2 (0x46843000) This results in hpricot segfaulting immediately upon require. Extras: output of gem1.9 install -V hpricot: http://pastie.org/492109 hpricot Makefile: http://pastie.org/492106 Note: I (synfinatic) was working with drbrain on #ruby-lang on this issue. ---------------------------------------------------------------------- >Comment By: Aaron Turner (synfinatic) Date: 2009-05-29 13:07 Message: Closing ticket. Issue turned out to be how ruby was built/installed (you can't just rename /usr/bin/ruby to /usr/bin/ruby1.9 and expect it to work properly). Using the configure --program-suffix option resolved the issue. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26050&group_id=126 From drbrain at segment7.net Sat May 30 10:22:50 2009 From: drbrain at segment7.net (Eric Hodel) Date: Sat, 30 May 2009 07:22:50 -0700 Subject: [Rubygems-developers] [ANN] RubyGems 1.3.4 Message-ID: <8F5BC8B8-8312-4A63-A17A-82976E1FC10A@segment7.net> NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no rubygems-update installed. You will need to follow the second set of update instructions if you see "Nothing to update". Release 1.3.4 fixes some bugs and adds some features. Bug Fixes: * Fixed various warnings * Gem::ruby_version works correctly for 1.8 branch and trunk * Prerelease gems now show up in `gem list` and can be used * Fixed option name for `gem setup --format-executable` * RubyGems now matches Ruby > 1.9.1 gem paths * Gem::RemoteFetcher#download now works for explicit Windows paths across drives. Bug #25882 by Lars Christensen * Fix typo in Gem::Requirement#parse. Bug #26000 by Mike Gunderloy. Deprecation Notices: * Bulk index update is no longer supported (the code currently remains, but not the tests) * Gem::manage_gems was removed in 1.3.3. * Time::today was removed in 1.3.3. For a full list of changes to RubyGems and the contributor for each change, see the ChangeLog file. == How can I get RubyGems? NOTE: If you have installed RubyGems using a package system you may want to install a new RubyGems through the same packaging system. If you have a recent version of RubyGems (0.8.5 or later), then all you need to do is: $ gem update --system (you might need to be admin/root) NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no rubygems-update installed. You will need to follow the second set of update instructions if you see "Nothing to update". NOTE: You may have to run the command twice if you have any previosly installed rubygems-update gems. If you have an older version of RubyGems installed, then you can still do it in two steps: $ gem install rubygems-update (again, might need to be admin/root) $ update_rubygems (... here too) If you don't have any gems install, there is still the pre-gem approach to getting software ... doing it manually: 1. DOWNLOAD FROM: http://rubyforge.org/frs/?group_id=126 2. UNPACK INTO A DIRECTORY AND CD THERE 3. INSTALL WITH: ruby setup.rb (you may need admin/root privilege) == To File Bugs The RubyGems bug tracker can be found on RubyForge at: http://rubyforge.org/tracker/?func=add&group_id=126&atid=575 When filing a bug, `gem env` output will be helpful in diagnosing the issue. If you find a bug where RubyGems crashes, please provide debug output. You can do that with `gem --debug the_command`. == Thanks Keep those gems coming! -- The RubyGems team From noreply at rubyforge.org Sat May 30 12:49:18 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 30 May 2009 12:49:18 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-26069 ] Error uninstalling pre-release gem Message-ID: <20090530164918.A3E7F185810C@rubyforge.org> Bugs item #26069, was opened at 2009-05-30 16:49 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26069&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: David Chelimsky (dchelimsky) Assigned to: Nobody (None) Summary: Error uninstalling pre-release gem Initial Comment: $ gem list rspec *** LOCAL GEMS *** rspec (1.2.7.a) $ sudo gem uninstall rspec Remove executables: autospec, spec in addition to the gem? [Yn] y Removing autospec Removing spec ERROR: While executing gem ... (NoMethodError) undefined method `name' for nil:NilClass $ gem list rspec *** LOCAL GEMS *** rspec (1.2.7.a) ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26069&group_id=126 From noreply at rubyforge.org Sat May 30 12:53:42 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 30 May 2009 12:53:42 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-26069 ] Error uninstalling pre-release gem Message-ID: <20090530165342.718271858124@rubyforge.org> Bugs item #26069, was opened at 2009-05-30 16:49 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26069&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: David Chelimsky (dchelimsky) Assigned to: Nobody (None) Summary: Error uninstalling pre-release gem Initial Comment: $ gem list rspec *** LOCAL GEMS *** rspec (1.2.7.a) $ sudo gem uninstall rspec Remove executables: autospec, spec in addition to the gem? [Yn] y Removing autospec Removing spec ERROR: While executing gem ... (NoMethodError) undefined method `name' for nil:NilClass $ gem list rspec *** LOCAL GEMS *** rspec (1.2.7.a) ---------------------------------------------------------------------- >Comment By: David Chelimsky (dchelimsky) Date: 2009-05-30 16:53 Message: $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.4 - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [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/david/.gem/ruby/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/ge ms/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/"] - "gem" => "--no-ri --no-rdoc" - REMOTE SOURCES: - http://gems.rubyforge.org/ - http://gems.github.com/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26069&group_id=126