or Create a profile
01 Mar, 2011 11:53 PM
shows 0.0.1.alpha instead of 0.0.3.alpha.
2 Posted by Luis Lavena on 02 Mar, 2011 12:04 AM
All your gems are prerelease status, and RubyGems.org prioritizes
Which triggers this:
And ends here, setting up latest to true:
And, drum roll, here:
Patches are welcome? ;-)
3 Posted by mtodd on 02 Mar, 2011 06:22 AM
Thanks for the awesome breakdown of the problem, Luis! I'll take
a look tomorrow to see if I can come up with a failing spec and
possibly a patch.
Thanks again for doing the legwork! :) Definitely a huge
motivator to write a patch.
Keep up the good motivation ;)
Nick Quaranto closed this discussion
on 17 Mar, 2011 03:34 PM.
mtodd re-opened this discussion
on 17 Mar, 2011 04:29 PM
4 Posted by mtodd on 17 Mar, 2011 04:29 PM
Haha, just decided to actually check if this had been fixed
because I was going to have some time this weekend for hacking...
looks like it was fixed. Booyah. Thanks!
mtodd closed this discussion
on 17 Mar, 2011 04:29 PM.
Comments are currently closed for this discussion.
You can start a new one.
2 people watching.
No more actions from RubyGems.org or the discussion starter are required.
This discussion is private.
Only you and RubyGems.org support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
Powered by Tender™.