Pierre-Elliott Bécue: > Le lundi 11 février 2019 à 23:40:51+0100, Jonas Meurer a écrit : >> Hi PEB, hi anarcat, >> >> Pierre-Elliott Bécue: >>> Le lundi 11 février 2019 à 16:27:21-0500, Antoine Beaupré a écrit : >>>> On 2019-02-11 21:52:32, Pierre-Elliott Bécue wrote: >>>>> Le lundi 11 février 2019 à 09:14:55-0500, Antoine Beaupré a écrit : >>>>>> Right, the only way this could be properly implemented would be if >>>>>> debconf would attempt to connect with the configured DB credentials to >>>>>> check the remote server version (or, better, to test the actuall code >>>>>> bugginess). >>>>>> >>>>>> That's probably overkill though. >>>>> >>>>> ISTM that it is. >>>>> >>>>> But if you wish to go to such extents I'd be glad to include a patch! >>>>> (no time to dev it though) >>>> >>>> Alright, let good win in the face of non-existing perfect threats. ;) >>> >>> I'll leave ourselves 24h of thinking and then I'll upload. >>> >>> If you get attacked by insomnia, you know what to do. :P >> >> Sorry for not responding earlier, I was to busy with other things. >> Still, I should have reacted earlier ... >> >> As you might have seen, mariadb-10.1 10.1.37-0+deb9u1 is in stable-new >> queue[1]. I don't know the details why it didn't proceed to stable yet, >> but there's hope that this issue will be sorted out in Stretch soon. The >> 10.1.37 contains both the upstream backport of >> `innodb_default_row_format`[2] and the patch to the config[3] that sets >> the default row format to `dynamic`, so the `max key length is 767 >> bytes` error is definitely fixed in this release. >> >> Therefore I don't think it's still *needed* to upload the patch that PEB >> poposed in this bugreport. I don't *object* to uploading it either. So >> if you want to, go ahead, PEB. But we should track the mariadb 10.1 >> version in Stretch and remove the Debconf question again once mariadb >> 10.1.37 got accepted into Stretch. >> >> Cheers > > This mariadb release seems to be already in security for stretch. > > I changed a little the warning but I think we should keep it (at least > until the point release of stretch is really done): > https://salsa.debian.org/mailman-team/mailman-suite/commits/stretch-backports > > Tell me what you think about it.
Thanks for taking care, PEB! As written, I don't have strong feelings on that, given that a compatible MariaDB should propagate to Stretch soon (hopefully). Feel free to upload as is, I reviewed the commits and think they're fine. I agree with you though that we should remove the debconf notification again once the compatible MariaDB packages went into Stretch. Cheers jonas >
signature.asc
Description: OpenPGP digital signature
