Bugs item #29074, was opened at 2011-03-10 17:44
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29074&group_id=126

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Martin Tepper (mgpalmer)
Assigned to: Nobody (None)
Summary: Can't upgrade to newer rubygems version with explicit version number

Initial Comment:
Hi everybody !

I've already briefly explained the problem here:

http://help.rubygems.org/discussions/problems/514-cant-upgrade-to-newer-rubygems-version-with-explicit-version-number

Basically, upgrading rubygems to a specific, higher-than-now version (or the 
latest version) doesn't work as it is. You can workaround by installing 
rubygems-update manually, but I think it's quite unobvious why you can't just 
tell the target version and be done with it.

I've poked around in the code and found a solution. Here's my take on it:

https://github.com/MGPalmer/rubygems/commit/a1bd03cd597a3a0fc1d13059c582ac7266c34fb8

I haven't really contributed to a project before like this, is there anything 
else I need to do ? Run tests etc. ?

Thanks for all your work on the ruby ecosystem !

Best regards,
Martin Tepper

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=575&aid=29074&group_id=126
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers

Reply via email to