[debian-mysql] MariaDB 10.6 regressed ruby-mysql2

Otto Kekäläinen otto at debian.org
Sun Jan 16 20:58:01 GMT 2022


Status update:

We are currently waiting for upstream ruby-mysql2 to make a new
release 0.5.4 which would include the fix mentioned below.

Tracking and comment at
https://github.com/brianmario/mysql2/issues/1179#issuecomment-1013950778

On Tue, Jan 4, 2022 at 4:26 PM Daniel Black <daniel at mariadb.org> wrote:
>
> FYI message forward to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002087
>
>
> On Thu, Dec 23, 2021 at 10:40 AM Daniel Black <daniel at mariadb.org> wrote:
> >
> >    expected Mysql2::Error with message matching /Lost connection to
> > MySQL server/, got #<Mysql2::Error::ConnectionError: Lost connection
> > to server during query> with backtrace:
> >
> > Our error message changed.
> >
> > ruby-mysql2 already fixed the test upstream -
> > https://github.com/brianmario/mysql2/commit/cca57b97ad6d1b1b985376be110b89d2b487dea6
> >
> >
> > On Thu, Dec 23, 2021 at 4:47 AM Otto Kekäläinen <otto at debian.org> wrote:
> > >
> > > Hello!
> > >
> > > Looking at https://tracker.debian.org/pkg/mariadb-10.6 it seems mariadb 1.10.6.5-2 is currently blocked from progressing from Debian unstable to testing due to Debian-CI/autopkgtests failures on package ruby-mysql2.
> > >
> > > This is a regression from 10.5. Could somebody please investigate?
> > >
> > > - Otto



More information about the pkg-mysql-maint mailing list