markmcspadden/ruby_chopped

Received same gem just two different versions of it

Closed this issue · 4 comments

Need to make sure that the same gem isn't picked for both gems.

If you decide to pull my fork in I think I have this fixed. Great gem idea! :0)

Did the pull bring in the fix or is still lingering out there?

Sorry...should be more specific...did 0.0.5 solve the issue?

Looks like the gem out there is still 0.0.4 however looking at the code it should be fixed, the only 'gem_pool' that I think is affected by is the 50 most popular list and extracting just the names and calling uniq! should be the fix.