Hi,
ruby-mysql is upstream dead [1].
I personally think we should let this package die for stretch.
[1] https://github.com/luislavena/mysql-gem
Best,
--
,''`. Christian Hofstaedtler
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
On Sun, Nov 01, 2015 at 01:18:28PM +0100, Andreas Beckmann wrote:
> On Sat, 31 Oct 2015 13:06:55 -0500 Adam Majer wrote:
> > Furthermore, rebuilding does not fix the bug at root of the
> > problem. If MySQL get upgraded to another minor version while keeping
> > its soname as is (ie. ABI doesn't c
control: tag -1 sid stretch
On Sat, 31 Oct 2015 13:06:55 -0500 Adam Majer wrote:
> Furthermore, rebuilding does not fix the bug at root of the
> problem. If MySQL get upgraded to another minor version while keeping
> its soname as is (ie. ABI doesn't change), ruby-mysql will break
> again.
It's
severity 803222 grave
tag 803222 + patch
thanks
After more careful look at this bug, the problem is entirely within
ruby-mysql and its handling of MySQL versions. Debian does not work
the way this software thinks. Needless to say, the entire MySQL
version check currently results in complete breaki
Package: ruby-mysql
Version: 2.9.1-1+b1
Severity: important
irb(main):001:0> require 'mysql'
RuntimeError: Incorrect MySQL client library version! This gem was compiled for
5.5.43 but the client library is 5.6.25.
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`requir
5 matches
Mail list logo