Package: mariadb-server-10.1 Version: 10.1.20-3 Severity: normal Dear maintainers,
On 21/01, a dist-upgrade replaced mariadb 10.0 with 10.1.
It removed mariadb-server-10.0:amd64 (10.0.28-2), mariadb-client-10.0:amd64
(10.0.28-2), mariadb-client-core-10.0:amd64 (10.0.28-2) but just installed
mariadb-client-10.1:amd64 (10.1.20-3, automatic),
mariadb-client-core-10.1:amd64 (10.1.20-3, automatic).
So, no server anymore breaking my dolibarr instance.
Manually installing mariadb-server-10.1 worked like a charm and solved the
dolibarr issue, also replacing mariadb-server-core-10.0 (still installed after
the mariadb-server-10.0 removal) with mariadb-client-core-10.1.
Another strange behavior: this dist-upgrade upgraded the default-mysql-client
from 1.0.1 but removed the
default-mysql-server instead of upgrading it.
=+=+=+=+=
$ env LANG=C apt policy default-mysql-client default-mysql-server
default-mysql-client:
Installed: 1.0.2
Candidate: 1.0.2
Version table:
*** 1.0.2 500
500 http://ftp.be.debian.org/debian testing/main amd64 Packages
100 http://ftp.be.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
default-mysql-server:
Installed: (none)
Candidate: 1.0.2
Version table:
1.0.2 500
500 http://ftp.be.debian.org/debian testing/main amd64 Packages
100 http://ftp.be.debian.org/debian unstable/main amd64 Packages
I hope it will help for future upgrade.
Regards,
Jean-Marc <jean-m...@6jf.be>
P.S. sorry for this incompleted bug report; reportbug does not work anymore on
my system (see bug #848729).
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
pgpY8_9Zz2Iv2.pgp
Description: PGP signature
