From jbarnette at gmail.com Thu Oct 1 02:44:01 2009 From: jbarnette at gmail.com (John Barnette) Date: Wed, 30 Sep 2009 23:44:01 -0700 Subject: [Rubygems-developers] Gem name validation Message-ID: <3E429D1D-AFEC-4D6C-9F24-B0F7D1FCEB6F@gmail.com> All, I'd like to add an error to Specification#validate if the spec's name doesn't match /[a-z][a-z0-9-_]*/i. Any objections? Disregarding obviously malformed specs, all current gem names match. ~ j. From thewoolleyman at gmail.com Thu Oct 1 03:47:11 2009 From: thewoolleyman at gmail.com (Chad Woolley) Date: Thu, 1 Oct 2009 00:47:11 -0700 Subject: [Rubygems-developers] Gem name validation In-Reply-To: <3E429D1D-AFEC-4D6C-9F24-B0F7D1FCEB6F@gmail.com> References: <3E429D1D-AFEC-4D6C-9F24-B0F7D1FCEB6F@gmail.com> Message-ID: On Wed, Sep 30, 2009 at 11:44 PM, John Barnette wrote: > All, > > I'd like to add an error to Specification#validate if the spec's name > doesn't match /[a-z][a-z0-9-_]*/i. Any objections? Disregarding obviously > malformed specs, all current gem names match. That sounds like a good idea. From luislavena at gmail.com Thu Oct 1 04:31:21 2009 From: luislavena at gmail.com (Luis Lavena) Date: Thu, 1 Oct 2009 10:31:21 +0200 Subject: [Rubygems-developers] Gem name validation In-Reply-To: <3E429D1D-AFEC-4D6C-9F24-B0F7D1FCEB6F@gmail.com> References: <3E429D1D-AFEC-4D6C-9F24-B0F7D1FCEB6F@gmail.com> Message-ID: <71166b3b0910010131o6c0ed229nd78c7ed788acde96@mail.gmail.com> On Thu, Oct 1, 2009 at 8:44 AM, John Barnette wrote: > All, > > I'd like to add an error to Specification#validate if the spec's name > doesn't match /[a-z][a-z0-9-_]*/i. Any objections? Disregarding obviously > malformed specs, all current gem names match. > No objection from here, that will reduce some gem install issues I got reported for Ruby Installer project. 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 josh at hasmanythrough.com Thu Oct 1 10:41:33 2009 From: josh at hasmanythrough.com (Josh Susser) Date: Thu, 1 Oct 2009 07:41:33 -0700 Subject: [Rubygems-developers] Gem name validation In-Reply-To: <3E429D1D-AFEC-4D6C-9F24-B0F7D1FCEB6F@gmail.com> References: <3E429D1D-AFEC-4D6C-9F24-B0F7D1FCEB6F@gmail.com> Message-ID: On Sep 30, 2009, at 11:44 PM, John Barnette wrote: > I'd like to add an error to Specification#validate if the spec's > name doesn't match /[a-z][a-z0-9-_]*/i. Any objections? Disregarding > obviously malformed specs, all current gem names match. Sounds good, with one minor nitpick: your regexp isn't valid. A dash in a character class must be in the first position to be a literal dash instead of a range separator. Use /[a-z][-_a-z0-9]*/i or /[a-z][- \w]*/i instead. Are we sure today isn't another Monday? -- Josh Susser http://blog.hasmanythrough.com From jbarnette at gmail.com Thu Oct 1 14:01:07 2009 From: jbarnette at gmail.com (John Barnette) Date: Thu, 1 Oct 2009 11:01:07 -0700 Subject: [Rubygems-developers] Gem name validation In-Reply-To: References: <3E429D1D-AFEC-4D6C-9F24-B0F7D1FCEB6F@gmail.com> Message-ID: <0BF3ADFF-A225-4F3A-AC82-A3BAF21F7238@gmail.com> On Oct 1, 2009, at 7:41 AM, Josh Susser wrote: > > On Sep 30, 2009, at 11:44 PM, John Barnette wrote: >> I'd like to add an error to Specification#validate if the spec's >> name doesn't match /[a-z][a-z0-9-_]*/i. Any objections? >> Disregarding obviously malformed specs, all current gem names match. > > > Sounds good, with one minor nitpick: your regexp isn't valid. A > dash in a character class must be in the first position to be a > literal dash instead of a range separator. Use /[a-z][-_a-z0-9]*/i > or /[a-z][-\w]*/i instead. /\A[a-z][a-z0-9_\-]*\Z/i # if you really really need to be that guy :p > Are we sure today isn't another Monday? On the contrary, we are *certain* today is another Monday. ~ j. From noreply at rubyforge.org Sat Oct 3 08:29:02 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 3 Oct 2009 08:29:02 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27228 ] gem which shell.rb fails Message-ID: <20091003122902.F3BBF1858282@rubyforge.org> Bugs item #27228, was opened at 2009-10-03 12:29 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27228&group_id=126 Category: `gem` commands (other) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Roger Pack (rogerdpack) Assigned to: Nobody (None) Summary: gem which shell.rb fails Initial Comment: I believe the following is not expected (i.e. bug) C:\dev\blade_copy\digitalarchive_trunk>gem which shell.rb Can't find ruby library file or shared library shell.rb C:\dev\blade_copy\digitalarchive_trunk>gem which shell c:/ruby18/lib/ruby/1.8/shell.rb Thanks. -r ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27228&group_id=126 From noreply at rubyforge.org Mon Oct 5 22:12:48 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 5 Oct 2009 22:12:48 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27244 ] ruby: no such file to load -- ubygems (LoadError) when installing rubygems Message-ID: <20091006021248.F09621D78853@rubyforge.org> Bugs item #27244, was opened at 2009-10-05 19:12 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27244&group_id=126 Category: RubyGems installer (setup.rb) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Tom Lianza (tlianza) Assigned to: Nobody (None) Summary: ruby: no such file to load -- ubygems (LoadError) when installing rubygems Initial Comment: I'm trying to install rubygems on a system that has never had it. I downloaded the latest version (1.3.5) and when I ran ruby setup.rb install, I get the error above: ruby: no such file to load -- ubygems (LoadError) when installing rubygems The README says this is only an update, so I assume that I need to download an older version - but I grabbed 1.3.0 and saw the same thing. So... I'm a little perplexed because it *seems* like rubygems is a requirement to install rubygems based on the errors. But, it could well be that I'm doing something stupid. FWIW I'm in a Cygwin/Windows env. Thanks! Tom ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27244&group_id=126 From noreply at rubyforge.org Tue Oct 6 02:03:39 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 6 Oct 2009 02:03:39 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27244 ] ruby: no such file to load -- ubygems (LoadError) when installing rubygems Message-ID: <20091006060340.0D65C1D78827@rubyforge.org> Bugs item #27244, was opened at 2009-10-05 23:12 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27244&group_id=126 Category: RubyGems installer (setup.rb) Group: None >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: Tom Lianza (tlianza) Assigned to: Nobody (None) Summary: ruby: no such file to load -- ubygems (LoadError) when installing rubygems Initial Comment: I'm trying to install rubygems on a system that has never had it. I downloaded the latest version (1.3.5) and when I ran ruby setup.rb install, I get the error above: ruby: no such file to load -- ubygems (LoadError) when installing rubygems The README says this is only an update, so I assume that I need to download an older version - but I grabbed 1.3.0 and saw the same thing. So... I'm a little perplexed because it *seems* like rubygems is a requirement to install rubygems based on the errors. But, it could well be that I'm doing something stupid. FWIW I'm in a Cygwin/Windows env. Thanks! Tom ---------------------------------------------------------------------- >Comment By: Luis Lavena (luislavena) Date: 2009-10-06 03:03 Message: This is related to RUBYOPT environment variable being set. Please unset RUBYOPT from your System preferences. Previous versions of Ruby Installer for Windows (One-Click) used to set it, that is no longer true. Since you're using Cygwin, is not clear how that variable got set. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27244&group_id=126 From stephen.bannasch at deanbrook.org Tue Oct 6 02:51:43 2009 From: stephen.bannasch at deanbrook.org (Stephen Bannasch) Date: Tue, 6 Oct 2009 02:51:43 -0400 Subject: [Rubygems-developers] does rubygems support platform-specific gem dependencies? Message-ID: I've patched the highline gem to use 'ffi-ncurses' when it is running in jruby instead of `stty` (which doesn't work properly in jruby). See: http://github.com/stepheneb/highline/tree/jruby Is there a way to add a platform-specific gem dependency in a Gem::Specification? Right now I throw an error telling users to install ff-ncurses manually. From noreply at rubyforge.org Wed Oct 7 10:18:09 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 7 Oct 2009 10:18:09 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Feature Requests-27252 ] gem install --test should imply --development Message-ID: <20091007141809.95C7018582DD@rubyforge.org> Feature Requests item #27252, was opened at 2009-10-07 14:18 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=27252&group_id=126 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: James Tucker (raggi) Assigned to: Nobody (None) Summary: gem install --test should imply --development Initial Comment: More often than otherwise, running tests requires the development dependencies, I think this would be a sensible default to derive. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=27252&group_id=126 From noreply at rubyforge.org Thu Oct 8 20:31:27 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 8 Oct 2009 20:31:27 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-26740 ] outdated rubygems/rubygems_version.rb still exists on Leopard default ruby install even though it was removed in 1.3.5 Message-ID: <20091009003127.7517B1779934@rubyforge.org> Bugs item #26740, was opened at 2009-07-24 07:44 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126 Category: None Group: None Status: Open Resolution: Rejected Priority: 3 Submitted By: Chad Woolley (thewoolleyman) Assigned to: Nobody (None) Summary: outdated rubygems/rubygems_version.rb still exists on Leopard default ruby install even though it was removed in 1.3.5 Initial Comment: Does system installer not delete old files? If someone happens to load this file, they get a warning, then get the wrong version. Can't we just move the version back into this file and avoid the issue altogether? chadmac:1.8 woolley$ pwd /Library/Ruby/Site/1.8 chadmac:1.8 woolley$ grep RubyGemsVersion rubygems.rb RubyGemsVersion = VERSION = '1.3.5' chadmac:1.8 woolley$ ls rubygems/rubygems_version.rb rubygems/rubygems_version.rb chadmac:~ woolley$ irb >> Gem::RubyGemsVersion => "1.3.5" >> require 'rubygems/rubygems_version' /Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:12: warning: already initialized constant RubyGemsVersion /Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:17: warning: already initialized constant VERSION => true >> Gem::RubyGemsVersion => "1.3.4" chadmac:~ woolley$ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.5 - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [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/woolley/.gem/ruby/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://gems.rubyforge.org", "http://gems.github.com"] - REMOTE SOURCES: - http://gems.rubyforge.org - http://gems.github.com ---------------------------------------------------------------------- Comment By: Youssef Gaigi (youssefg) Date: 2009-10-09 00:31 Message: Did you figure out a way out of this. I tried to delete rubygems and install again, but still the problem is there. Here's what I get whenever i require rubygems: irb(main):001:0> require 'RubyGems' /usr/lib/ruby/site_ruby/1.8/RubyGems.rb:14: warning: already initialized constant VERSION /usr/lib/ruby/site_ruby/1.8/RubyGems.rb:14: warning: already initialized constant RubyGemsVersion /usr/lib/ruby/site_ruby/1.8/RubyGems.rb:193: warning: already initialized constant MUTEX /usr/lib/ruby/site_ruby/1.8/RubyGems.rb:195: warning: already initialized constant RubyGemsPackageVersion /usr/lib/ruby/site_ruby/1.8/RubyGems.rb:207: warning: already initialized constant WIN_PATTERNS /usr/lib/ruby/site_ruby/1.8/RubyGems.rb:1078: warning: already initialized constant MARSHAL_SPEC_DIR /usr/lib/ruby/site_ruby/1.8/RubyGems.rb:1083: warning: already initialized constant YAML_SPEC_DIR => true I appreciate your help Youssef ---------------------------------------------------------------------- Comment By: John Trupiano (jtrupiano) Date: 2009-09-18 01:53 Message: You have fixed it Chad-- our preinit wasn't enforcing 0.5.3 or greater, and this particular box did not yet have 0.5.3 installed. ---------------------------------------------------------------------- Comment By: Chad Woolley (thewoolleyman) Date: 2009-09-17 21:08 Message: "You know what, I just realized that I was loading geminstaller in the preinitializer, which was in turn loading rubygems_version.rb." I'm sure I fixed this in the latest geminstaller release. Please open a bug if I didn't. ---------------------------------------------------------------------- Comment By: John Trupiano (jtrupiano) Date: 2009-09-17 18:44 Message: Hey Ryan, You know what, I just realized that I was loading geminstaller in the preinitializer, which was in turn loading rubygems_version.rb. As a result, the "require 'rubygems'" call on line 86 of config/boot.rb was actually returning false and consequently not setting the RubyGemsVersion to 1.3.5 appropriately. This explains why I could not reproduce the problem in irb. My apologies for the noise. In any case, manually deleting the file did do the trick. -John ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2009-09-17 18:23 Message: I just looked at rails 2.3.4 and don't see any place that rubygems_version is being required. The version checking code requires rubygems and then uses RubyGemsVersion. How did you get bit by this bug? ---------------------------------------------------------------------- Comment By: John Trupiano (jtrupiano) Date: 2009-09-17 14:55 Message: I just want to point out that this exact bug bit us pretty badly again. The scenario is this (and I'm surprised it hasn't happened more frequently): We're running a rails 2.3.4 app. The rails 2.3.x branch requires rubygems 1.3.2 or greater. On this particular OSX machine, we jumped from RubyGems 1.3.1 directly to 1.3.5. As a result, this left the rubygems_version.rb file specifying version 1.3.1. As a result, we could never actually run the rails app because of the version checking code in config/boot.rb. It took us quite awhile to track down what the issue really was. Others not so in tune with RubyGems development are surely to lose a whole lot more time than we did. ---------------------------------------------------------------------- Comment By: Chad Woolley (thewoolleyman) Date: 2009-07-24 20:53 Message: Agreed, a very low priority. I was only requiring explicitly as a side effect of my regression tests - normally you should rely on rubygems to require what it needs. However, this should probably get turned into a bug with the system install command, because it isn't deleting old files. This could come back to bite us in a more serious way in the future. ---------------------------------------------------------------------- Comment By: John Trupiano (jtrupiano) Date: 2009-07-24 20:51 Message: I can confirm the odd behavior on a default Leopard install: john-mbp:1.8 john$ irb irb(main):001:0> Gem::RubyGemsVersion => "1.3.5" irb(main):002:0> require 'rubygems/rubygems_version' /Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:12: warning: already initialized constant RubyGemsVersion /Library/Ruby/Site/1.8/rubygems/rubygems_version.rb:17: warning: already initialized constant VERSION => true irb(main):003:0> Gem::RubyGemsVersion => "1.3.4" -John ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-07-24 19:16 Message: I agree, the rubygems_version.rb file should be deleted on update if possible. Mind you, I've never heard of anyone explicitly require'ing that file, so it strikes me as a very low priority item, but it's still something we could fix. Regards, Dan ---------------------------------------------------------------------- Comment By: Chad Woolley (thewoolleyman) Date: 2009-07-24 19:01 Message: Rejected with no comment, huh? Classy. You ignore the fact that there are actual bugs: * RubyGems 1.3.5 introduced an obsolete file on the Leopard distribution * This file contains an outdated and conflicting RubyGems version number * If any existing rubygems API clients happen to still load this file, they will get a warning, and rubygems will subsequently report the incorrect and outdated version. * There is a bug with the system update command that does not delete old files, at least on the default Leopard install. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26740&group_id=126 From noreply at rubyforge.org Thu Oct 8 21:24:36 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 8 Oct 2009 21:24:36 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27260 ] rubygems 1.3.5 can't install prerelease gems with dependencies Message-ID: <20091009012436.ED9D41779934@rubyforge.org> Bugs item #27260, was opened at 2009-10-08 21:24 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27260&group_id=126 Category: `gem install` command Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Aslak Helles?y (aslak_hellesoy) Assigned to: Nobody (None) Summary: rubygems 1.3.5 can't install prerelease gems with dependencies Initial Comment: To reproduce: # Make sure a dependency isn't on your system. Ignore uninstall error if you don't have it. sudo gem uninstall term-ansicolor # cucumber depends on term-ansicolor sudo gem install cucumber --version 0.4.0.rc1 ERROR: Error installing cucumber: cucumber requires term-ansicolor (>= 1.0.3, runtime) # It works fine with: sudo gem install cucumber --version 0.3.104 The error also happens if you run: sudo gem install cucumber --prerelease (I'm planning to release cucumber 0.4.0 in a few days, so this might not let you reproduce it with --prerelease). FYI: cucumber 0.4.0.rc1 was packaged with rubygems 1.3.5 ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27260&group_id=126 From noreply at rubyforge.org Fri Oct 9 17:08:22 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 9 Oct 2009 17:08:22 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Feature Requests-27269 ] Add required_ruby_implementation to the GemSpec Message-ID: <20091009210822.322341D78829@rubyforge.org> Feature Requests item #27269, was opened at 2009-10-09 14:08 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=27269&group_id=126 Category: other Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Conrad Taylor (conradwt) Assigned to: Nobody (None) Summary: Add required_ruby_implementation to the GemSpec Initial Comment: In order to fully exploit a particular Ruby implementation, it will be necessary to allow gem developers the ability to create gems targeted to a specific implementations. For example, this can be any of the following: ruby macruby rubinius maglev jruby and so on Thus, I would like to propose the adding of an additional attribute to the gem specification (i.e. GemSpec) called required_ruby_implementation. This attribute can have the 'any' value by default which specifies all Ruby implementations. Otherwise, Ruby Gem developers can tag a gem to use a specific ruby implementation when necessary. Next, this attribute will compliment the attribute, required_ruby_version. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=27269&group_id=126 From jbarnette at gmail.com Wed Oct 14 01:01:27 2009 From: jbarnette at gmail.com (John Barnette) Date: Tue, 13 Oct 2009 22:01:27 -0700 Subject: [Rubygems-developers] Behavior change for --source Message-ID: <2bce3eb60910132201y3d94bc77l15b4733c0e3e08d3@mail.gmail.com> All, I've changed the behavior of --source in trunk. Before r2315, the first specification of --source would remove the defaults from Gem.sources, requiring flags for each source that should be searched. After r2315, --source is purely additive. This makes cross-source dependencies more manageable. For a completely restricted list of sources, you can use --clear-sources: $ gem install --clear-sources --source http://only.this.one.example.com/ Eric and I have talked this over pretty thoroughly, but I'd like to hear from you if you have any concerns about this change. ~ j. From josh at hasmanythrough.com Wed Oct 14 01:52:34 2009 From: josh at hasmanythrough.com (Josh Susser) Date: Tue, 13 Oct 2009 22:52:34 -0700 Subject: [Rubygems-developers] Behavior change for --source In-Reply-To: <2bce3eb60910132201y3d94bc77l15b4733c0e3e08d3@mail.gmail.com> References: <2bce3eb60910132201y3d94bc77l15b4733c0e3e08d3@mail.gmail.com> Message-ID: <20B3A643-2971-4A55-AABE-C0288968D233@hasmanythrough.com> On Oct 13, 2009, at 10:01 PM, John Barnette wrote: > I've changed the behavior of --source in trunk. > > Before r2315, the first specification of --source would remove the > defaults from Gem.sources, requiring flags for each source that should > be searched. After r2315, --source is purely additive. This makes > cross-source dependencies more manageable. For a completely restricted > list of sources, you can use --clear-sources: > > $ gem install --clear-sources --source http://only.this.one.example.com/ > > Eric and I have talked this over pretty thoroughly, but I'd like to > hear from you if you have any concerns about this change. I've been wanting this change for over a year. Thanks! -- Josh Susser http://blog.hasmanythrough.com From thewoolleyman at gmail.com Wed Oct 14 12:17:10 2009 From: thewoolleyman at gmail.com (Chad Woolley) Date: Wed, 14 Oct 2009 09:17:10 -0700 Subject: [Rubygems-developers] Behavior change for --source In-Reply-To: <2bce3eb60910132201y3d94bc77l15b4733c0e3e08d3@mail.gmail.com> References: <2bce3eb60910132201y3d94bc77l15b4733c0e3e08d3@mail.gmail.com> Message-ID: On Tue, Oct 13, 2009 at 10:01 PM, John Barnette wrote: > $ gem install --clear-sources --source http://only.this.one.example.com/ > > Eric and I have talked this over pretty thoroughly, but I'd like to > hear from you if you have any concerns about this change. What is the behavior of the default source (gems.rubyforge.org)? Is it always used unless you pass --clear-sources? From jbarnette at gmail.com Wed Oct 14 13:11:51 2009 From: jbarnette at gmail.com (John Barnette) Date: Wed, 14 Oct 2009 10:11:51 -0700 Subject: [Rubygems-developers] Behavior change for --source In-Reply-To: References: <2bce3eb60910132201y3d94bc77l15b4733c0e3e08d3@mail.gmail.com> Message-ID: <2bce3eb60910141011s343d9cb5x9550d066c50adf14@mail.gmail.com> On Wed, Oct 14, 2009 at 9:17 AM, Chad Woolley wrote: > On Tue, Oct 13, 2009 at 10:01 PM, John Barnette wrote: >> $ gem install --clear-sources --source http://only.this.one.example.com/ >> > What is the behavior of the default source (gems.rubyforge.org)? ?Is > it always used unless you pass --clear-sources? Correct. Specifying --source doesn't replace the default sources unless --clear-sources is specified. ~ j. From thewoolleyman at gmail.com Wed Oct 14 13:52:02 2009 From: thewoolleyman at gmail.com (Chad Woolley) Date: Wed, 14 Oct 2009 10:52:02 -0700 Subject: [Rubygems-developers] Behavior change for --source In-Reply-To: <2bce3eb60910141011s343d9cb5x9550d066c50adf14@mail.gmail.com> References: <2bce3eb60910132201y3d94bc77l15b4733c0e3e08d3@mail.gmail.com> <2bce3eb60910141011s343d9cb5x9550d066c50adf14@mail.gmail.com> Message-ID: On Wed, Oct 14, 2009 at 10:11 AM, John Barnette wrote: > Correct. Specifying --source doesn't replace the default sources > unless --clear-sources is specified. Great. This sounds perfect then... From noreply at rubyforge.org Wed Oct 14 17:40:31 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 14 Oct 2009 17:40:31 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27292 ] Empty gem file prevents installation Message-ID: <20091014214032.091A218582C2@rubyforge.org> Bugs item #27292, was opened at 2009-10-14 16:40 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27292&group_id=126 Category: `gem install` command Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Ian Ragsdale (iragsdale) Assigned to: Nobody (None) Summary: Empty gem file prevents installation Initial Comment: I'm not sure how but there was an empty file in the gem cache on my system. When the gem installer tried to figure out the file format, it crashed on line 45 of format.rb: if File.read(file_path, 20).include?("MD5SUM =") If the file is empty, then file.read returns nil, and the install fails. It would be better to trap this error and give a more useful error message, so that I don't have to modify the source to figure out why the gem won't install. This is probably low priority because most users will never hit it, but I thought I'd submit it anyway. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27292&group_id=126 From noreply at rubyforge.org Thu Oct 15 23:20:04 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 15 Oct 2009 23:20:04 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27301 ] gem uninstall without sudo incorrectly reports success on OS X Message-ID: <20091016032004.A4C6F3C8037@rubyforge.org> Bugs item #27301, was opened at 2009-10-15 21:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27301&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Craig Walker (softcraft) Assigned to: Nobody (None) Summary: gem uninstall without sudo incorrectly reports success on OS X Initial Comment: On my system (OS X 10.5.8), uninstalling a gem without using "sudo" first causes gem to report that it uninstalled the gem. However, it does not do so; the gem remains intalled. I install gems using sudo; I get error messages if I forget it. Running with --debug shows plenty of permissions errors, but those aren't propagated up under normal circumstances. Attached is a copy of a gem session that shows the error and the pertinent info. Is this a widespread issue? If so, could it be fixed so that it correctly fails? Thanks, Craig Walker SoftCraft Development ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27301&group_id=126 From noreply at rubyforge.org Fri Oct 16 15:27:34 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 16 Oct 2009 15:27:34 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27301 ] gem uninstall without sudo incorrectly reports success on OS X Message-ID: <20091016192734.8ECDD18582C9@rubyforge.org> Bugs item #27301, was opened at 2009-10-15 20:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27301&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Craig Walker (softcraft) Assigned to: Nobody (None) Summary: gem uninstall without sudo incorrectly reports success on OS X Initial Comment: On my system (OS X 10.5.8), uninstalling a gem without using "sudo" first causes gem to report that it uninstalled the gem. However, it does not do so; the gem remains intalled. I install gems using sudo; I get error messages if I forget it. Running with --debug shows plenty of permissions errors, but those aren't propagated up under normal circumstances. Attached is a copy of a gem session that shows the error and the pertinent info. Is this a widespread issue? If so, could it be fixed so that it correctly fails? Thanks, Craig Walker SoftCraft Development ---------------------------------------------------------------------- >Comment By: Ryan Davis (zenspider) Date: 2009-10-16 12:27 Message: I'd have to guess that you or macports messed with your perms in some way, or macports patches rubygems? The only other difference I see is in GEM_PATH, so that is prolly easier to check first. I can't repro this at all: drwxr-xr-x 7 root admin 374 Aug 31 15:14 zenweb-2.18.1/ 503 % gem uninstall zenweb Remove executables: zenweb, zenwebpage, zenwebsite in addition to the gem? [Yn] ERROR: While executing gem ... (Gem::FilePermissionError) You don't have write permissions into the /usr/bin directory. 504 % gem -v 1.3.5 505 % gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.5 - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-10 - GEM PATHS: - /Library/Ruby/Gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://gems.rubyforge.org"] - REMOTE SOURCES: - http://gems.rubyforge.org ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27301&group_id=126 From noreply at rubyforge.org Fri Oct 16 15:54:20 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 16 Oct 2009 15:54:20 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27301 ] gem uninstall without sudo incorrectly reports success on OS X Message-ID: <20091016195420.15D6518582C9@rubyforge.org> Bugs item #27301, was opened at 2009-10-15 21:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27301&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Craig Walker (softcraft) Assigned to: Nobody (None) Summary: gem uninstall without sudo incorrectly reports success on OS X Initial Comment: On my system (OS X 10.5.8), uninstalling a gem without using "sudo" first causes gem to report that it uninstalled the gem. However, it does not do so; the gem remains intalled. I install gems using sudo; I get error messages if I forget it. Running with --debug shows plenty of permissions errors, but those aren't propagated up under normal circumstances. Attached is a copy of a gem session that shows the error and the pertinent info. Is this a widespread issue? If so, could it be fixed so that it correctly fails? Thanks, Craig Walker SoftCraft Development ---------------------------------------------------------------------- >Comment By: Craig Walker (softcraft) Date: 2009-10-16 13:54 Message: I have had other problems with Ruby so I would not be surprised if it was something specific to my machine. Is there anything I can do to debug it further? ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2009-10-16 13:27 Message: I'd have to guess that you or macports messed with your perms in some way, or macports patches rubygems? The only other difference I see is in GEM_PATH, so that is prolly easier to check first. I can't repro this at all: drwxr-xr-x 7 root admin 374 Aug 31 15:14 zenweb-2.18.1/ 503 % gem uninstall zenweb Remove executables: zenweb, zenwebpage, zenwebsite in addition to the gem? [Yn] ERROR: While executing gem ... (Gem::FilePermissionError) You don't have write permissions into the /usr/bin directory. 504 % gem -v 1.3.5 505 % gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.5 - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-10 - GEM PATHS: - /Library/Ruby/Gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://gems.rubyforge.org"] - REMOTE SOURCES: - http://gems.rubyforge.org ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27301&group_id=126 From noreply at rubyforge.org Mon Oct 19 13:49:21 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 19 Oct 2009 13:49:21 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Feature Requests-27318 ] weight spec.name when searching gem lib dirs for 'path' Message-ID: <20091019174921.2345B1588060@rubyforge.org> Feature Requests item #27318, was opened at 2009-10-19 11:49 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=27318&group_id=126 Category: local package management Group: None Status: Open Resolution: None Priority: 3 Submitted By: ara howard (ahoward) Assigned to: Nobody (None) Summary: weight spec.name when searching gem lib dirs for 'path' Initial Comment: gems has a *serious* issue in that someone structuring there gem like a_gem-1.2.3/lib/rails.rb will have there rails.rb loaded *before* the actual rails.rb when one does a require 'rails' this because the search through gem libdirs is sorted alpha/version wise with no concept of the semantics of the require statement. in fact, we know that users of rubygems mean to require the gem *named* rails when issuing the above. no gem user issues a normal require to pick up some random file from inside and arbitrary gem libdir. as such it makes sense to *prefer* file matches which exactly match the spec.name when searching. here is a patch, all tests that passed before (there was one failing) continue to pass with this patch: --- lib/rubygems/gem_path_searcher.rb.org 2009-10-19 11:37:13.000000000 -0600 +++ lib/rubygems/gem_path_searcher.rb 2009-10-19 11:46:26.000000000 -0600 @@ -30,8 +30,11 @@ # Return the _gemspec_ of the gem where it was found. If no match # is found, return nil. # - # The gems are searched in alphabetical order, and in reverse - # version order. + # The gems are searched in alphabetical order, and in reverse version order. + # If a path is found in more than one gem the gem with a spec.name == path + # is preferred over others - in otherwords main-3.0.3/lib/main.rb would be + # preferred over geonames-1.2.3/lib/main.rb if one issued a 'require "main"' + # - assuming main had spec.name=='main'. # # For example: # @@ -46,8 +49,18 @@ # only that there is a match. def find(path) - @gemspecs.find do |spec| matching_file? spec, path end + first_named = first = nil + @gemspecs.select do |spec| + if(matching_file?(spec, path)) + name = File.basename(path).sub(%r/\..*$/,'') + first ||= spec + first_named ||= spec if(spec.name == name) + end + break if(first_named and first) end + first_named or first + end + ## # Works like #find, but finds all gemspecs matching +path+. also see http://gist.github.com/213544 ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=27318&group_id=126 From aaron at tenderlovemaking.com Mon Oct 19 14:34:59 2009 From: aaron at tenderlovemaking.com (Aaron Patterson) Date: Mon, 19 Oct 2009 11:34:59 -0700 Subject: [Rubygems-developers] [ rubygems-Feature Requests-27318 ] weight spec.name when searching gem lib dirs for 'path' In-Reply-To: <20091019174921.2345B1588060@rubyforge.org> References: <20091019174921.2345B1588060@rubyforge.org> Message-ID: <4ADCB153.8010001@tenderlovemaking.com> noreply at rubyforge.org wrote: > Feature Requests item #27318, was opened at 2009-10-19 11:49 > You can respond by visiting: > http://rubyforge.org/tracker/?func=detail&atid=578&aid=27318&group_id=126 > > Category: local package management > Group: None > Status: Open > Resolution: None > Priority: 3 > Submitted By: ara howard (ahoward) > Assigned to: Nobody (None) > Summary: weight spec.name when searching gem lib dirs for 'path' > > Initial Comment: > gems has a *serious* issue in that someone structuring there gem like > > a_gem-1.2.3/lib/rails.rb > > will have there rails.rb loaded *before* the actual rails.rb when one does a > > require 'rails' > > this because the search through gem libdirs is sorted alpha/version wise with no concept of the semantics of the require statement. in fact, we know that users of rubygems mean to require the gem *named* rails when issuing the above. no gem user issues a normal require to pick up some random file from inside and arbitrary gem libdir. as such it makes sense to *prefer* file matches which exactly match the spec.name when searching. here is a patch, all tests that passed before (there was one failing) continue to pass with this patch: I don't think this is a problem rubygems necessarily needs to solve. As a library writer, why are you including a lib/rails.rb in your gem? Why not "lib/a_gem/rails.rb"? I wouldn't use a gem where the gem author didn't realize the implications of included a top-level rb file that conflicted with other gems. It seems like bad form. > --- lib/rubygems/gem_path_searcher.rb.org 2009-10-19 11:37:13.000000000 -0600 > +++ lib/rubygems/gem_path_searcher.rb 2009-10-19 11:46:26.000000000 -0600 > @@ -30,8 +30,11 @@ > # Return the _gemspec_ of the gem where it was found. If no match > # is found, return nil. > # > - # The gems are searched in alphabetical order, and in reverse > - # version order. > + # The gems are searched in alphabetical order, and in reverse version order. > + # If a path is found in more than one gem the gem with a spec.name == path > + # is preferred over others - in otherwords main-3.0.3/lib/main.rb would be > + # preferred over geonames-1.2.3/lib/main.rb if one issued a 'require "main"' > + # - assuming main had spec.name=='main'. > # > # For example: > # > @@ -46,8 +49,18 @@ > # only that there is a match. > > def find(path) > - @gemspecs.find do |spec| matching_file? spec, path end > + first_named = first = nil > + @gemspecs.select do |spec| > + if(matching_file?(spec, path)) > + name = File.basename(path).sub(%r/\..*$/,'') > + first ||= spec > + first_named ||= spec if(spec.name == name) > + end > + break if(first_named and first) > end > + first_named or first > + end > + > > ## > # Works like #find, but finds all gemspecs matching +path+. A patch with no tests? o_O -- Aaron Patterson http://tenderlovemaking.com/ From jbarnette at gmail.com Mon Oct 19 14:48:46 2009 From: jbarnette at gmail.com (John Barnette) Date: Mon, 19 Oct 2009 11:48:46 -0700 Subject: [Rubygems-developers] [ rubygems-Feature Requests-27318 ] weight spec.name when searching gem lib dirs for 'path' In-Reply-To: <4ADCB153.8010001@tenderlovemaking.com> References: <20091019174921.2345B1588060@rubyforge.org> <4ADCB153.8010001@tenderlovemaking.com> Message-ID: <2bce3eb60910191148g4a1ba9cev9151a29caf9b326a@mail.gmail.com> On Mon, Oct 19, 2009 at 11:34 AM, Aaron Patterson wrote: > I don't think this is a problem rubygems necessarily needs to solve. ?As > a library writer, why are you including a lib/rails.rb in your gem? ?Why > not "lib/a_gem/rails.rb"? Ara, do you have any examples of gems that are busted by the current behavior? I assume you've run in to a few. ~ j. From noreply at rubyforge.org Mon Oct 19 20:47:46 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 19 Oct 2009 20:47:46 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27228 ] gem which shell.rb fails Message-ID: <20091020004746.461B01858283@rubyforge.org> Bugs item #27228, was opened at 2009-10-03 05:29 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27228&group_id=126 Category: `gem` commands (other) Group: None >Status: Closed >Resolution: Rejected Priority: 3 Submitted By: Roger Pack (rogerdpack) >Assigned to: Eric Hodel (drbrain) Summary: gem which shell.rb fails Initial Comment: I believe the following is not expected (i.e. bug) C:\dev\blade_copy\digitalarchive_trunk>gem which shell.rb Can't find ruby library file or shared library shell.rb C:\dev\blade_copy\digitalarchive_trunk>gem which shell c:/ruby18/lib/ruby/1.8/shell.rb Thanks. -r ---------------------------------------------------------------------- >Comment By: Eric Hodel (drbrain) Date: 2009-10-19 17:47 Message: Since you don't necessarily know the extension of the file you would require, don't force it. (thread.rb vs. thread.so) ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27228&group_id=126 From jftucker at gmail.com Tue Oct 20 05:26:38 2009 From: jftucker at gmail.com (James Tucker) Date: Tue, 20 Oct 2009 10:26:38 +0100 Subject: [Rubygems-developers] [ rubygems-Feature Requests-27318 ] weight spec.name when searching gem lib dirs for 'path' In-Reply-To: <2bce3eb60910191148g4a1ba9cev9151a29caf9b326a@mail.gmail.com> References: <20091019174921.2345B1588060@rubyforge.org> <4ADCB153.8010001@tenderlovemaking.com> <2bce3eb60910191148g4a1ba9cev9151a29caf9b326a@mail.gmail.com> Message-ID: <6A820DD1-B2D7-4CC0-8747-86A7D0594232@gmail.com> On 19 Oct 2009, at 19:48, John Barnette wrote: > On Mon, Oct 19, 2009 at 11:34 AM, Aaron Patterson > wrote: >> I don't think this is a problem rubygems necessarily needs to >> solve. As >> a library writer, why are you including a lib/rails.rb in your >> gem? Why >> not "lib/a_gem/rails.rb"? > > Ara, do you have any examples of gems that are busted by the current > behavior? I assume you've run in to a few. I patched aasm not that long ago for this reason, it was conflicting with state_machine > > > ~ j. > _______________________________________________ > Rubygems-developers mailing list > http://rubyforge.org/projects/rubygems > Rubygems-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers From noreply at rubyforge.org Wed Oct 21 05:41:13 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Oct 2009 05:41:13 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27324 ] string contains null byte Message-ID: <20091021094113.F244A1D78831@rubyforge.org> Bugs item #27324, was opened at 2009-10-21 11:41 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27324&group_id=126 Category: `gem install` command Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Thomas Preymesser (thopre) Assigned to: Nobody (None) Summary: string contains null byte Initial Comment: Hello, i get this error when i try to install rails. Many other gems can be installed without problems. $ sudo gem install rails --backtrace ERROR: While executing gem ... (ArgumentError) string contains null byte /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader/entry.rb:66:in `join' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader/entry.rb:66:in `full_name' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:32:in `block in initialize' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader.rb:63:in `block in each' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader.rb:54:in `loop' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_reader.rb:54:in `each' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:31:in `initialize' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:16:in `new' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package/tar_input.rb:16:in `open' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/package.rb:56:in `open' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:67:in `from_io' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:51:in `block in from_file_by_path' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:50:in `open' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/format.rb:50:in `from_file_by_path' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/installer.rb:119:in `initialize' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:239:in `new' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:239:in `block in install' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:222:in `each' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/dependency_installer.rb:222:in `install' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/commands/install_command.rb:118:in `block in execute' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/commands/install_command.rb:115:in `each' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/commands/install_command.rb:115:in `execute' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command.rb:257:in `invoke' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:132:in `process_args' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:102:in `run' /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/gem_runner.rb:58:in `run' /usr/local/bin/gem:21:in `
' $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.5 - RUBY VERSION: 1.9.2 (2009-10-21 patchlevel -1) [i686-linux] - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.9.1 - RUBYGEMS PREFIX: /usr/local/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5 - RUBY EXECUTABLE: /usr/local/bin/ruby - EXECUTABLE DIRECTORY: /usr/local/bin - RUBYGEMS PLATFORMS: - ruby - x86-linux - GEM PATHS: - /usr/local/lib/ruby/gems/1.9.1 - /home/tp/.gem/ruby/1.9.1 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - :sources => ["http://gems.rubyforge.org/"] - "rdoc" => "--inline-source --line-numbers --format=html --template=hanna" - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27324&group_id=126 From noreply at rubyforge.org Wed Oct 21 05:43:18 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Oct 2009 05:43:18 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-26299 ] undefined method `each' for #< String:0xcb6e3e4> Message-ID: <20091021094318.17B091D78832@rubyforge.org> Bugs item #26299, was opened at 2009-06-20 20:50 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26299&group_id=126 Category: None Group: None >Status: Closed Resolution: None Priority: 3 Submitted By: Thomas Preymesser (thopre) Assigned to: Nobody (None) >Summary: undefined method `each' for #<String:0xcb6e3e4> Initial Comment: i get the following message at the installation of each gem with Ruby 1.9 Updating ri class cache with 7980 classes... ERROR: While executing gem ... (NoMethodError) undefined method `each' for # ---------------------------------------------------------------------- Comment By: Nick Hildebrant (nihildeb) Date: 2009-08-26 23:44 Message: close ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-06-30 01:14 Message: Hi, please follow the guidelines from the top of the "submit bug" page: Be sure to include the output of `gem env` with your bug report, and if the bug is a result of one of the `gem` commands, run with `gem -- debug thecommand` and include the full output. This will greatly help us in fixing your bug. Thanks. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=26299&group_id=126 From noreply at rubyforge.org Wed Oct 21 09:20:26 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Oct 2009 09:20:26 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27327 ] RubyGems does not work properly with upcomming Ruby 1.9.2 Message-ID: <20091021132026.5D628197827D@rubyforge.org> Bugs item #27327, was opened at 2009-10-21 15:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27327&group_id=126 Category: #gem and #require methods Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: V?t Ondruch (voxik) Assigned to: Nobody (None) Summary: RubyGems does not work properly with upcomming Ruby 1.9.2 Initial Comment: With ruby ruby 1.9.2dev (2009-10-07) [i386-mswin32_90], coming from win32-unicode-test branch, RubyGems does not work properly anymore. The problem is in initialization of system_config_path variable. The original code is: system_config_path = begin require 'Win32API' CSIDL_COMMON_APPDATA = 0x0023 path = 0.chr * 260 SHGetFolderPath = Win32API.new 'shell32', 'SHGetFolderPath', 'PLPLP', 'L', :stdcall SHGetFolderPath.call nil, CSIDL_COMMON_APPDATA, nil, 1, path path.strip rescue LoadError '/etc' end but it should be replaced by the following version: system_config_path = begin require 'Win32API' CSIDL_COMMON_APPDATA = 0x0023 path = 0.chr * 260 SHGetFolderPath = Win32API.new 'shell32', 'SHGetFolderPathW', 'PLPLP', 'L', :stdcall SHGetFolderPath.call nil, CSIDL_COMMON_APPDATA, nil, 1, path path.force_encoding('UTF-16LE').encode!('UTF-8') path.strip rescue LoadError '/etc' end i.e. the wide version of SHGetFolderPath should be used. However this code should be probably specific for specific Ruby versions. The problem can be reproduced for example on czech windows XP, where the method SHGetFolderPath returns following string: "c:\Documents and Settings\All Users\Data aplikac?" ("c:\Documents and Settings\All Users\Application data" in EN windows), with US-ASCII encoding, which is completely wrong. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27327&group_id=126 From noreply at rubyforge.org Wed Oct 21 10:52:54 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Oct 2009 10:52:54 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27327 ] RubyGems does not work properly with upcomming Ruby 1.9.2 Message-ID: <20091021145254.EF8ED1D78847@rubyforge.org> Bugs item #27327, was opened at 2009-10-21 10:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27327&group_id=126 Category: #gem and #require methods Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: V?t Ondruch (voxik) Assigned to: Nobody (None) Summary: RubyGems does not work properly with upcomming Ruby 1.9.2 Initial Comment: With ruby ruby 1.9.2dev (2009-10-07) [i386-mswin32_90], coming from win32-unicode-test branch, RubyGems does not work properly anymore. The problem is in initialization of system_config_path variable. The original code is: system_config_path = begin require 'Win32API' CSIDL_COMMON_APPDATA = 0x0023 path = 0.chr * 260 SHGetFolderPath = Win32API.new 'shell32', 'SHGetFolderPath', 'PLPLP', 'L', :stdcall SHGetFolderPath.call nil, CSIDL_COMMON_APPDATA, nil, 1, path path.strip rescue LoadError '/etc' end but it should be replaced by the following version: system_config_path = begin require 'Win32API' CSIDL_COMMON_APPDATA = 0x0023 path = 0.chr * 260 SHGetFolderPath = Win32API.new 'shell32', 'SHGetFolderPathW', 'PLPLP', 'L', :stdcall SHGetFolderPath.call nil, CSIDL_COMMON_APPDATA, nil, 1, path path.force_encoding('UTF-16LE').encode!('UTF-8') path.strip rescue LoadError '/etc' end i.e. the wide version of SHGetFolderPath should be used. However this code should be probably specific for specific Ruby versions. The problem can be reproduced for example on czech windows XP, where the method SHGetFolderPath returns following string: "c:\Documents and Settings\All Users\Data aplikac?" ("c:\Documents and Settings\All Users\Application data" in EN windows), with US-ASCII encoding, which is completely wrong. ---------------------------------------------------------------------- >Comment By: Luis Lavena (luislavena) Date: 2009-10-21 11:52 Message: You're correct. We can't implement Wide characters API as Ruby 1.8 do not support encoding in the same way 1.9 does. A workaround will be use Win32API completely for the encoding translation, but I'm having hard time finding that right now. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27327&group_id=126 From noreply at rubyforge.org Wed Oct 21 12:48:29 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Oct 2009 12:48:29 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-22617 ] Gem.loaded_specs does not work on 1.9 Message-ID: <20091021164829.D87981D78851@rubyforge.org> Bugs item #22617, was opened at 2008-10-30 17:32 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=22617&group_id=126 Category: other Group: v1.3.x Status: Open Resolution: Accepted Priority: 3 Submitted By: Paul Brannan (cout) Assigned to: Eric Hodel (drbrain) Summary: Gem.loaded_specs does not work on 1.9 Initial Comment: The loaded_specs attribute seems to always be empty on 1.9: [pbrannan at zem ruby]$ ruby -rubygems -e 'gem("ruby-prof"); p Gem.loaded_specs' {"ruby-prof"=>#=", #]]>, @version=#, @files=["Rakefile", "README", "LICENSE", "CHANGES", "bin/ruby-prof", "lib/ruby-prof", "lib/ruby-prof.rb", "lib/unprof.rb", "lib/ruby-prof/abstract_printer.rb", "lib/ruby-prof/call_tree_printer.rb", "lib/ruby-prof/call_tree_printer.rb.rej", "lib/ruby-prof/flat_printer.rb", "lib/ruby-prof/graph_html_printer.rb", "lib/ruby-prof/graph_printer.rb", "lib/ruby-prof/profile_test_case.rb", "lib/ruby-prof/task.rb", "rails_plugin/ruby-prof", "rails_plugin/ruby-prof/init.rb", "rails_plugin/ruby-prof/lib", "rails_plugin/ruby-prof/lib/profiling.rb", "examples/flat.txt", "examples/graph.html", "examples/graph.txt", "ext/extconf.rb", "ext/extconf.rb.rej", "ext/measure_allocations.h", "ext/measure_cpu_time.h", "ext/measure_memory.h", "ext/measure_process_time.h", "ext/measure_wall_time.h", "ext/ruby_prof.c", "test/basic_test.rb", "test/duplicate_names_test.rb", "test/line_number_test.rb", "test/measure_mode_test.rb", "test/module_test.rb", "test/no_method_class_test.rb", "test/prime.rb", "test/prime1.rb", "test/prime2.rb", "test/prime3.rb", "test/prime_test.rb", "test/printers_test.rb", "test/profile_unit_test.rb", "test/recursive_test.rb", "test/singleton_test.rb", "test/start_test.rb", "test/test_helper.rb", "test/test_suite.rb", "test/thread_test.rb", "test/timing_test.rb"], @has_rdoc=true, @specification_version=2, @loaded=true, @requirements=[], @signing_key=nil, @default_executable="ruby-prof", @email="shugo at ruby-lang.org and cfis at savagexi.com", @required_ruby_version=#=", #]]>, @rdoc_options=["--title", "ruby-prof", "--inline-source", "--line-numbers", "--main", "README"], @bindir="bin", @rubygems_version="1.2.0", @homepage="http://rubyforge.org/projects/ruby-prof/", @name="ruby-prof", @platform="ruby", @autorequire=nil, @rubyforge_project="ruby-prof", @extensions=["ext/extconf.rb"], @summary="Fast Ruby profiler", @loaded_from="/usr/local/lib/ruby/gems/1.8/specifications/ruby-prof-0.6.0.gemspec", @original_platform=nil, @post_install_message=nil, @description="ruby-prof is a fast code profiler for Ruby. It is a C extension and therefore is many times faster than the standard Ruby profiler. It supports both flat and graph profiles. For each method, graph profiles show how long the method ran, which methods called it and which methods it called. RubyProf generate both text and html and can output it to standard out or to a file.", @dependencies=[], @test_files=["test/test_helper.rb", "test/test_suite.rb"], @require_paths=["bin", "lib"]>} [pbrannan at zem ruby]$ ruby1.9 -rubygems -e 'gem("ruby-prof"); p Gem.loaded_specs' /usr/local/lib/ruby/gems/1.9.0/gems/rubygems-update-1.3.1/lib/rubygems/config_file.rb:7: warning: mismatched indentations: line 216:'def' and line 218:'end' /usr/local/lib/ruby/gems/1.9.0/gems/rubygems-update-1.3.1/lib/rubygems/config_file.rb:7: warning: mismatched indentations: line 231:'def' and line 233:'end' /usr/local/lib/ruby/gems/1.9.0/gems/rubygems-update-1.3.1/lib/rubygems/config_file.rb:7: warning: mismatched indentations: line 246:'def' and line 248:'end' /usr/local/lib/ruby/gems/1.9.0/gems/rubygems-update-1.3.1/lib/rubygems/config_file.rb:7: warning: mismatched indentations: line 261:'def' and line 263:'end' {} ---------------------------------------------------------------------- Comment By: Nikolai Weibull (pcp) Date: 2009-10-21 18:48 Message: This is still the case on Windows 1.9.1-p243. By extension, Config.datadir, which is what I care about, doesn?t work. I don?t want to sound whiny, but I can?t see how this can have gone unfixed for close to a year now. It seems like a rather central concept. ---------------------------------------------------------------------- Comment By: Matt Hulse (mhulse) Date: 2009-08-05 01:27 Message: Yes, this is still happening in 1.9.1-p129. I'm on WinXP Pro using the mingw32 build from rubyinstaller.org/downloads. I just updated to rubygems 1.3.5 using gem update --system and Gem.loaded_specs is still empty until I call gem('') or gem('nokogiri') (the gem I'm looking for). ---------------------------------------------------------------------- Comment By: Joeri Samson (joeri) Date: 2009-03-29 20:42 Message: with 1.9.1p0 and rubygems 1.3.1 I get the same error as Eric Hodel, except if I print/access Gem.loaded_specs before calling gem "rake": joeri at alpha ~ $ ruby19 -rubygems -e 'p Gem.loaded_specs; gem("rake"); p Gem.loaded_specs' {} {"rake"=>#, @summary="Ruby based make-like utility.", @email="jim at weirichhouse.org", @homepage="http://rake.rubyforge.org", @rubyforge_project="rake", @description="Rake is a Make-like program implemented in Ruby. Tasks and dependencies are specified in standard Ruby syntax.", @autorequire=nil, @default_executable="rake", @signing_key=nil, @post_install_message=nil, @original_platform=nil, @rubygems_version="1.3.1", @specification_version=2, @date=2009-03-04 00:00:00 +0100, @require_paths=["bin", "lib"], @bindir="bin", @has_rdoc=true, @required_ruby_version=#=", #]], @version=nil>, @required_rubygems_version=#=", #]], @version=nil>, @platform="ruby", @cert_chain=[], @authors=["Jim Weirich"], @files=["install.rb", "CHANGES", "MIT-LICENSE", "Rakefile", "README", "TODO", "bin/rake", "lib/rake/classic_namespace.rb", "lib/rake/clean.rb", "lib/rake/contrib/compositepublisher.rb", "lib/rake/contrib/ftptools.rb", "lib/rake/contrib/publisher.rb", "lib/rake/contrib/rubyforgepublisher.rb", "lib/rake/contrib/sshpublisher.rb", "lib/rake/contrib/sys.rb", "lib/rake/gempackagetask.rb", "lib/rake/loaders/makefile.rb", "lib/rake/packagetask.rb", "lib/rake/rake_test_loader.rb", "lib/rake/rdoctask.rb", "lib/rake/repaired_system.rb", "lib/rake/ruby182_test_unit_fix.rb", "lib/rake/runtest.rb", "lib/rake/tasklib.rb", "lib/rake/testtask.rb", "lib/rake/win32.rb", "lib/rake.rb", "test/capture_stdout.rb", "test/check_expansion.rb", "test/contrib/test_sys.rb", "test/data/rakelib/test1.rb", "test/data/rbext/rakefile.rb", "test/filecreation.rb", "test/functional.rb", "test/in_environment.rb", "test/rake_test_setup.rb", "test/reqfile.rb", "test/reqfile2.rb", "test/session_functional.rb", "test/shellcommand.rb", "test/test_application.rb", "test/test_clean.rb", "test/test_definitions.rb", "test/test_earlytime.rb", "test/test_extension.rb", "test/test_file_creation_task.rb", "test/test_file_task.rb", "test/test_filelist.rb", "test/test_fileutils.rb", "test/test_ftp.rb", "test/test_invocation_chain.rb", "test/test_makefile_loader.rb", "test/test_multitask.rb", "test/test_namespace.rb", "test/test_package_task.rb", "test/test_pathmap.rb", "test/test_rake.rb", "test/test_rdoc_task.rb", "test/test_require.rb", "test/test_rules.rb", "test/test_task_arguments.rb", "test/test_task_manager.rb", "test/test_tasklib.rb", "test/test_tasks.rb", "test/test_test_task.rb", "test/test_top_level_functions.rb", "test/test_win32.rb", "test/data/imports/deps.mf", "test/data/sample.mf", "test/data/chains/Rakefile", "test/data/default/Rakefile", "test/data/dryrun/Rakefile", "test/data/file_creation_task/Rakefile", "test/data/imports/Rakefile", "test/data/multidesc/Rakefile", "test/data/namespace/Rakefile", "test/data/statusreturn/Rakefile", "test/data/unittest/Rakefile", "test/data/unittest/subdir", "doc/command_line_usage.rdoc", "doc/example", "doc/example/a.c", "doc/example/b.c", "doc/example/main.c", "doc/example/Rakefile1", "doc/example/Rakefile2", "doc/glossary.rdoc", "doc/jamis.rb", "doc/proto_rake.rdoc", "doc/rake.1.gz", "doc/rakefile.rdoc", "doc/rational.rdoc", "doc/release_notes", "doc/release_notes/rake-0.4.14.rdoc", "doc/release_notes/rake-0.4.15.rdoc", "doc/release_notes/rake-0.5.0.rdoc", "doc/release_notes/rake-0.5.3.rdoc", "doc/release_notes/rake-0.5.4.rdoc", "doc/release_notes/rake-0.6.0.rdoc", "doc/release_notes/rake-0.7.0.rdoc", "doc/release_notes/rake-0.7.1.rdoc", "doc/release_notes/rake-0.7.2.rdoc", "doc/release_notes/rake-0.7.3.rdoc", "doc/release_notes/rake-0.8.0.rdoc", "doc/release_notes/rake-0.8.2.rdoc", "doc/release_notes/rake-0.8.3.rdoc", "doc/release_notes/rake-0.8.4.rdoc"], @test_files=[], @rdoc_options=["--line-numbers", "--inline-source", "--main", "README", "--title", "Rake -- Ruby Make"], @extra_rdoc_files=["README", "MIT-LICENSE", "TODO", "CHANGES", "doc/command_line_usage.rdoc", "doc/glossary.rdoc", "doc/proto_rake.rdoc", "doc/rakefile.rdoc", "doc/rational.rdoc", "doc/release_notes/rake-0.4.14.rdoc", "doc/release_notes/rake-0.4.15.rdoc", "doc/release_notes/rake-0.5.0.rdoc", "doc/release_notes/rake-0.5.3.rdoc", "doc/release_notes/rake-0.5.4.rdoc", "doc/release_notes/rake-0.6.0.rdoc", "doc/release_notes/rake-0.7.0.rdoc", "doc/release_notes/rake-0.7.1.rdoc", "doc/release_notes/rake-0.7.2.rdoc", "doc/release_notes/rake-0.7.3.rdoc", "doc/release_notes/rake-0.8.0.rdoc", "doc/release_notes/rake-0.8.2.rdoc", "doc/release_notes/rake-0.8.3.rdoc", "doc/release_notes/rake-0.8.4.rdoc"], @executables=["rake"], @extensions=[], @requirements=[], @dependencies=[], @loaded=true, @loaded_from="/home/joeri/.gem/ruby/1.9.1/specifications/rake-0.8.4.gemspec">} ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-03-27 22:29 Message: With 1.9.1p0 and 1.9.2dev I see: $ ruby19 -v -rubygems -e 'gem "rake"; p Gem.loaded_specs' ruby 1.9.2dev (2009-03-28 trunk 23085) [i386-darwin9.6.0] :234:in `push_gem_version_on_load_path': Could not find RubyGem rake (>= 0) (Gem::LoadError) from :14:in `gem' from -e:1:in `
' This will take a bit more work than I planned for 1.3.1, and may require changes to gem_prelude :/ ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-03-16 11:50 Message: Ah, no, I hit .activate, which hits source_index. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-03-16 11:48 Message: works for me ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-01-02 16:59 Message: Is this still happening in 1.9.1? ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=22617&group_id=126 From noreply at rubyforge.org Wed Oct 21 12:52:05 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Oct 2009 12:52:05 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27327 ] RubyGems does not work properly with upcomming Ruby 1.9.2 Message-ID: <20091021165205.67C1118582C3@rubyforge.org> Bugs item #27327, was opened at 2009-10-21 15:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27327&group_id=126 Category: #gem and #require methods Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: V?t Ondruch (voxik) Assigned to: Nobody (None) Summary: RubyGems does not work properly with upcomming Ruby 1.9.2 Initial Comment: With ruby ruby 1.9.2dev (2009-10-07) [i386-mswin32_90], coming from win32-unicode-test branch, RubyGems does not work properly anymore. The problem is in initialization of system_config_path variable. The original code is: system_config_path = begin require 'Win32API' CSIDL_COMMON_APPDATA = 0x0023 path = 0.chr * 260 SHGetFolderPath = Win32API.new 'shell32', 'SHGetFolderPath', 'PLPLP', 'L', :stdcall SHGetFolderPath.call nil, CSIDL_COMMON_APPDATA, nil, 1, path path.strip rescue LoadError '/etc' end but it should be replaced by the following version: system_config_path = begin require 'Win32API' CSIDL_COMMON_APPDATA = 0x0023 path = 0.chr * 260 SHGetFolderPath = Win32API.new 'shell32', 'SHGetFolderPathW', 'PLPLP', 'L', :stdcall SHGetFolderPath.call nil, CSIDL_COMMON_APPDATA, nil, 1, path path.force_encoding('UTF-16LE').encode!('UTF-8') path.strip rescue LoadError '/etc' end i.e. the wide version of SHGetFolderPath should be used. However this code should be probably specific for specific Ruby versions. The problem can be reproduced for example on czech windows XP, where the method SHGetFolderPath returns following string: "c:\Documents and Settings\All Users\Data aplikac?" ("c:\Documents and Settings\All Users\Application data" in EN windows), with US-ASCII encoding, which is completely wrong. ---------------------------------------------------------------------- Comment By: Nikolai Weibull (pcp) Date: 2009-10-21 18:52 Message: Also, use dl instead of Win32API, as Win32API is deprecated. And Luis, why not have one case for 1.8 and one for 1.9 here? ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-10-21 16:52 Message: You're correct. We can't implement Wide characters API as Ruby 1.8 do not support encoding in the same way 1.9 does. A workaround will be use Win32API completely for the encoding translation, but I'm having hard time finding that right now. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27327&group_id=126 From noreply at rubyforge.org Wed Oct 21 13:00:36 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Oct 2009 13:00:36 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-22617 ] Gem.loaded_specs does not work on 1.9 Message-ID: <20091021170036.D9C8D1D78847@rubyforge.org> Bugs item #22617, was opened at 2008-10-30 13:32 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=22617&group_id=126 Category: other Group: v1.3.x Status: Open Resolution: Accepted Priority: 3 Submitted By: Paul Brannan (cout) Assigned to: Eric Hodel (drbrain) Summary: Gem.loaded_specs does not work on 1.9 Initial Comment: The loaded_specs attribute seems to always be empty on 1.9: [pbrannan at zem ruby]$ ruby -rubygems -e 'gem("ruby-prof"); p Gem.loaded_specs' {"ruby-prof"=>#=", #]]>, @version=#, @files=["Rakefile", "README", "LICENSE", "CHANGES", "bin/ruby-prof", "lib/ruby-prof", "lib/ruby-prof.rb", "lib/unprof.rb", "lib/ruby-prof/abstract_printer.rb", "lib/ruby-prof/call_tree_printer.rb", "lib/ruby-prof/call_tree_printer.rb.rej", "lib/ruby-prof/flat_printer.rb", "lib/ruby-prof/graph_html_printer.rb", "lib/ruby-prof/graph_printer.rb", "lib/ruby-prof/profile_test_case.rb", "lib/ruby-prof/task.rb", "rails_plugin/ruby-prof", "rails_plugin/ruby-prof/init.rb", "rails_plugin/ruby-prof/lib", "rails_plugin/ruby-prof/lib/profiling.rb", "examples/flat.txt", "examples/graph.html", "examples/graph.txt", "ext/extconf.rb", "ext/extconf.rb.rej", "ext/measure_allocations.h", "ext/measure_cpu_time.h", "ext/measure_memory.h", "ext/measure_process_time.h", "ext/measure_wall_time.h", "ext/ruby_prof.c", "test/basic_test.rb", "test/duplicate_names_test.rb", "test/line_number_test.rb", "test/measure_mode_test.rb", "test/module_test.rb", "test/no_method_class_test.rb", "test/prime.rb", "test/prime1.rb", "test/prime2.rb", "test/prime3.rb", "test/prime_test.rb", "test/printers_test.rb", "test/profile_unit_test.rb", "test/recursive_test.rb", "test/singleton_test.rb", "test/start_test.rb", "test/test_helper.rb", "test/test_suite.rb", "test/thread_test.rb", "test/timing_test.rb"], @has_rdoc=true, @specification_version=2, @loaded=true, @requirements=[], @signing_key=nil, @default_executable="ruby-prof", @email="shugo at ruby-lang.org and cfis at savagexi.com", @required_ruby_version=#=", #]]>, @rdoc_options=["--title", "ruby-prof", "--inline-source", "--line-numbers", "--main", "README"], @bindir="bin", @rubygems_version="1.2.0", @homepage="http://rubyforge.org/projects/ruby-prof/", @name="ruby-prof", @platform="ruby", @autorequire=nil, @rubyforge_project="ruby-prof", @extensions=["ext/extconf.rb"], @summary="Fast Ruby profiler", @loaded_from="/usr/local/lib/ruby/gems/1.8/specifications/ruby-prof-0.6.0.gemspec", @original_platform=nil, @post_install_message=nil, @description="ruby-prof is a fast code profiler for Ruby. It is a C extension and therefore is many times faster than the standard Ruby profiler. It supports both flat and graph profiles. For each method, graph profiles show how long the method ran, which methods called it and which methods it called. RubyProf generate both text and html and can output it to standard out or to a file.", @dependencies=[], @test_files=["test/test_helper.rb", "test/test_suite.rb"], @require_paths=["bin", "lib"]>} [pbrannan at zem ruby]$ ruby1.9 -rubygems -e 'gem("ruby-prof"); p Gem.loaded_specs' /usr/local/lib/ruby/gems/1.9.0/gems/rubygems-update-1.3.1/lib/rubygems/config_file.rb:7: warning: mismatched indentations: line 216:'def' and line 218:'end' /usr/local/lib/ruby/gems/1.9.0/gems/rubygems-update-1.3.1/lib/rubygems/config_file.rb:7: warning: mismatched indentations: line 231:'def' and line 233:'end' /usr/local/lib/ruby/gems/1.9.0/gems/rubygems-update-1.3.1/lib/rubygems/config_file.rb:7: warning: mismatched indentations: line 246:'def' and line 248:'end' /usr/local/lib/ruby/gems/1.9.0/gems/rubygems-update-1.3.1/lib/rubygems/config_file.rb:7: warning: mismatched indentations: line 261:'def' and line 263:'end' {} ---------------------------------------------------------------------- >Comment By: Luis Lavena (luislavena) Date: 2009-10-21 14:00 Message: Whiny you sound, patches are welcome too :-) ---------------------------------------------------------------------- Comment By: Nikolai Weibull (pcp) Date: 2009-10-21 13:48 Message: This is still the case on Windows 1.9.1-p243. By extension, Config.datadir, which is what I care about, doesn?t work. I don?t want to sound whiny, but I can?t see how this can have gone unfixed for close to a year now. It seems like a rather central concept. ---------------------------------------------------------------------- Comment By: Matt Hulse (mhulse) Date: 2009-08-04 20:27 Message: Yes, this is still happening in 1.9.1-p129. I'm on WinXP Pro using the mingw32 build from rubyinstaller.org/downloads. I just updated to rubygems 1.3.5 using gem update --system and Gem.loaded_specs is still empty until I call gem('') or gem('nokogiri') (the gem I'm looking for). ---------------------------------------------------------------------- Comment By: Joeri Samson (joeri) Date: 2009-03-29 15:42 Message: with 1.9.1p0 and rubygems 1.3.1 I get the same error as Eric Hodel, except if I print/access Gem.loaded_specs before calling gem "rake": joeri at alpha ~ $ ruby19 -rubygems -e 'p Gem.loaded_specs; gem("rake"); p Gem.loaded_specs' {} {"rake"=>#, @summary="Ruby based make-like utility.", @email="jim at weirichhouse.org", @homepage="http://rake.rubyforge.org", @rubyforge_project="rake", @description="Rake is a Make-like program implemented in Ruby. Tasks and dependencies are specified in standard Ruby syntax.", @autorequire=nil, @default_executable="rake", @signing_key=nil, @post_install_message=nil, @original_platform=nil, @rubygems_version="1.3.1", @specification_version=2, @date=2009-03-04 00:00:00 +0100, @require_paths=["bin", "lib"], @bindir="bin", @has_rdoc=true, @required_ruby_version=#=", #]], @version=nil>, @required_rubygems_version=#=", #]], @version=nil>, @platform="ruby", @cert_chain=[], @authors=["Jim Weirich"], @files=["install.rb", "CHANGES", "MIT-LICENSE", "Rakefile", "README", "TODO", "bin/rake", "lib/rake/classic_namespace.rb", "lib/rake/clean.rb", "lib/rake/contrib/compositepublisher.rb", "lib/rake/contrib/ftptools.rb", "lib/rake/contrib/publisher.rb", "lib/rake/contrib/rubyforgepublisher.rb", "lib/rake/contrib/sshpublisher.rb", "lib/rake/contrib/sys.rb", "lib/rake/gempackagetask.rb", "lib/rake/loaders/makefile.rb", "lib/rake/packagetask.rb", "lib/rake/rake_test_loader.rb", "lib/rake/rdoctask.rb", "lib/rake/repaired_system.rb", "lib/rake/ruby182_test_unit_fix.rb", "lib/rake/runtest.rb", "lib/rake/tasklib.rb", "lib/rake/testtask.rb", "lib/rake/win32.rb", "lib/rake.rb", "test/capture_stdout.rb", "test/check_expansion.rb", "test/contrib/test_sys.rb", "test/data/rakelib/test1.rb", "test/data/rbext/rakefile.rb", "test/filecreation.rb", "test/functional.rb", "test/in_environment.rb", "test/rake_test_setup.rb", "test/reqfile.rb", "test/reqfile2.rb", "test/session_functional.rb", "test/shellcommand.rb", "test/test_application.rb", "test/test_clean.rb", "test/test_definitions.rb", "test/test_earlytime.rb", "test/test_extension.rb", "test/test_file_creation_task.rb", "test/test_file_task.rb", "test/test_filelist.rb", "test/test_fileutils.rb", "test/test_ftp.rb", "test/test_invocation_chain.rb", "test/test_makefile_loader.rb", "test/test_multitask.rb", "test/test_namespace.rb", "test/test_package_task.rb", "test/test_pathmap.rb", "test/test_rake.rb", "test/test_rdoc_task.rb", "test/test_require.rb", "test/test_rules.rb", "test/test_task_arguments.rb", "test/test_task_manager.rb", "test/test_tasklib.rb", "test/test_tasks.rb", "test/test_test_task.rb", "test/test_top_level_functions.rb", "test/test_win32.rb", "test/data/imports/deps.mf", "test/data/sample.mf", "test/data/chains/Rakefile", "test/data/default/Rakefile", "test/data/dryrun/Rakefile", "test/data/file_creation_task/Rakefile", "test/data/imports/Rakefile", "test/data/multidesc/Rakefile", "test/data/namespace/Rakefile", "test/data/statusreturn/Rakefile", "test/data/unittest/Rakefile", "test/data/unittest/subdir", "doc/command_line_usage.rdoc", "doc/example", "doc/example/a.c", "doc/example/b.c", "doc/example/main.c", "doc/example/Rakefile1", "doc/example/Rakefile2", "doc/glossary.rdoc", "doc/jamis.rb", "doc/proto_rake.rdoc", "doc/rake.1.gz", "doc/rakefile.rdoc", "doc/rational.rdoc", "doc/release_notes", "doc/release_notes/rake-0.4.14.rdoc", "doc/release_notes/rake-0.4.15.rdoc", "doc/release_notes/rake-0.5.0.rdoc", "doc/release_notes/rake-0.5.3.rdoc", "doc/release_notes/rake-0.5.4.rdoc", "doc/release_notes/rake-0.6.0.rdoc", "doc/release_notes/rake-0.7.0.rdoc", "doc/release_notes/rake-0.7.1.rdoc", "doc/release_notes/rake-0.7.2.rdoc", "doc/release_notes/rake-0.7.3.rdoc", "doc/release_notes/rake-0.8.0.rdoc", "doc/release_notes/rake-0.8.2.rdoc", "doc/release_notes/rake-0.8.3.rdoc", "doc/release_notes/rake-0.8.4.rdoc"], @test_files=[], @rdoc_options=["--line-numbers", "--inline-source", "--main", "README", "--title", "Rake -- Ruby Make"], @extra_rdoc_files=["README", "MIT-LICENSE", "TODO", "CHANGES", "doc/command_line_usage.rdoc", "doc/glossary.rdoc", "doc/proto_rake.rdoc", "doc/rakefile.rdoc", "doc/rational.rdoc", "doc/release_notes/rake-0.4.14.rdoc", "doc/release_notes/rake-0.4.15.rdoc", "doc/release_notes/rake-0.5.0.rdoc", "doc/release_notes/rake-0.5.3.rdoc", "doc/release_notes/rake-0.5.4.rdoc", "doc/release_notes/rake-0.6.0.rdoc", "doc/release_notes/rake-0.7.0.rdoc", "doc/release_notes/rake-0.7.1.rdoc", "doc/release_notes/rake-0.7.2.rdoc", "doc/release_notes/rake-0.7.3.rdoc", "doc/release_notes/rake-0.8.0.rdoc", "doc/release_notes/rake-0.8.2.rdoc", "doc/release_notes/rake-0.8.3.rdoc", "doc/release_notes/rake-0.8.4.rdoc"], @executables=["rake"], @extensions=[], @requirements=[], @dependencies=[], @loaded=true, @loaded_from="/home/joeri/.gem/ruby/1.9.1/specifications/rake-0.8.4.gemspec">} ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-03-27 18:29 Message: With 1.9.1p0 and 1.9.2dev I see: $ ruby19 -v -rubygems -e 'gem "rake"; p Gem.loaded_specs' ruby 1.9.2dev (2009-03-28 trunk 23085) [i386-darwin9.6.0] :234:in `push_gem_version_on_load_path': Could not find RubyGem rake (>= 0) (Gem::LoadError) from :14:in `gem' from -e:1:in `
' This will take a bit more work than I planned for 1.3.1, and may require changes to gem_prelude :/ ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-03-16 07:50 Message: Ah, no, I hit .activate, which hits source_index. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-03-16 07:48 Message: works for me ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-01-02 12:59 Message: Is this still happening in 1.9.1? ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=22617&group_id=126 From noreply at rubyforge.org Wed Oct 21 13:08:59 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Oct 2009 13:08:59 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27327 ] RubyGems does not work properly with upcomming Ruby 1.9.2 Message-ID: <20091021170859.5FCEA1D78847@rubyforge.org> Bugs item #27327, was opened at 2009-10-21 15:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27327&group_id=126 Category: #gem and #require methods Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: V?t Ondruch (voxik) Assigned to: Nobody (None) Summary: RubyGems does not work properly with upcomming Ruby 1.9.2 Initial Comment: With ruby ruby 1.9.2dev (2009-10-07) [i386-mswin32_90], coming from win32-unicode-test branch, RubyGems does not work properly anymore. The problem is in initialization of system_config_path variable. The original code is: system_config_path = begin require 'Win32API' CSIDL_COMMON_APPDATA = 0x0023 path = 0.chr * 260 SHGetFolderPath = Win32API.new 'shell32', 'SHGetFolderPath', 'PLPLP', 'L', :stdcall SHGetFolderPath.call nil, CSIDL_COMMON_APPDATA, nil, 1, path path.strip rescue LoadError '/etc' end but it should be replaced by the following version: system_config_path = begin require 'Win32API' CSIDL_COMMON_APPDATA = 0x0023 path = 0.chr * 260 SHGetFolderPath = Win32API.new 'shell32', 'SHGetFolderPathW', 'PLPLP', 'L', :stdcall SHGetFolderPath.call nil, CSIDL_COMMON_APPDATA, nil, 1, path path.force_encoding('UTF-16LE').encode!('UTF-8') path.strip rescue LoadError '/etc' end i.e. the wide version of SHGetFolderPath should be used. However this code should be probably specific for specific Ruby versions. The problem can be reproduced for example on czech windows XP, where the method SHGetFolderPath returns following string: "c:\Documents and Settings\All Users\Data aplikac?" ("c:\Documents and Settings\All Users\Application data" in EN windows), with US-ASCII encoding, which is completely wrong. ---------------------------------------------------------------------- >Comment By: V?t Ondruch (voxik) Date: 2009-10-21 19:08 Message: > And Luis, why not have one case for 1.8 and one for 1.9 here? I agree with that, why not? ---------------------------------------------------------------------- Comment By: Nikolai Weibull (pcp) Date: 2009-10-21 18:52 Message: Also, use dl instead of Win32API, as Win32API is deprecated. And Luis, why not have one case for 1.8 and one for 1.9 here? ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-10-21 16:52 Message: You're correct. We can't implement Wide characters API as Ruby 1.8 do not support encoding in the same way 1.9 does. A workaround will be use Win32API completely for the encoding translation, but I'm having hard time finding that right now. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27327&group_id=126 From noreply at rubyforge.org Wed Oct 21 13:12:08 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Oct 2009 13:12:08 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27327 ] RubyGems does not work properly with upcomming Ruby 1.9.2 Message-ID: <20091021171208.27B321D78847@rubyforge.org> Bugs item #27327, was opened at 2009-10-21 10:20 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27327&group_id=126 Category: #gem and #require methods Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: V?t Ondruch (voxik) Assigned to: Nobody (None) Summary: RubyGems does not work properly with upcomming Ruby 1.9.2 Initial Comment: With ruby ruby 1.9.2dev (2009-10-07) [i386-mswin32_90], coming from win32-unicode-test branch, RubyGems does not work properly anymore. The problem is in initialization of system_config_path variable. The original code is: system_config_path = begin require 'Win32API' CSIDL_COMMON_APPDATA = 0x0023 path = 0.chr * 260 SHGetFolderPath = Win32API.new 'shell32', 'SHGetFolderPath', 'PLPLP', 'L', :stdcall SHGetFolderPath.call nil, CSIDL_COMMON_APPDATA, nil, 1, path path.strip rescue LoadError '/etc' end but it should be replaced by the following version: system_config_path = begin require 'Win32API' CSIDL_COMMON_APPDATA = 0x0023 path = 0.chr * 260 SHGetFolderPath = Win32API.new 'shell32', 'SHGetFolderPathW', 'PLPLP', 'L', :stdcall SHGetFolderPath.call nil, CSIDL_COMMON_APPDATA, nil, 1, path path.force_encoding('UTF-16LE').encode!('UTF-8') path.strip rescue LoadError '/etc' end i.e. the wide version of SHGetFolderPath should be used. However this code should be probably specific for specific Ruby versions. The problem can be reproduced for example on czech windows XP, where the method SHGetFolderPath returns following string: "c:\Documents and Settings\All Users\Data aplikac?" ("c:\Documents and Settings\All Users\Application data" in EN windows), with US-ASCII encoding, which is completely wrong. ---------------------------------------------------------------------- >Comment By: Luis Lavena (luislavena) Date: 2009-10-21 14:12 Message: Not as easy at you make it look like Win32API is going to be deprecated at 1.9.2 By that time, all should have switched to DL. DL doesn't work with x86_64, at least not for my Windows. There still lot of pieces in Ruby stdlib that depend on Win32API that need to switch to DL. ---------------------------------------------------------------------- Comment By: V?t Ondruch (voxik) Date: 2009-10-21 14:08 Message: > And Luis, why not have one case for 1.8 and one for 1.9 here? I agree with that, why not? ---------------------------------------------------------------------- Comment By: Nikolai Weibull (pcp) Date: 2009-10-21 13:52 Message: Also, use dl instead of Win32API, as Win32API is deprecated. And Luis, why not have one case for 1.8 and one for 1.9 here? ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-10-21 11:52 Message: You're correct. We can't implement Wide characters API as Ruby 1.8 do not support encoding in the same way 1.9 does. A workaround will be use Win32API completely for the encoding translation, but I'm having hard time finding that right now. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27327&group_id=126 From noreply at rubyforge.org Wed Oct 21 16:36:34 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 21 Oct 2009 16:36:34 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-22617 ] Gem.loaded_specs does not work on 1.9 Message-ID: <20091021203635.9A20516782AF@rubyforge.org> Bugs item #22617, was opened at 2008-10-30 17:32 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=22617&group_id=126 Category: other Group: v1.3.x Status: Open Resolution: Accepted Priority: 3 Submitted By: Paul Brannan (cout) Assigned to: Eric Hodel (drbrain) Summary: Gem.loaded_specs does not work on 1.9 Initial Comment: The loaded_specs attribute seems to always be empty on 1.9: [pbrannan at zem ruby]$ ruby -rubygems -e 'gem("ruby-prof"); p Gem.loaded_specs' {"ruby-prof"=>#=", #]]>, @version=#, @files=["Rakefile", "README", "LICENSE", "CHANGES", "bin/ruby-prof", "lib/ruby-prof", "lib/ruby-prof.rb", "lib/unprof.rb", "lib/ruby-prof/abstract_printer.rb", "lib/ruby-prof/call_tree_printer.rb", "lib/ruby-prof/call_tree_printer.rb.rej", "lib/ruby-prof/flat_printer.rb", "lib/ruby-prof/graph_html_printer.rb", "lib/ruby-prof/graph_printer.rb", "lib/ruby-prof/profile_test_case.rb", "lib/ruby-prof/task.rb", "rails_plugin/ruby-prof", "rails_plugin/ruby-prof/init.rb", "rails_plugin/ruby-prof/lib", "rails_plugin/ruby-prof/lib/profiling.rb", "examples/flat.txt", "examples/graph.html", "examples/graph.txt", "ext/extconf.rb", "ext/extconf.rb.rej", "ext/measure_allocations.h", "ext/measure_cpu_time.h", "ext/measure_memory.h", "ext/measure_process_time.h", "ext/measure_wall_time.h", "ext/ruby_prof.c", "test/basic_test.rb", "test/duplicate_names_test.rb", "test/line_number_test.rb", "test/measure_mode_test.rb", "test/module_test.rb", "test/no_method_class_test.rb", "test/prime.rb", "test/prime1.rb", "test/prime2.rb", "test/prime3.rb", "test/prime_test.rb", "test/printers_test.rb", "test/profile_unit_test.rb", "test/recursive_test.rb", "test/singleton_test.rb", "test/start_test.rb", "test/test_helper.rb", "test/test_suite.rb", "test/thread_test.rb", "test/timing_test.rb"], @has_rdoc=true, @specification_version=2, @loaded=true, @requirements=[], @signing_key=nil, @default_executable="ruby-prof", @email="shugo at ruby-lang.org and cfis at savagexi.com", @required_ruby_version=#=", #]]>, @rdoc_options=["--title", "ruby-prof", "--inline-source", "--line-numbers", "--main", "README"], @bindir="bin", @rubygems_version="1.2.0", @homepage="http://rubyforge.org/projects/ruby-prof/", @name="ruby-prof", @platform="ruby", @autorequire=nil, @rubyforge_project="ruby-prof", @extensions=["ext/extconf.rb"], @summary="Fast Ruby profiler", @loaded_from="/usr/local/lib/ruby/gems/1.8/specifications/ruby-prof-0.6.0.gemspec", @original_platform=nil, @post_install_message=nil, @description="ruby-prof is a fast code profiler for Ruby. It is a C extension and therefore is many times faster than the standard Ruby profiler. It supports both flat and graph profiles. For each method, graph profiles show how long the method ran, which methods called it and which methods it called. RubyProf generate both text and html and can output it to standard out or to a file.", @dependencies=[], @test_files=["test/test_helper.rb", "test/test_suite.rb"], @require_paths=["bin", "lib"]>} [pbrannan at zem ruby]$ ruby1.9 -rubygems -e 'gem("ruby-prof"); p Gem.loaded_specs' /usr/local/lib/ruby/gems/1.9.0/gems/rubygems-update-1.3.1/lib/rubygems/config_file.rb:7: warning: mismatched indentations: line 216:'def' and line 218:'end' /usr/local/lib/ruby/gems/1.9.0/gems/rubygems-update-1.3.1/lib/rubygems/config_file.rb:7: warning: mismatched indentations: line 231:'def' and line 233:'end' /usr/local/lib/ruby/gems/1.9.0/gems/rubygems-update-1.3.1/lib/rubygems/config_file.rb:7: warning: mismatched indentations: line 246:'def' and line 248:'end' /usr/local/lib/ruby/gems/1.9.0/gems/rubygems-update-1.3.1/lib/rubygems/config_file.rb:7: warning: mismatched indentations: line 261:'def' and line 263:'end' {} ---------------------------------------------------------------------- Comment By: Nikolai Weibull (pcp) Date: 2009-10-21 22:36 Message: Yes, I would love to be able to provide a patch, but I don?t see a solution. To me it looks like this is an inherent flaw in how Ruby 1.9 and Rubygems interact. Since Ruby 1.9 adds all the paths to gems installed on your system, Rubygems never gets a chance to load the specs and thus solve this problem. I have no idea why it was decided that Ruby 1.9 should augment its $LOAD_PATH in this way, nor why these things weren?t considered at the time, but it would be great if someone came up with a solution. ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-10-21 19:00 Message: Whiny you sound, patches are welcome too :-) ---------------------------------------------------------------------- Comment By: Nikolai Weibull (pcp) Date: 2009-10-21 18:48 Message: This is still the case on Windows 1.9.1-p243. By extension, Config.datadir, which is what I care about, doesn?t work. I don?t want to sound whiny, but I can?t see how this can have gone unfixed for close to a year now. It seems like a rather central concept. ---------------------------------------------------------------------- Comment By: Matt Hulse (mhulse) Date: 2009-08-05 01:27 Message: Yes, this is still happening in 1.9.1-p129. I'm on WinXP Pro using the mingw32 build from rubyinstaller.org/downloads. I just updated to rubygems 1.3.5 using gem update --system and Gem.loaded_specs is still empty until I call gem('') or gem('nokogiri') (the gem I'm looking for). ---------------------------------------------------------------------- Comment By: Joeri Samson (joeri) Date: 2009-03-29 20:42 Message: with 1.9.1p0 and rubygems 1.3.1 I get the same error as Eric Hodel, except if I print/access Gem.loaded_specs before calling gem "rake": joeri at alpha ~ $ ruby19 -rubygems -e 'p Gem.loaded_specs; gem("rake"); p Gem.loaded_specs' {} {"rake"=>#, @summary="Ruby based make-like utility.", @email="jim at weirichhouse.org", @homepage="http://rake.rubyforge.org", @rubyforge_project="rake", @description="Rake is a Make-like program implemented in Ruby. Tasks and dependencies are specified in standard Ruby syntax.", @autorequire=nil, @default_executable="rake", @signing_key=nil, @post_install_message=nil, @original_platform=nil, @rubygems_version="1.3.1", @specification_version=2, @date=2009-03-04 00:00:00 +0100, @require_paths=["bin", "lib"], @bindir="bin", @has_rdoc=true, @required_ruby_version=#=", #]], @version=nil>, @required_rubygems_version=#=", #]], @version=nil>, @platform="ruby", @cert_chain=[], @authors=["Jim Weirich"], @files=["install.rb", "CHANGES", "MIT-LICENSE", "Rakefile", "README", "TODO", "bin/rake", "lib/rake/classic_namespace.rb", "lib/rake/clean.rb", "lib/rake/contrib/compositepublisher.rb", "lib/rake/contrib/ftptools.rb", "lib/rake/contrib/publisher.rb", "lib/rake/contrib/rubyforgepublisher.rb", "lib/rake/contrib/sshpublisher.rb", "lib/rake/contrib/sys.rb", "lib/rake/gempackagetask.rb", "lib/rake/loaders/makefile.rb", "lib/rake/packagetask.rb", "lib/rake/rake_test_loader.rb", "lib/rake/rdoctask.rb", "lib/rake/repaired_system.rb", "lib/rake/ruby182_test_unit_fix.rb", "lib/rake/runtest.rb", "lib/rake/tasklib.rb", "lib/rake/testtask.rb", "lib/rake/win32.rb", "lib/rake.rb", "test/capture_stdout.rb", "test/check_expansion.rb", "test/contrib/test_sys.rb", "test/data/rakelib/test1.rb", "test/data/rbext/rakefile.rb", "test/filecreation.rb", "test/functional.rb", "test/in_environment.rb", "test/rake_test_setup.rb", "test/reqfile.rb", "test/reqfile2.rb", "test/session_functional.rb", "test/shellcommand.rb", "test/test_application.rb", "test/test_clean.rb", "test/test_definitions.rb", "test/test_earlytime.rb", "test/test_extension.rb", "test/test_file_creation_task.rb", "test/test_file_task.rb", "test/test_filelist.rb", "test/test_fileutils.rb", "test/test_ftp.rb", "test/test_invocation_chain.rb", "test/test_makefile_loader.rb", "test/test_multitask.rb", "test/test_namespace.rb", "test/test_package_task.rb", "test/test_pathmap.rb", "test/test_rake.rb", "test/test_rdoc_task.rb", "test/test_require.rb", "test/test_rules.rb", "test/test_task_arguments.rb", "test/test_task_manager.rb", "test/test_tasklib.rb", "test/test_tasks.rb", "test/test_test_task.rb", "test/test_top_level_functions.rb", "test/test_win32.rb", "test/data/imports/deps.mf", "test/data/sample.mf", "test/data/chains/Rakefile", "test/data/default/Rakefile", "test/data/dryrun/Rakefile", "test/data/file_creation_task/Rakefile", "test/data/imports/Rakefile", "test/data/multidesc/Rakefile", "test/data/namespace/Rakefile", "test/data/statusreturn/Rakefile", "test/data/unittest/Rakefile", "test/data/unittest/subdir", "doc/command_line_usage.rdoc", "doc/example", "doc/example/a.c", "doc/example/b.c", "doc/example/main.c", "doc/example/Rakefile1", "doc/example/Rakefile2", "doc/glossary.rdoc", "doc/jamis.rb", "doc/proto_rake.rdoc", "doc/rake.1.gz", "doc/rakefile.rdoc", "doc/rational.rdoc", "doc/release_notes", "doc/release_notes/rake-0.4.14.rdoc", "doc/release_notes/rake-0.4.15.rdoc", "doc/release_notes/rake-0.5.0.rdoc", "doc/release_notes/rake-0.5.3.rdoc", "doc/release_notes/rake-0.5.4.rdoc", "doc/release_notes/rake-0.6.0.rdoc", "doc/release_notes/rake-0.7.0.rdoc", "doc/release_notes/rake-0.7.1.rdoc", "doc/release_notes/rake-0.7.2.rdoc", "doc/release_notes/rake-0.7.3.rdoc", "doc/release_notes/rake-0.8.0.rdoc", "doc/release_notes/rake-0.8.2.rdoc", "doc/release_notes/rake-0.8.3.rdoc", "doc/release_notes/rake-0.8.4.rdoc"], @test_files=[], @rdoc_options=["--line-numbers", "--inline-source", "--main", "README", "--title", "Rake -- Ruby Make"], @extra_rdoc_files=["README", "MIT-LICENSE", "TODO", "CHANGES", "doc/command_line_usage.rdoc", "doc/glossary.rdoc", "doc/proto_rake.rdoc", "doc/rakefile.rdoc", "doc/rational.rdoc", "doc/release_notes/rake-0.4.14.rdoc", "doc/release_notes/rake-0.4.15.rdoc", "doc/release_notes/rake-0.5.0.rdoc", "doc/release_notes/rake-0.5.3.rdoc", "doc/release_notes/rake-0.5.4.rdoc", "doc/release_notes/rake-0.6.0.rdoc", "doc/release_notes/rake-0.7.0.rdoc", "doc/release_notes/rake-0.7.1.rdoc", "doc/release_notes/rake-0.7.2.rdoc", "doc/release_notes/rake-0.7.3.rdoc", "doc/release_notes/rake-0.8.0.rdoc", "doc/release_notes/rake-0.8.2.rdoc", "doc/release_notes/rake-0.8.3.rdoc", "doc/release_notes/rake-0.8.4.rdoc"], @executables=["rake"], @extensions=[], @requirements=[], @dependencies=[], @loaded=true, @loaded_from="/home/joeri/.gem/ruby/1.9.1/specifications/rake-0.8.4.gemspec">} ---------------------------------------------------------------------- Comment By: Eric Hodel (drbrain) Date: 2009-03-27 22:29 Message: With 1.9.1p0 and 1.9.2dev I see: $ ruby19 -v -rubygems -e 'gem "rake"; p Gem.loaded_specs' ruby 1.9.2dev (2009-03-28 trunk 23085) [i386-darwin9.6.0] :234:in `push_gem_version_on_load_path': Could not find RubyGem rake (>= 0) (Gem::LoadError) from :14:in `gem' from -e:1:in `
' This will take a bit more work than I planned for 1.3.1, and may require changes to gem_prelude :/ ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-03-16 11:50 Message: Ah, no, I hit .activate, which hits source_index. ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2009-03-16 11:48 Message: works for me ---------------------------------------------------------------------- Comment By: Daniel Berger (djberg96) Date: 2009-01-02 16:59 Message: Is this still happening in 1.9.1? ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=22617&group_id=126 From thewoolleyman at gmail.com Wed Oct 21 16:43:58 2009 From: thewoolleyman at gmail.com (Chad Woolley) Date: Wed, 21 Oct 2009 13:43:58 -0700 Subject: [Rubygems-developers] Recent refactoring introduced regression? Message-ID: In rev 2317, jbarnette introduced the following line into Gem::DependencyInstaller#find_gems_with_sources: requirements = dep.requirement.requirements.map do |req, ver| In my tests (GemInstaller integration tests against RubyGems trunk), this is breaking because sometimes the 'requirement' property on dependencies is nil. I'm not sure how this happens, because the Gem::Dependency seems to be getting constructed correctly with a requirement, but later in #find_gems_with_sources it is nil. Here is the gemspec: http://github.com/thewoolleyman/geminstaller/blob/master/spec/fixture/gems/specifications/dependent-stubgem-1.0.0.gemspec Any ideas? This seems like a regression, these tests have been working against rubygems since pre-1.0 days... Thanks, -- Chad From thewoolleyman at gmail.com Wed Oct 21 19:10:20 2009 From: thewoolleyman at gmail.com (Chad Woolley) Date: Wed, 21 Oct 2009 16:10:20 -0700 Subject: [Rubygems-developers] Recent refactoring to remove Gem::Version::Requirement breaks with old cached gem files Message-ID: Old cached gems contain marshalled referenced to Gem::Version::Requirement in required_ruby_version. This causes breakages when they are unmarshalled with the new trunk code in which this class has been removed. Here is an example (see dependent-stubgem-1.0.0.gem): http://github.com/thewoolleyman/geminstaller/tree/master/spec/fixture/gems/cache/ From noreply at rubyforge.org Thu Oct 22 13:10:30 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Oct 2009 13:10:30 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Patches-27334 ] patch to allow for non libs gems Message-ID: <20091022171030.96C7D1858289@rubyforge.org> Patches item #27334, was opened at 2009-10-22 17:10 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=27334&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: patch to allow for non libs gems Initial Comment: Currently if you do $ gem install FotoVerite-fotoverite-babygitter ... ERROR: While executing gem ... (NoMethodError) undefined method `each' for nil:NilClass $ ruby -rubygems -e '' /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:99:in `lib_dirs_for': undefined method `join' for nil:NilClass (NoMethodError) from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:24:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:23:in `each' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_path_searcher.rb:23:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:889:in `new' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:889:in `searcher' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:888:in `synchronize' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:888:in `searcher' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:528:in `find_files' from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:1132 from /usr/local/lib/ruby/site_ruby/1.8/ubygems.rb:10:in `require' from /usr/local/lib/ruby/site_ruby/1.8/ubygems.rb:10 This patch avoids this. Thanks! -r ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=27334&group_id=126 From noreply at rubyforge.org Thu Oct 22 13:29:45 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Oct 2009 13:29:45 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Patches-27335 ] patch to avoid undefined method size for nil Message-ID: <20091022172945.36DF31588060@rubyforge.org> Patches item #27335, was opened at 2009-10-22 17:29 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=27335&group_id=126 Category: `gem install` Group: None Status: Open Resolution: None Priority: 3 Submitted By: Roger Pack (rogerdpack) Assigned to: Nobody (None) Summary: patch to avoid undefined method size for nil Initial Comment: I never drilled down to see what caused it, but this message ERROR: While executing gem ? (NoMethodError) undefined method `size? for nil:NilClass seems overcome with the attached diff Thanks! (ref: http://github.com/rdp/rubygems/commit/cf10766529d441d9b012705d9f4a0538d8c7f52e) ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=27335&group_id=126 From noreply at rubyforge.org Thu Oct 22 19:27:19 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 22 Oct 2009 19:27:19 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Patches-27338 ] patch for avoiding satisfied_by? error Message-ID: <20091022232719.DB65D1858267@rubyforge.org> Patches item #27338, was opened at 2009-10-22 23:27 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=27338&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: patch for avoiding satisfied_by? error Initial Comment: The attached patch overcomes this trace (caused by some gem 'er other...which apparently has no requirements [?]): ERROR: While executing gem ... (NoMethodError) undefined method `satisfied_by?' for nil:NilClass /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency.rb:136:in `=~' /usr/local/lib/ruby/site_ruby/1.8/rubygems/spec_fetcher.rb:125:in `find_matching' /usr/local/lib/ruby/site_ruby/1.8/rubygems/spec_fetcher.rb:124:in `select' /usr/local/lib/ruby/site_ruby/1.8/rubygems/spec_fetcher.rb:124:in `find_matching' /usr/local/lib/ruby/site_ruby/1.8/rubygems/spec_fetcher.rb:123:in `each' /usr/local/lib/ruby/site_ruby/1.8/rubygems/spec_fetcher.rb:123:in `find_matching' /usr/local/lib/ruby/site_ruby/1.8/rubygems/spec_fetcher.rb:69:in `fetch' /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:100:in `find_gems_with_sources' /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:140:in `gather_dependencies' /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:139:in `each' /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:139:in `gather_dependencies' /usr/local/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:221:in `install' /usr/local/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:118:in `execute' /usr/local/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:115:in `each' /usr/local/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:115:in `execute' /usr/local/lib/ruby/site_ruby/1.8/rubygems/command.rb:257:in `invoke' /usr/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:132:in `process_args' /usr/local/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:102:in `run' /usr/local/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:58:in `run' /usr/local/bin/gem:21 Thanks! ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=27338&group_id=126 From thewoolleyman at gmail.com Thu Oct 22 20:29:57 2009 From: thewoolleyman at gmail.com (Chad Woolley) Date: Thu, 22 Oct 2009 17:29:57 -0700 Subject: [Rubygems-developers] Recent refactoring introduced regression? In-Reply-To: References: Message-ID: On Wed, Oct 21, 2009 at 1:43 PM, Chad Woolley wrote: > In rev 2317, jbarnette introduced the following line into > Gem::DependencyInstaller#find_gems_with_sources: > > ?requirements = dep.requirement.requirements.map do |req, ver| > > In my tests (GemInstaller integration tests against RubyGems trunk), > this is breaking because sometimes the 'requirement' property on > dependencies is nil. Here is a patch related to this problem, looks like other gems in the wild have missing requirement property, in addition to my test gems: http://rubyforge.org//tracker/?func=detail&atid=577&aid=27338&group_id=126 From thewoolleyman at gmail.com Fri Oct 23 00:23:14 2009 From: thewoolleyman at gmail.com (Chad Woolley) Date: Thu, 22 Oct 2009 21:23:14 -0700 Subject: [Rubygems-developers] Recent refactoring to remove Gem::Version::Requirement breaks with old cached gem files In-Reply-To: References: Message-ID: On Wed, Oct 21, 2009 at 4:10 PM, Chad Woolley wrote: > Old cached gems contain marshalled referenced to > Gem::Version::Requirement in required_ruby_version. ?This causes > breakages when they are unmarshalled with the new trunk code in which > this class has been removed. I looked into this some more. Even if I restore the hack to make Gem::Version::Requirement exist, the other refactorings to Gem::Version (e.g. the addition of the segments attribute) will break when old gems are unmarshalled. We need to either fully handle backward compatibility with old gems, or roll back the refactorings to Gem::Version which change the marshalled format. From jbarnette at gmail.com Fri Oct 23 14:45:46 2009 From: jbarnette at gmail.com (John Barnette) Date: Fri, 23 Oct 2009 11:45:46 -0700 Subject: [Rubygems-developers] Recent refactoring to remove Gem::Version::Requirement breaks with old cached gem files In-Reply-To: References: Message-ID: <2bce3eb60910231145l6218741fmd74769ccc723f6e@mail.gmail.com> On Thu, Oct 22, 2009 at 9:23 PM, Chad Woolley wrote: > On Wed, Oct 21, 2009 at 4:10 PM, Chad Woolley wrote: >> Old cached gems contain marshalled referenced to >> Gem::Version::Requirement in required_ruby_version. ?This causes >> breakages when they are unmarshalled with the new trunk code in which >> this class has been removed. > > I looked into this some more. ?Even if I restore the hack to make > Gem::Version::Requirement exist, the other refactorings to > Gem::Version (e.g. the addition of the segments attribute) will break > when old gems are unmarshalled. > > We need to either fully handle backward compatibility with old gems, > or roll back the refactorings to Gem::Version which change the > marshalled format. Yup, I definitely didn't intend to break backwards compatibility. Our marshaling tests must be even more lacking than I thought they were. Thanks for digging, Chad, I'll take a poke at it this weekend. ~ j. From thewoolleyman at gmail.com Fri Oct 23 14:53:18 2009 From: thewoolleyman at gmail.com (Chad Woolley) Date: Fri, 23 Oct 2009 11:53:18 -0700 Subject: [Rubygems-developers] Recent refactoring to remove Gem::Version::Requirement breaks with old cached gem files In-Reply-To: <2bce3eb60910231145l6218741fmd74769ccc723f6e@mail.gmail.com> References: <2bce3eb60910231145l6218741fmd74769ccc723f6e@mail.gmail.com> Message-ID: On Fri, Oct 23, 2009 at 11:45 AM, John Barnette wrote: > Yup, I definitely didn't intend to break backwards compatibility. Our > marshaling tests must be even more lacking than I thought they were. > Thanks for digging, Chad, I'll take a poke at it this weekend. Cool thanks. Feel free to keep me in the loop, especially if you have problems running the geminstaller tests. They are kind of wierd, I have to jump through a ton of hoops to test against an embedded trunk version of rubygems. From noreply at rubyforge.org Fri Oct 23 19:26:54 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 23 Oct 2009 19:26:54 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Feature Requests-27343 ] feature request: gem uninstall xxx -y Message-ID: <20091023232654.79E24185828D@rubyforge.org> Feature Requests item #27343, was opened at 2009-10-23 23:26 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=27343&group_id=126 Category: `gem` commands Group: None Status: Open Resolution: None Priority: 3 Submitted By: Roger Pack (rogerdpack) Assigned to: Nobody (None) Summary: feature request: gem uninstall xxx -y Initial Comment: It would be nice to not be prompted for anything during uninstall [like "do you want to remove this executable") Thanks! -r ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=27343&group_id=126 From noreply at rubyforge.org Sun Oct 25 11:55:58 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sun, 25 Oct 2009 11:55:58 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27346 ] gem cleanup fails on system wide installed gems with non informative error message Message-ID: <20091025155558.F28811858291@rubyforge.org> Bugs item #27346, was opened at 2009-10-25 16:55 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27346&group_id=126 Category: `gem` commands (other) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Martin H?cker (dwt) Assigned to: Nobody (None) Summary: gem cleanup fails on system wide installed gems with non informative error message Initial Comment: Hi there, I use gem to install stuff in my home directory and today found out that gem cleanup could get me rid of quite a part of old gems. This however didn't work, as those are installed system wide and I of course don't start gem with root privileges as I totally want it to install only in my home directory. The error message didn't mention this rights problem and the installed path at all, so I had to search very long till I found out why this failed. So, please improve the error message, make it state that rights are missing and on what file they are missing. Regards, Martin % gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.1 - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0] - INSTALLATION DIRECTORY: /Users/dwt/Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /Users/dwt/Library/Ruby/Gems/1.8/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-10 - GEM PATHS: - /Users/dwt/Library/Ruby/Gems/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8 - /Library/Ruby/Gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - "gempath" => ["/Users/dwt/Library/Ruby/Gems/1.8", "/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8", "/Library/Ruby/Gems/1.8"] - "gemhome" => "/Users/dwt/Library/Ruby/Gems/1.8" - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27346&group_id=126 From noreply at rubyforge.org Sun Oct 25 14:05:27 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sun, 25 Oct 2009 14:05:27 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27346 ] gem cleanup fails on system wide installed gems with non informative error message Message-ID: <20091025180528.08AF11858267@rubyforge.org> Bugs item #27346, was opened at 2009-10-25 12:55 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27346&group_id=126 Category: `gem` commands (other) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Martin H?cker (dwt) Assigned to: Nobody (None) Summary: gem cleanup fails on system wide installed gems with non informative error message Initial Comment: Hi there, I use gem to install stuff in my home directory and today found out that gem cleanup could get me rid of quite a part of old gems. This however didn't work, as those are installed system wide and I of course don't start gem with root privileges as I totally want it to install only in my home directory. The error message didn't mention this rights problem and the installed path at all, so I had to search very long till I found out why this failed. So, please improve the error message, make it state that rights are missing and on what file they are missing. Regards, Martin % gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.1 - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0] - INSTALLATION DIRECTORY: /Users/dwt/Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /Users/dwt/Library/Ruby/Gems/1.8/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-10 - GEM PATHS: - /Users/dwt/Library/Ruby/Gems/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8 - /Library/Ruby/Gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - "gempath" => ["/Users/dwt/Library/Ruby/Gems/1.8", "/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8", "/Library/Ruby/Gems/1.8"] - "gemhome" => "/Users/dwt/Library/Ruby/Gems/1.8" - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- >Comment By: Luis Lavena (luislavena) Date: 2009-10-25 15:05 Message: Hello, Thank you for your report. Please try updating your RubyGems installation to 1.3.5: sudo gem update --system Since several improvements in gem cleanup has been implemented in 1.3.3, which is greater than the version you're reporting from. Once you do that, try recreate the same scenario and report back the output of the clenaup command with "--debug -V". Thank you. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27346&group_id=126 From noreply at rubyforge.org Tue Oct 27 07:43:58 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 27 Oct 2009 07:43:58 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Patches-27357 ] Option --bind for gem server Message-ID: <20091027114358.5340115B8028@rubyforge.org> Patches item #27357, was opened at 27/10/2009 12:43 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=27357&group_id=126 Category: `gem server` command Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Bruno Michel (nono) Assigned to: Nobody (None) Summary: Option --bind for gem server Initial Comment: This patch adds an option -b / --bind for gem server. It makes gem serve binds only the given IP address. The default behaviour is not changed: binding on 0.0.0.0, but it enables a typical case, binding only on local interface: gem server -b 127.0.0.1. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=577&aid=27357&group_id=126 From noreply at rubyforge.org Tue Oct 27 18:44:58 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Tue, 27 Oct 2009 18:44:58 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27346 ] gem cleanup fails on system wide installed gems with non informative error message Message-ID: <20091027224458.423721588063@rubyforge.org> Bugs item #27346, was opened at 2009-10-25 16:55 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27346&group_id=126 Category: `gem` commands (other) Group: None >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Martin H?cker (dwt) Assigned to: Nobody (None) Summary: gem cleanup fails on system wide installed gems with non informative error message Initial Comment: Hi there, I use gem to install stuff in my home directory and today found out that gem cleanup could get me rid of quite a part of old gems. This however didn't work, as those are installed system wide and I of course don't start gem with root privileges as I totally want it to install only in my home directory. The error message didn't mention this rights problem and the installed path at all, so I had to search very long till I found out why this failed. So, please improve the error message, make it state that rights are missing and on what file they are missing. Regards, Martin % gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.1 - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0] - INSTALLATION DIRECTORY: /Users/dwt/Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /Users/dwt/Library/Ruby/Gems/1.8/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-10 - GEM PATHS: - /Users/dwt/Library/Ruby/Gems/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8 - /Library/Ruby/Gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - "gempath" => ["/Users/dwt/Library/Ruby/Gems/1.8", "/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8", "/Library/Ruby/Gems/1.8"] - "gemhome" => "/Users/dwt/Library/Ruby/Gems/1.8" - REMOTE SOURCES: - http://gems.rubyforge.org/ ---------------------------------------------------------------------- >Comment By: Martin H?cker (dwt) Date: 2009-10-27 23:44 Message: Indeed the new error message is quite good. Strange, I was under the impression that I did do "gem update --system" before reporting this - but apparently I missed it. Thanks for the reply and keep up the good work. Regards, Martin ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-10-25 19:05 Message: Hello, Thank you for your report. Please try updating your RubyGems installation to 1.3.5: sudo gem update --system Since several improvements in gem cleanup has been implemented in 1.3.3, which is greater than the version you're reporting from. Once you do that, try recreate the same scenario and report back the output of the clenaup command with "--debug -V". Thank you. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27346&group_id=126 From noreply at rubyforge.org Wed Oct 28 12:24:55 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 28 Oct 2009 12:24:55 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27366 ] gem env command doesn't display ~/.gem as a gem path Message-ID: <20091028162455.937451588067@rubyforge.org> Bugs item #27366, was opened at 2009-10-28 16:24 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27366&group_id=126 Category: `gem` commands (other) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Roger Pack (rogerdpack) Assigned to: Nobody (None) Summary: gem env command doesn't display ~/.gem as a gem path Initial Comment: Currently gem treats ~/.gem as a gem path, however running gem env doesn't hint at that fact. rdp at li49-39:~/dev/downloads/rubygems-1.3.5$ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.5 - RUBY VERSION: 1.8.6 (2009-3-4 patchlevel 287) [i686-linux] - INSTALLATION DIRECTORY: /home/rdp/dev/downloads/rubygems-1.3.5 - RUBY EXECUTABLE: /usr/local/bin/ruby - EXECUTABLE DIRECTORY: /home/rdp/dev/downloads/rubygems-1.3.5/bin - RUBYGEMS PLATFORMS: - ruby - x86-linux - GEM PATHS: - /home/rdp/dev/downloads/rubygems-1.3.5 - GEM CONFIGURATION: ... Thanks! -r ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27366&group_id=126 From noreply at rubyforge.org Wed Oct 28 13:51:30 2009 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Wed, 28 Oct 2009 13:51:30 -0400 (EDT) Subject: [Rubygems-developers] [ rubygems-Bugs-27366 ] gem env command doesn't display ~/.gem as a gem path Message-ID: <20091028175131.6FEDB1588067@rubyforge.org> Bugs item #27366, was opened at 2009-10-28 09:24 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27366&group_id=126 Category: `gem` commands (other) Group: None Status: Open Resolution: None Priority: 3 Submitted By: Roger Pack (rogerdpack) Assigned to: Nobody (None) Summary: gem env command doesn't display ~/.gem as a gem path Initial Comment: Currently gem treats ~/.gem as a gem path, however running gem env doesn't hint at that fact. rdp at li49-39:~/dev/downloads/rubygems-1.3.5$ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.5 - RUBY VERSION: 1.8.6 (2009-3-4 patchlevel 287) [i686-linux] - INSTALLATION DIRECTORY: /home/rdp/dev/downloads/rubygems-1.3.5 - RUBY EXECUTABLE: /usr/local/bin/ruby - EXECUTABLE DIRECTORY: /home/rdp/dev/downloads/rubygems-1.3.5/bin - RUBYGEMS PLATFORMS: - ruby - x86-linux - GEM PATHS: - /home/rdp/dev/downloads/rubygems-1.3.5 - GEM CONFIGURATION: ... Thanks! -r ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2009-10-28 10:51 Message: Hm, mine did on Snow Leopard: RubyGems Environment: - RUBYGEMS VERSION: 1.3.5 - RUBY VERSION: 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin10.0.0] - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.8 - RUBY EXECUTABLE: /usr/local/bin/ruby - EXECUTABLE DIRECTORY: /usr/local/bin - RUBYGEMS PLATFORMS: - ruby - x86-darwin-10 - GEM PATHS: - /usr/local/lib/ruby/gems/1.8 - /Users/dberger/.gem/ruby/1.8 ... Interestingly, when I run "gem env gempath" it only shows my .gem path, while "gem env gemdir" only shows the /usr/local/lib path. Intentional? Not sure. Not sure what to make of this yet. Regards, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27366&group_id=126 From adam.q.salter at gmail.com Tue Oct 20 02:42:01 2009 From: adam.q.salter at gmail.com (Adam Salter) Date: Tue, 20 Oct 2009 17:42:01 +1100 Subject: [Rubygems-developers] [ rubygems-Feature Requests-27318 ] weight spec.name when searching gem lib dirs for 'path' In-Reply-To: <4ADCB153.8010001@tenderlovemaking.com> References: <20091019174921.2345B1588060@rubyforge.org> <4ADCB153.8010001@tenderlovemaking.com> Message-ID: <89FB6B01-54FD-4322-8B0E-0E7D60908BDE@gmail.com> This change makes sense to me. Straight alphabetical sorting seems unfair and maybe a little insecure somehow. Installing 'aaaGem' could potentially wreak havoc, or make a very good little man in the middle gem. I'm not sure if this change would fix this problem, but I do recall seeing a similar problem in the dbd-odbc library: http://ruby-dbi.rubyforge.org/git?p=ruby-dbi.git;a=blob;f=lib/dbd/ODBC.rb;h=2c531b52613295ac802bdd880d668b159e52b0ca;hb=HEAD#l33 Line 33: -Adam On 20/10/2009, at 5:34 AM, Aaron Patterson wrote: > noreply at rubyforge.org wrote: >> Feature Requests item #27318, was opened at 2009-10-19 11:49 >> You can respond by visiting: >> http://rubyforge.org/tracker/?func=detail&atid=578&aid=27318&group_id=126 >> >> Category: local package management >> Group: None >> Status: Open >> Resolution: None >> Priority: 3 >> Submitted By: ara howard (ahoward) >> Assigned to: Nobody (None) >> Summary: weight spec.name when searching gem lib dirs for 'path' >> >> Initial Comment: >> gems has a *serious* issue in that someone structuring there gem like >> >> a_gem-1.2.3/lib/rails.rb >> >> will have there rails.rb loaded *before* the actual rails.rb when >> one does a >> >> require 'rails' >> >> this because the search through gem libdirs is sorted alpha/version >> wise with no concept of the semantics of the require statement. in >> fact, we know that users of rubygems mean to require the gem >> *named* rails when issuing the above. no gem user issues a normal >> require to pick up some random file from inside and arbitrary gem >> libdir. as such it makes sense to *prefer* file matches which >> exactly match the spec.name when searching. here is a patch, all >> tests that passed before (there was one failing) continue to pass >> with this patch: > > I don't think this is a problem rubygems necessarily needs to > solve. As > a library writer, why are you including a lib/rails.rb in your gem? > Why > not "lib/a_gem/rails.rb"? > > I wouldn't use a gem where the gem author didn't realize the > implications of included a top-level rb file that conflicted with > other > gems. It seems like bad form. > >> --- lib/rubygems/gem_path_searcher.rb.org 2009-10-19 >> 11:37:13.000000000 -0600 >> +++ lib/rubygems/gem_path_searcher.rb 2009-10-19 11:46:26.000000000 >> -0600 >> @@ -30,8 +30,11 @@ >> # Return the _gemspec_ of the gem where it was found. If no match >> # is found, return nil. >> # >> - # The gems are searched in alphabetical order, and in reverse >> - # version order. >> + # The gems are searched in alphabetical order, and in reverse >> version order. >> + # If a path is found in more than one gem the gem with a >> spec.name == path >> + # is preferred over others - in otherwords main-3.0.3/lib/ >> main.rb would be >> + # preferred over geonames-1.2.3/lib/main.rb if one issued a >> 'require "main"' >> + # - assuming main had spec.name=='main'. >> # >> # For example: >> # >> @@ -46,8 +49,18 @@ >> # only that there is a match. >> >> def find(path) >> - @gemspecs.find do |spec| matching_file? spec, path end >> + first_named = first = nil >> + @gemspecs.select do |spec| >> + if(matching_file?(spec, path)) >> + name = File.basename(path).sub(%r/\..*$/,'') >> + first ||= spec >> + first_named ||= spec if(spec.name == name) >> + end >> + break if(first_named and first) >> end >> + first_named or first >> + end >> + >> >> ## >> # Works like #find, but finds all gemspecs matching +path+. > > A patch with no tests? o_O > > -- > Aaron Patterson > http://tenderlovemaking.com/ > _______________________________________________ > Rubygems-developers mailing list > http://rubyforge.org/projects/rubygems > Rubygems-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers From rogerdpack2 at gmail.com Tue Oct 20 10:34:34 2009 From: rogerdpack2 at gmail.com (Roger Pack) Date: Tue, 20 Oct 2009 08:34:34 -0600 Subject: [Rubygems-developers] [ rubygems-Feature Requests-27318 ] weight spec.name when searching gem lib dirs for 'path' In-Reply-To: <6A820DD1-B2D7-4CC0-8747-86A7D0594232@gmail.com> References: <20091019174921.2345B1588060@rubyforge.org> <4ADCB153.8010001@tenderlovemaking.com> <2bce3eb60910191148g4a1ba9cev9151a29caf9b326a@mail.gmail.com> <6A820DD1-B2D7-4CC0-8747-86A7D0594232@gmail.com> Message-ID: <87d974fd0910200734m2847dfbv73feedca2c31a41b@mail.gmail.com> >> Ara, do you have any examples of gems that are busted by the current >> behavior? I assume you've run in to a few. > > I patched aasm not that long ago for this reason, it was conflicting with > state_machine If you have two gems that have a same named library [like mysql.so] then doing a require 'mysql' within one can sometimes require the mysql of the other. -r From adam.q.salter at gmail.com Fri Oct 30 17:37:49 2009 From: adam.q.salter at gmail.com (Adam Salter) Date: Sat, 31 Oct 2009 08:37:49 +1100 Subject: [Rubygems-developers] [ rubygems-Bugs-27366 ] gem env command doesn't display ~/.gem as a gem path In-Reply-To: <20091028175131.6FEDB1588067@rubyforge.org> References: <20091028175131.6FEDB1588067@rubyforge.org> Message-ID: <82E47200-83CF-4596-8942-EAD4B8787D50@gmail.com> I've had a lot of trouble with this on Ruby1.9 (.1p243 Mac OS 10.6) My solution was to use a bash script: export BIN_PATH=$PATH # find current version v=`ruby -e 'puts RUBY_VERSION'` if [ $v == "1.9.1" ];then export PATH=$BIN_PATH:~/Library/bin:$HOME/.gem/ruby/1.9.1/bin export GEM_HOME=/opt/local/lib/ruby1.9/gems/1.9.1 export GEM_PATH=$GEM_HOME:/Users/adam/.gem/ruby/1.9.1 else export PATH=$BIN_PATH:~/Library/bin:$HOME/.gem/ruby/1.8/bin fi Not ideal obviously. -Adam On 29/10/2009, at 4:51 AM, wrote: > Bugs item #27366, was opened at 2009-10-28 09:24 > You can respond by visiting: > http://rubyforge.org/tracker/?func=detail&atid=575&aid=27366&group_id=126 > > Category: `gem` commands (other) > Group: None > Status: Open > Resolution: None > Priority: 3 > Submitted By: Roger Pack (rogerdpack) > Assigned to: Nobody (None) > Summary: gem env command doesn't display ~/.gem as a gem path > > Initial Comment: > Currently gem treats ~/.gem as a gem path, however running gem env > doesn't hint at that fact. > > rdp at li49-39:~/dev/downloads/rubygems-1.3.5$ gem env > RubyGems Environment: > - RUBYGEMS VERSION: 1.3.5 > - RUBY VERSION: 1.8.6 (2009-3-4 patchlevel 287) [i686-linux] > - INSTALLATION DIRECTORY: /home/rdp/dev/downloads/rubygems-1.3.5 > - RUBY EXECUTABLE: /usr/local/bin/ruby > - EXECUTABLE DIRECTORY: /home/rdp/dev/downloads/rubygems-1.3.5/bin > - RUBYGEMS PLATFORMS: > - ruby > - x86-linux > - GEM PATHS: > - /home/rdp/dev/downloads/rubygems-1.3.5 > - GEM CONFIGURATION: > ... > > Thanks! > -r > > ---------------------------------------------------------------------- > >> Comment By: Daniel Berger (djberg96) > Date: 2009-10-28 10:51 > > Message: > Hm, mine did on Snow Leopard: > > RubyGems Environment: > - RUBYGEMS VERSION: 1.3.5 > - RUBY VERSION: 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin10.0.0] > - INSTALLATION DIRECTORY: /usr/local/lib/ruby/gems/1.8 > - RUBY EXECUTABLE: /usr/local/bin/ruby > - EXECUTABLE DIRECTORY: /usr/local/bin > - RUBYGEMS PLATFORMS: > - ruby > - x86-darwin-10 > - GEM PATHS: > - /usr/local/lib/ruby/gems/1.8 > - /Users/dberger/.gem/ruby/1.8 > ... > > Interestingly, when I run "gem env gempath" it only shows my .gem > path, while "gem env gemdir" only shows the /usr/local/lib path. > Intentional? Not sure. > > Not sure what to make of this yet. > > Regards, > > Dan > > ---------------------------------------------------------------------- > > You can respond by visiting: > http://rubyforge.org/tracker/?func=detail&atid=575&aid=27366&group_id=126 > _______________________________________________ > Rubygems-developers mailing list > http://rubyforge.org/projects/rubygems > Rubygems-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers