[debian-mysql] Heads up to release team about MariadB 10.3

[Emilio Pozuelo Monfort]

On 18/01/2019 13:52, Olaf van der Spek wrote:
> On Fri, Jan 18, 2019 at 11:44 AM Emilio Pozuelo Monfort
> <pochu at debian.org> wrote:
>>
>> On 18/01/2019 10:59, Olaf van der Spek wrote:
>>> On Thu, Jan 17, 2019 at 3:37 PM Emilio Pozuelo Monfort <pochu at debian.org> wrote:
>>>> That was with the old libdbd-mariadb-perl, and the new one (which was fine)
>>>> wasn't migrating due to a build-dep on the new mysql-defaults, which was blocked
>>>> on mariadb-10.3, blocked on libdbd-mariadb-perl... I cheated a bit and let
>>>> libdbd-mariadb-perl ignore that build-dep and migrate to testing ahead of
>>>> mysql-defaults, so now mariadb-10.3 and mysql-defaults should be happy to
>>>> migrate soon (once the age requirements are met).
>>>
>>> Isn't the migration script capable of migrating all 3 at once automatically?
>>
>> The problem was that the old libdbd-mariadb-perl didn't work with the new
>> mariadb-10.3, so without a Breaks relationship in mariadb-10.3, there was an
>> autopkgtests regression that was blocking the mariadb-10.3 migration. Yes, a
>> Breaks could have been added, but that would have caused extra delays and I
>> wanted to avoid that.
> 
> Do the autopkgtests run with versions from testing or with versions
> from unstable?
> If from unstable, how is the old libdbd-mariadb-perl version (in
> testing) relevant?

https://ci.debian.net/packages/libd/libdbd-mariadb-perl/testing/amd64/

Emilio