[Rubygems-developers] [ rubygems-Bugs-27575 ] Gem reports: WARNING: RubyGems 1.2+ index not found for

2010-05-23 Thread noreply
Bugs item #27575, was opened at 2009-12-16 10:29 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=27575&group_id=126 Category: other Group: v1.3.x Status: Closed Resolution: Rejected Priority: 3 Submitted By: Yann Golanski (kierun) Assigned to: Nobody (None) Sum

[Rubygems-developers] [ rubygems-Bugs-28238 ] gem update fails when released gem is outdated but a prerelease is installed

2010-05-23 Thread noreply
Bugs item #28238, was opened at 2010-05-23 15:23 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28238&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Caio Chassot (cchassot) Assigned to: Nobod

[Rubygems-developers] [ rubygems-Bugs-28238 ] gem update fails when released gem is outdated but a prerelease is installed

2010-05-23 Thread noreply
Bugs item #28238, was opened at 2010-05-23 15:23 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28238&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Caio Chassot (cchassot) Assigned to: Nobod

[Rubygems-developers] [ rubygems-Bugs-28237 ] gem outdated fails for gems that are outdated but have a prerelease installed

2010-05-23 Thread noreply
Bugs item #28237, was opened at 2010-05-23 14:58 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28237&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Caio Chassot (cchassot) Assigned to: Nobod

[Rubygems-developers] [ rubygems-Bugs-28237 ] gem outdated fails for gems that are outdated but have a prerelease installed

2010-05-23 Thread noreply
Bugs item #28237, was opened at 2010-05-23 14:58 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28237&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Caio Chassot (cchassot) Assigned to: Nobod

[Rubygems-developers] [ rubygems-Bugs-28237 ] gem outdated fails for gems that are outdated but have a prerelease installed

2010-05-23 Thread noreply
Bugs item #28237, was opened at 2010-05-23 14:58 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28237&group_id=126 Category: `gem` commands (other) Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Caio Chassot (cchassot) Assigned to: Nobod

Re: [Rubygems-developers] API access to versions in list command

2010-05-23 Thread Chad Woolley
On Sun, May 23, 2010 at 1:21 AM, Chad Woolley wrote: > 1. Are we doing it wrong? Does the RubyGems API provide a way to avoid > this manual parsing? > 2. Should there be a --[no-]platforms option to the 'list' command, > which would have made these updates to the parsing logic unnecessary? So, I

[Rubygems-developers] API access to versions in list command

2010-05-23 Thread Chad Woolley
This [1] manual Gem version parsing was just added to chef to handle the addition of platforms to the version string in 1.3.7. I had to update GemInstaller in a similar fashion [2]. Two questions: 1. Are we doing it wrong? Does the RubyGems API provide a way to avoid this manual parsing? 2. Shou