Bugs item #29070, was opened at 2011-03-08 04:11 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=29070&group_id=126
Category: other Group: None >Status: Closed >Resolution: Out of Date Priority: 3 Submitted By: Usaku Nakamura (usa) Assigned to: Luis Lavena (luislavena) Summary: MRI test-all reports a failure on Windows Initial Comment: see r31062 on MRI. ---------------------------------------------------------------------- >Comment By: Luis Lavena (luislavena) Date: 2011-03-09 21:35 Message: Hello, I can confirm this issue is no longer present in trunk, was fixed by RubyGems 1.6.0 and now is merged in trunk. ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2011-03-08 18:38 Message: Luis, we pulled in 1.6.0 (and maybe 1.6.1?) into trunk... so I think something else might be going on. Can you look into it? We're about to do 1.6.2 so I'll double check that we're completely synced up when we release. ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2011-03-08 09:40 Message: Hello, This was already fixed in RubyGems master prior the release of 1.6.0: https://github.com/rubygems/rubygems/commit/53df9ed9364ae9130ffbed92cd28f9fb16140802 And the rationale was simple: cache_dir expand_path, which will contain ':' for Windows drive letter at the beginning of it, but not as part of the cache dir. So decided to extract .dir from it before doing the comparison. The change done in trunk should be reverted with this change. When RubyGems will be merged back? Dunno if I should mark this as out of date or closed, so assigning back to you Ryan to decide. ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2011-03-08 07:41 Message: I default to reject because the change was made in ruby-trunk in a clearly marked file. So... Your call Luis... ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=29070&group_id=126 _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
