This is nowhere remotely nearly as bad as Debian's bug, which broke the underlying library underpinning most of the crypto on Linux, and broke the most universally sensitive component of that library.
Both cases cause key generation to produce weak, easily broken keys. I agree that far less software does key generation with Ruby than with OpenSSL, but that aside the severity of the bug seems quite similar.
While the effects caused by each bug might be on a similar level, I would argue that the fact that this particular bug was never released in a patch (I don't think I've ever seen anyone using Ruby trunk outside of those hacking the Ruby interpreter) makes it less severe.
In other words, equally serious, but in software not nearly as widely used.
It'd be pretty bad if it were in any of the stable builds of ruby that people actually use in production. As it stands it's a month-old bug in a bleeding-edge repo, not a huge deal. Nice that someone caught it early!
This is bad, but it's not in the same league as the Debian ssh bug.