Am 03.07.2017 um 22:51 schrieb Jon Foster:
I'm constantly astounded at the extreme cavalier attitude that MySQL/MariaDB has had towards backwards compatibility for the nearly two decades I've worked with it. Its like you hate the developers that use your stuff. What's up with this?!?!
I decided I better install the latest updates to my Deb7 64bit MariaDB install. WTF! Now all of my PHP apps are griping about:
symbol client_errors, version libmysqlclient_18 not defined in file libmysqlclient.so.18 ...
blame the one which links PHP in 2017 still against libmysql at all http://php.net/manual/de/book.mysqlnd.php however, if you upgrade libraries it's pretty normal that you have to rebuild consumers of that libraries and hence you have build/staging/test systems before deployment - do you?
And it was working so well ten minutes ago. 10.2 even did away with the previous gripes from v10.1. :-/ But with the update to 10.2.6+maria~wheezy of the client libraries from your Debian repositories my clients' sites are down.
Please fix. I'll find someway to install older functional code again while i hate this useless rename and have currently no idea how to bootstrap the upgrade to 10.2 for other software than PHP and why it not simply has symlinks to satisfy already compiled dependencies... upgrade to 10.2 within a dist-upgrade is a nogo
if you just jump blindly to a new major release, don't test anything,
don't inform yourself and mix distribution and other packages and to
make it worst throw self compiled stuff not properly packaged in the mix
you are the one to blame and nonody else
-------- Weitergeleitete Nachricht --------
Betreff: [SONAME change] MySQL, MariaDB
Datum: Mon, 3 Jul 2017 15:12:13 +0200
Von: Michal Schorm