Bug#1004151: Skip test ruby-mysql2/0.5.3-3 for mariadb-10.6
Package: release.debian.org
Currently mariadb-10.6 is blocked from migrating to testing due to
test failure in ruby-mysql2/0.5.3-3
Please consider adding a migration hint[1, 2] like:
force-skiptest ruby-mysql2/0.5.3-3
We are currently waiting for upstream ruby-mysql2 to make a new
release 0.5.4 which would include the fix test failure. This is
however likely to take a long time and it is unreasonable to keep
blocking mariadb-10.6 on this.
>From upstream issue [3]:
> A new 0.5.4 release that includes commit cca57b9 would enable Debian to release a new version of ruby-mysql2 to fix Debian bug #1002087, which in turn would unblock MariaDB 10.6 from entering Debian testing, which in turn would unblock mariadb-10.5 10.5.13-0+deb11u1 from entering Debian Bullseye, which in turn would fix Debian#1003839 and a bunch of other issues.
I recommend unblocking the test rather than making new patched uploads
of ruby-mysql as that would require extra efforts in testing and
preparing a release for a one-off benefit. Skipping a test seems to me
like a better solution for a one-off problem.
[1] https://release.debian.org/doc/britney/hints.html
[2] examples: https://release.debian.org/britney/hints/elbrus
[3] https://github.com/brianmario/mysql2/issues/1179#issuecomment-1013950778
Reply to: