Hi, Resuming the discussion about this bug, I believe the best solution we can come up right now is to drop the Provides for ruby-interpreter in jruby, given how late we are on the release cycle already. However, I'd like to revisit this issue during "buster" development cycle. jruby provides high compatibility with MRI, so users should be able to use rake and/or another standard ruby tools with jruby if they want. We should have in place a simple way to switch interpreters. I'd like to have jruby 9k packaged for "buster", so this package can be more relevant and more useful for real world users, so it's likely this need will surface again in the future. I plan to upload the most recent upstream release for jruby 1.7.x this weekend and fix all remaining RC bugs, unless there is an objection or some unexpected blocker. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche
Attachment:
signature.asc
Description: Digital signature