Your message dated Tue, 8 Jan 2019 22:43:01 +0100 with message-id <0196760c-c34b-cbdf-c60b-859d1fc74...@debian.org> and subject line Re: mariadb-10.3: libmariadb3 causes removal of default-libmysqlclient-dev has caused the Debian Bug report #917075, regarding mariadb-10.3: libmariadb3 causes removal of default-libmysqlclient-dev to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: mariadb-10.3 Version: 1:10.3.11-1 Severity: serious Justification: makes the package in question unusable or mostly so Control: affects -1 src:gdal Dear Maintainer, libmariadb3 (1:10.3.11-1) conflicts with libmariadbclient18 (<< 10.2.0) which causes default-libmysqlclient-dev to be removed. When building gdal in unstable now, MySQL support is disabled because libmariadbclient-dev cannot be installed: The following packages have unmet dependencies: libmariadbclient-dev : Depends: libmariadbclient18 (= 1:10.1.37-3) but it is not going to be installed The following actions will resolve these dependencies: Install the following packages: 1) libmariadb-dev [1:10.3.11-1 (unstable)] 2) libmariadb3 [1:10.3.11-1 (unstable)] 3) mariadb-common [1:10.3.11-1 (unstable)] 4) mysql-common [5.8+1.0.4 (unstable)] Keep the following packages at their current version: 5) libmariadbclient-dev [Not Installed] Please fix the incompatibility with the default-* packages. Kind Regards, Bas
--- End Message ---
--- Begin Message ---On Sat, 5 Jan 2019 13:36:40 +0100 Sebastiaan Couwenberg <sebas...@xs4all.nl> wrote: > You can also close this issue as it was fixed by the mysql-defaults > changes mentioned previously. I just tested rebuilding all mariadb rdepends in a sid pbuilder environment and did not encounter any installability problems. Closing this now. Andreas
--- End Message ---
