ti 25. jouluk. 2018 klo 10.17 Sebastiaan Couwenberg (sebas...@xs4all.nl) kirjoitti: > > On 12/25/18 8:57 AM, Otto Kekäläinen wrote: > > Can you please provide an actual pbuilder command or something I can > > copy-paste to reproduce the actual problem (and not just the aptitude > > symptom)? > > Sure: > > sudo cowbuilder --create \ > --distribution=sid \ > --basepath=/var/cache/pbuilder/base-sid.cow > dget -u \ > http://deb.debian.org/debian/pool/main/g/gdal/gdal_2.3.3+dfsg-1.dsc > cd gdal-2.3.3/ > dch -nm "Test rebuild" > pdebuild --pbuilder cowbuilder -- \ > --basepath /var/cache/pbuilder/base-sid.cow/ > > pbuilder will be unstable to install the build dependencies, causing the > configure target to disable MySQL support despite using the --with-mysql > option: > > MySQL support: no
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. > Please also answer my questions: > > > Isn't the appropriate fix to build libmariadbclient-dev-compat from > > the mariadb-10.3 instead of 10.1? Aren't you now transitioning from > > 10.1 to 10.3? And shouldn't mysql-defaults be updated for that too? Of course, in due time, say 2-3 days after mariadb-10.3 is in unstable.
