Your message dated Fri, 21 Jan 2022 22:15:51 +0100 with message-id <1f872096-d7a9-2ee6-3bdf-a472403ec32a@debian.org> and subject line Re: Bug#1004151: Skip test ruby-mysql2/0.5.3-3 for mariadb-10.6 has caused the Debian Bug report #1004151, regarding Skip test ruby-mysql2/0.5.3-3 for mariadb-10.6 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1004151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004151 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org, Lucas Nussbaum <lucas@debian.org>
- Subject: Skip test ruby-mysql2/0.5.3-3 for mariadb-10.6
- From: Otto Kekäläinen <otto@debian.org>
- Date: Fri, 21 Jan 2022 12:11:48 -0800
- Message-id: <[🔎] CAOU6tADJjuj7_Qr8eidbOm_dnam8QjtxLgcy9SLMf1QQE1LnQw@mail.gmail.com>
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
--- End Message ---
--- Begin Message ---
- To: Otto Kekäläinen <otto@debian.org>, 1004151-done@bugs.debian.org, Lucas Nussbaum <lucas@debian.org>, 1002087@bugs.debian.org
- Subject: Re: Bug#1004151: Skip test ruby-mysql2/0.5.3-3 for mariadb-10.6
- From: Paul Gevers <elbrus@debian.org>
- Date: Fri, 21 Jan 2022 22:15:51 +0100
- Message-id: <1f872096-d7a9-2ee6-3bdf-a472403ec32a@debian.org>
- In-reply-to: <[🔎] CAOU6tADJjuj7_Qr8eidbOm_dnam8QjtxLgcy9SLMf1QQE1LnQw@mail.gmail.com>
- References: <[🔎] CAOU6tADJjuj7_Qr8eidbOm_dnam8QjtxLgcy9SLMf1QQE1LnQw@mail.gmail.com>
Hi Otto, On 21-01-2022 21:11, Otto Kekäläinen wrote:Currently mariadb-10.6 is blocked from migrating to testing due to test failure in ruby-mysql2/0.5.3-3I just uploaded a fix. The bug report already had the solution since January 5.PaulAttachment: OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---