Description of problem: The current version of cqrlog provided with fedora 21 is 1.8.1. This does not seem to work anymore with the mariadb version in F21. Whenever one tries to start cqrlog, you get a dialog stating: Error during connection to database: TMySQL55Connection can not work with the installed MySQL client version: Expected (5.5), got (10.0.14-MariaDB). Version-Release number of selected component (if applicable): And the program is unable to connect to the database. How reproducible: Everytime you start cqrlog. Steps to Reproduce: 1. Install cqrlog 2. Try to start it 3. Actual results: Unable to connect to database. Expected results: It should connect to the database as before. Additional info: I don't know if this would be fixed in the new cqrlog versions but these apparently are pending for the new version free pascal & lazarus.
I did some poking around the cqrlog source. Here is why it does not work: 1) Free pascal compile 2.6.x version sql routines cannot deal with the new mariadb version. You would either patch 2.6.x to accept the current mariadb version number and proceed or use 2.7.x (experimental). 2) The version number returned by the new mariadb server differs from the usual format major version.minor version. cqrlog uses the currency datatype for version numbers and this non-standard version string does not fit into that. For that reason, one has to change the source code such that it either: 1) only uses 5.6 stuff or 2) uses a different datatype for storing the version string and making appropriate comparisons (the right way to do it). So, for short, the new mariadb is incompatible with cqrlog (or with free pascal for that matter). I did mangage to procude a working version of cqrlog after doing the above. However, fpc 2.7.x has some stability issues and I need to look how to get the mariadb patch into fpc.2.6.4. By the way, fedora is still stuck at 2.6.2 (also new lazarus is needed). Those who use fedora for ham radio should NOT upgrade to 21 until this one is sorted out.
I must be still asleep, change: You would either patch 2.6.x to accept the current mariadb version number and proceed or use 2.7.x (experimental). to You should either patch 2.6.x to accept the current mariadb version number or use 2.7.x (experimental), which already includes this patch.
Some good news. The cqrlog authors have developed a workaround for the mariadb server response issue. The new version is already in the git repository and I have verified that it works correctly. This will compile only with fpc 2.6.4 (and new lazarus) and not with 2.6.2. So, *please* update fpc and lazarus packages for fedora so that we can get cqrlog working again.
OK, new cqrlog version (1.8.3) is available and it contains the mariadb fix. So, new fpc, lazarus and cqrlog are need in order to get cqrlog to work on F21.
Could someone please look into this? This is the single most important application for ham radio. We will have an installfest geared toward hams soon and I would have to switch to some other distro just because of things are lagging behind.
The lazarus and fpc issues are being tracked separately so I added them as "see also" instead of blockers. I haven't had much time to deal with this and ideally fpc and lazarus would be updated but if it comes down to it I may setup a COPR repository as a stop-gap.
Ok, building what should have been a minor update (fpc 2.6.2 -> 2.6.4) was problematic. Seeing how it builds I really wish cqrlog was written in C :) After that lazarus and cqrlog were easy, you can enable the COPR repository below: https://copr.fedoraproject.org/coprs/hobbes1069/cqrlog/ This is intended to be a temporary fix, hopefully the fpc and lazarus maintainers will eventually get the packages updated.
Works great - thank you!!!!
I noticed that only intel binaries are available. All the components compile on ARM as well and some people were asking for a working cqrlog for this architecture. Any chance you could compile this for ARM too?
Unfortunately COPR does not provide an ARM target so there's not much I can do.
Ok, I'm going to go ahead and close this one. Once the fpc and lazarus issues are fixed, this one should be a non-issue.