Get rid of ‘Gem::Specification#rubyforge_project=’ deprecation warnings
1 min readMay 3, 2020
Recently I ran into the error “Cant find gem bundler (>= 0.a) with executable bundle” when installing a bundle in a Ruby project.
The fix for this problem is to run “gem update — system”, but in my case that lead to all gems throwing the deprecation warning “Gem::Specification#rubyforge_project=” for every gem installed in my bundle, because of a bug in Rubygems.
To solve this annoyance, simply run “gem update — system 3.0.0” and the problem will be fixed.