control: tag -1 sid stretch On Sat, 31 Oct 2015 13:06:55 -0500 Adam Majer <ad...@zombino.com> 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 not as bad as it initially looks (the message emits major.minor.patchlevel versions), because only the first two components of the version (major.minor) are being compared, so it blows up on the 5.5->5.6 switch. The new upstream patchlevel releases frequently uploaded to (old-)stable do not cause problems. Andreas
