```Issue #3607 has been updated by Roger Pack.

I just ran into this, as well [1].  I suppose it's a bug that needs to be fixed within rubygems proper, then?

The following fixed it for me, as a work around.