[Maria-discuss] Broken MariaDB client ARGGG!!!
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 ... ---- 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. - Jon -- Sent from my Debian Linux workstation -- http://www.debian.org/intro/about Jon Foster JF Possibilities, Inc. jon@jfpossibilities.com 541-410-2760 Making computers work for you!
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 ...
Not related to the backwards compability but for the php imo it's best to build with the native mysqlnd driver (transparently works with mysql/mysqli and pdo extensions). Comes with the php core so one less shared library to rely on. Afaik there should be also php7-mysqlnd package for Debian. rr
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 <mschorm@redhat.com> Antwort an: Development discussions related to Fedora <devel@lists.fedoraproject.org> An: Development discussions related to Fedora <devel@lists.fedoraproject.org> Hello everybody! Since MariaDB 10.2 is finally stable and I resolved all issues that blocked it for Fedora, I'd like to propose an update for Rawhide. Current version of MariaDB: 10.1.24 Update planned to: 10.2.6 (or newer) *This change introduces change of library name from "libmysqlclient.so" to "libmariadb.so".* *There are many dependant packages affected.* The current (optimistic) plan is to deliver the update before Fedora 27 mass rebuild <https://fedoraproject.org/wiki/Releases/27/Schedule> at 12.7.2017. Either the rebuild of all depending packages is inevitable. - We actively track the issue here <https://bugzilla.redhat.com/show_bug.cgi?id=1467297>. There is also a list of affected packages. We have a work repository in COPR, where you can find builds of your packages here <https://copr.fedorainfracloud.org/coprs/g/db-sig/mariadb-10.2/packages/>. We go through all of the issues and we are trying to solve all of those, which are caused by the library change. More information will appear in bugzillas connected to the tracker. Issues are also consulted with MariaDB upstream. I was told, that there should be strong API and ABI compatibility. - Notes: - this means also drop of symlinks to "libmysqlclient.so.18.0.0" library. - the version of the library in MariaDB 10.2.6 is "mariadb.so.3", however in mariadb-connector-c it is only "mariadb.so.2". That should sync in next big update in about a month, I believe. - Feel free to ask any questinos here or in tracker BZ, I'll try to search for all answers.
Hi Jon, This is 2017, and you should use mysqlnd. libmysqlclient is not needed for PHP mysql extensions anymore, hence the error. apt-get php5-mysqlnd should fix the issue. And btw, Deb9 is out :) Best -GL Le lun. 3 juil. 2017 à 22:51, Jon Foster <jon@jfpossibilities.com> a écrit :
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 ...
----
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.
- Jon
-- Sent from my Debian Linux workstation -- http://www.debian.org/intro/about
Jon Foster JF Possibilities, Inc. jon@jfpossibilities.com 541-410-2760 <(541)%20410-2760> Making computers work for you!
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Thanks for the heads up about Deb9. I hadn't seen that yet. Moving to Devuan myself. But all this talk about PHP is off topic. Its just one example. I guess I'll take these comments to mean that the official stance on binary backwards compatibility is that there is less then 0 concern. So I should expect that all compiled software will need to be patched and recompiled potentially with each point release. This is a surprise. Bummer. - Jon On 07/04/2017 03:13 AM, Guillaume Lefranc wrote:
Hi Jon,
This is 2017, and you should use mysqlnd. libmysqlclient is not needed for PHP mysql extensions anymore, hence the error. apt-get php5-mysqlnd should fix the issue.
And btw, Deb9 is out :)
Best -GL
Le lun. 3 juil. 2017 à 22:51, Jon Foster <jon@jfpossibilities.com <mailto:jon@jfpossibilities.com>> a écrit :
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 ...
----
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.
- Jon
-- Sent from my Debian Linux workstation -- http://www.debian.org/intro/about
Jon Foster JF Possibilities, Inc. jon@jfpossibilities.com <mailto:jon@jfpossibilities.com> 541-410-2760 <tel:%28541%29%20410-2760> Making computers work for you!
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss <https://launchpad.net/%7Emaria-discuss> Post to : maria-discuss@lists.launchpad.net <mailto:maria-discuss@lists.launchpad.net> Unsubscribe : https://launchpad.net/~maria-discuss <https://launchpad.net/%7Emaria-discuss> More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
-- Sent from my Debian Linux workstation -- http://www.debian.org/intro/about Jon Foster JF Possibilities, Inc. jon@jfpossibilities.com 541-410-2760 Making computers work for you!
Am 04.07.2017 um 19:08 schrieb Jon Foster:
Thanks for the heads up about Deb9. I hadn't seen that yet. Moving to Devuan myself.
But all this talk about PHP is off topic. Its just one example. I guess I'll take these comments to mean that the official stance on binary backwards compatibility is that there is less then 0 concern. So I should expect that all compiled software will need to be patched and recompiled potentially with each point release. This is a surprise.
how is that a surprise? Oracle even did manage it two times that they broke ABI compatibility without a soname bump and than *after* the GA release they introduced the soname bump that's what point releases are for but i find that whole rename to libmariadb commplete nonsense because the whole world needs to make a dance around this in tons of projects while a smart transition would have provided a compatibilit layer so that a simple re-compile is enough
Hi, Jon! Generally, if you want to have a bug fixed, you'll have better chances at jira.mariadb.org, than on the mailing list. This particular bug was filed as https://jira.mariadb.org/browse/MDEV-12889 and it's already fixed, the fix will be released in 10.2.7. The release schedule is also available at jira.mariadb.org. On Jul 03, Jon Foster wrote:
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 ...
----
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.
Regards, Sergei Chief Architect MariaDB and security@mariadb.org
participants (5)
-
Guillaume Lefranc -
Jon Foster -
Reindl Harald -
Reinis Rozitis -
Sergei Golubchik