#678515: ruby-mysql vs ruby1.9 encodings vs redmine
I'm somewhat puzzled about this bug. The root cause of the problem
appears to be that ruby-mysql doesn't support Ruby 1.9 string encodings,
and it is abandoned upstream, so a quick fix from upstream isn't likely.
The proposed solution is to package Mysql2 gem, and this is where things
Weirdest but possibly easiest problem is that bug comments say that
Mysql2 0.2.x should be used instead of the latest upstream 0.3.x,
because the latter doesn't include activerecord-mysql2-adapter which has
migrated into rails 3.1. Can anyone confirm how this reconciles with the
ruby-rails-3.2 package? Is redmine still not compatible with rails3?
I don't think packaging an old version of Mysql2 is a good solution, if
that's the only way to get remine work with mysql under ruby1.9, I'm
inclined to package latest Mysql2 and then reassign this bug back to
redmine so that it can be made to work with Mysql2 0.3.x.
And this is where we get to the second problem: we shouldn't have two
mutually incompatible sets of Ruby MySQL bindings in Debian.
A quick search through the packages shows that there's not that many
direct and indirect reverse dependencies of ruby-mysql.
Can be safely removed if its own reverse dependencies can be satisfied
They use Sequel which supports Mysql2.
No straight answer in documentation but it seems to support Mysql2.
OAR uses DBI, so it will need a port to Sequel before it can drop its
dependency on ruby-dbd-mysql.
Based on all this (including all the assumptions I've made above), the
most sensible way forward is rather long and winding:
1. Package MySQL2 0.3.11 as ruby-mysql2.
2. Reassign #678515 back to redmine-mysql.
3. Raise new normal bugs against ruby-graffiti, jekyll, and
ruby-opennebula to update its Depends.
4. Raise new upstream normal bug against oar to replace Ruby/DBI with
5. Raise new serious bugs against ruby-mysql and ruby-dbd-mysql to warn
off future would-be dependers and remove these package as soon as their
reverse-dependencies are sorted.