Comment 25 for bug 1310292

Here is our workaround which should be better than the ones proposed above (doesn't get wiped out by package upgrade / reinstall)

# Rename original out of the way, so updates / reinstalls don't squash our hack fix
dpkg-divert --add --rename --divert /usr/bin/ruby.divert /usr/bin/ruby
dpkg-divert --add --rename --divert /usr/bin/gem.divert /usr/bin/gem
# Create an alternatives entry pointing ruby -> ruby2.0
update-alternatives --install /usr/bin/ruby ruby /usr/bin/ruby2.0 1
update-alternatives --install /usr/bin/gem gem /usr/bin/gem2.0 1

Can we get this issue re-evaluated / re-opened? IMO the "Won't Fix" assessment was premature, especially in the context of Ruby 1.9 being unsupported.