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

Otto Kekäläinen otto at debian.org
Sat Jan 5 11:24:21 GMT 2019


ti 25. jouluk. 2018 klo 21.31 Sebastiaan Couwenberg
(sebastic at xs4all.nl) 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.

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? Having it in gitlab-ci.yml would ensure that the
packaging is correct it works as expected, and later on nobody would
accidentally to changes to the packaging that would result in a
regression as any failures would be evident in
https://salsa.debian.org/mariadb-team/mariadb-10.3/pipelines



More information about the pkg-mysql-maint mailing list