TMySQL57Connection problem: Expected (5.7), got (6.1.11)

6 posts / 0 new
Last post
dl3dth
TMySQL57Connection problem: Expected (5.7), got (6.1.11)

Hi,

Since the last upgrade on my Gentoo system I can't use cqrlog anymore. I get the following output at the command line:

Cqrlog Ver:2.3.0 (001) Date:2018-06-17
**** DEBUG LEVEL 1 ****

SSL libraries:
/usr/lib64/libssl.so.1.0.0
/usr/lib64/libcrypto.so.1.0.0
Loading libmysqlclient: /usr/lib64/libmysqlclient.so
**************************
MySQL version: 6.1
**************************
**********************************
MySQL version assigned: 6.1
**********************************
Loaded 121329 LoTW users
Loaded 117362 eQSL users
Loaded 39622 SCP calls
*
User home directory: /home/tom/
Program home directory: /home/tom/.config/cqrlog/
Data directory: /home/tom/.config/cqrlog/database/
Memebers directory: /home/tom/.config/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/
TConnection to MySQL: 6.1
*
56 us states loaded
/usr/sbin/mysqld --defaults-file=/home/tom/.config/cqrlog/database/mysql.cnf --datadir=/home/tom/.config/cqrlog/database/ --socket=/home/tom/.config/cqrlog/database/sock --port=64000
Trying to connect to database
2018-10-03 19:24:32 139832652863296 [Note] /usr/sbin/mysqld (mysqld 10.2.17-MariaDB) starting as process 1891 ...
TMySQL57Connection can not work with the installed MySQL client version: Expected (5.7), got (6.1.11).

I had it working during the last month with mariadb-10.1.31-r1, but this version was now removed and it is also not possible to use the "client-libs" useflag anymore. The problem seems to be related to the way how Lazarus/FPC checks for the mysqlconnector version (here: mysql-connector-c-6.1.11, which is the latest version available).
Any idea how to fix this?

Thanks and best 73,
Tom, DL3DTH

n4ogw
I have exactly the same

I have exactly the same problem- I am also using Gentoo.

Tor N4OGW

n3fv
bug logged, workaround

FYI - Gentoo bug for this is logged as: https://bugs.gentoo.org/669712

I'm working with the mysql maintainers to ID the best fix. A temporary workaround is to unmask and enable the client-libs USE flag:
echo "dev-db/mysql -client-libs" > /etc/portage/profile/package.use.mask/cqrlog
echo "dev-db/mysql client-libs" > /etc/portage/package.use/cqrlog
emerge -1 mysql

(I think it will work fine if you swap mariadb for mysql if that is your preference. Also, the "-" in the first line is intentional as we're removing the mask from the profile.) Expect to have to run emerge @preserved-rebuild. This is all going from memory so I might have missed a step.

Once I hear back from the mysql devs I'll probably update the ebuild with an appropriate dependency so that this is all automatic. Either that or the package will have to be temporarily masked until the issues with mysql-connector-c are sorted out, since we can't have an unmasked package depending on masked flags. The mask comment would a link to the workaround for anybody who runs into it.

I suggest anybody interested add themselves to the bug CC and you'll know what is going on. Long-term the preferred config is to not use client-libs, so I want to fix this right. But, at least you won't be dead in the water...

n3fv
This issue has been fixed by

This issue has been fixed by backporting upstream commit 044d4190966267aa285d3317e02f6f57ef4b25c4 on Gentoo - the package has been updated. If you implemented any workarounds I recommend removing those lines so that portage will return your config to normal.

dl3dth
Nice, many thanks!

Hi Richard,
many thanks for your input. With your help I was able to get cqrlog back to work - at least temporary. It was not that simple as in your post because I also had to modify the mariadb-ebuild (to remove the clientlib-patch) - but finally it works now! I really like Gentoo with all these possibilities and learned something new this time...
I've also seen the last entries in bugzilla and will test the patched cqrlog as soon as possible.
Many thanks again!

Best regards,
Tom, DL3DTH

73 de

Tom, DL3DTH

n4ogw
Thanks, this fixed my problem

Thanks, this fixed my problem.

Tor
N4OGW