[debian-mysql] Bug#917075: mariadb-10.3: libmariadb3 causes removal of default-libmysqlclient-dev

[Sebastiaan Couwenberg]

On 1/5/19 12:24 PM, Otto Kekäläinen wrote:
> ti 25. jouluk. 2018 klo 21.31 Sebastiaan Couwenberg kirjoitti:
>>> I cannot reproduce this inside a Docker image (e.g. via Salsa
>>> gitlab-ci.yml) because the operation is too heavy, but basically this
>>> bug report is about how aptitude resolves build dependencies and that
>>> specific part can be reproduced with:
>>>
>>> aptitude -y build-dep gdal
>>>
>>> This, however, does not result in any problems either.
>>
>> Have you checked the buildlog to see whether MySQL support is enabled or
>> not?
>>
>> Also try building grass, vtk7, or any of the other affected packages.
>> Both grass & vtk7 FTBFS in my sid pbuilder chroots.
> 
> Unfortunately I cannot create a gitlab-ci.yml pipeline for these
> builds myself right now. Pbuilder as such does not work in a Docker
> setting and other alternatives I tried required too much effort from
> me to finalize.

Don't solely rely on CI. Use a real system (or VM) to rebuild the
mariadb reverse dependencies like they would on developers systems
and/or buildds (using pbuilder and/or sbuild). And treat a switch like
this (from 10.1 to 10.3) as a proper transition coordinated with the
release team.

> Would you Sebastiaan want to take a try at extending the
> https://salsa.debian.org/mariadb-team/mariadb-10.3/blob/master/debian/gitlab-ci.yml
> to this testing?

No.

You can also close this issue as it was fixed by the mysql-defaults
changes mentioned previously.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1