Hi On 07/29/2012 06:58 AM, Dmitry Borodaenko wrote: > 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.
> 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? No, MySQL2 old-stable does not need to be used at all, Redmine is compatible with Rails 3.2 [1] via the 2.x branch [which is stable as the 1.4 branch.] Actually it would probably make management and bug handling a bit easier, read below for more. [1] https://github.com/redmine/redmine/blob/master/Gemfile#L3 > 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. There really is no need. If one keeps the old MySQL active for now until rdepends of it die or get updated and then just upgrades Redmine to 2.x, which supports both MySQL on 1.8 and MySQL2 on 1.9 [with no version dependencies] then all should be well IMO, but 1.8 is as good as dead to some, and so are some versions of Rails (even if they get security updates for now.) This should rid of quite a few old packages that keep hindering, but that outlook is subjective and optimistic since I can't assume what the maintainers will do. What I mean by all that is... Just adding MySQL2 latest and Redmine latest should solve the problem IMO and the rest will resolve itself as 1.8 finally dies for good and Rails 2.3 dies for good too. > A quick search through the packages shows that there's not that many > direct and indirect reverse dependencies of ruby-mysql. > ruby-graffiti, jekyll: > > They use Sequel which supports Mysql2. > Objections, ideas? I really think Redmine should be pushed to the 2.x branch which would fix this bug, but I assume people will object to that because they might have a lot invested in 1.4 and I don't assume there is an easy way to manage everyones upgrades in a straight forward manner, but when we upgraded here the path was pretty easy [2] [2] http://www.redmine.org/projects/redmine/wiki/RedmineUpgrade -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
