CQRLOG - open discusion

Mint 18.3 TMySQL56Connection

I get the following error when I try to launch:

Error during connection to database: TMySQL56Connection can not work with the installed MySQL client version: Expected (5.6), got (5.7).

I fixed it by removing libmysqlclient-dev. Cqrlog now starts & works fine (2.3).

Synaptic wont't let me remove it because Cqrlog depends on it. I went to the terminal and ran the following command:
sudo apt-get install libmariadbclient-dev-compat

It executed with some errors but removed libmysqlclient-dev.

Forums: 

dxcc_ref

I tried a filter to see what I could come up with on the DXCC entities I've worked and sent a QSL to but haven't received one back. With the goal being to re-work the ones I need in order to get closer to making Challenge.

What column/field in cqrlog_main is dxcc_ref? I tried this from the SQL console and it fails since there is no column/field named dxcc_ref

select qsodate,time_on,callsign,band, dxcc_ref, lotw_qsls, lotw_qslr from cqrlog_main where lotw_qslr=""

Forums: 

error "risk corruption of data or click cancel"

same error as on raspbian.
in rasbian deleting the file called lotw solves the problem ( until cqrlog creates that map again )....

sadly in debian 8 it looks that cqrlog on startup first recreates the map i delete and then servers me the same error again...

seems this software is all but happy to run on more than one linux distro.
if it stays as unstable i guess i will be better using a maybe not that complete software that is multiplatform ready or at least is willing to run decent on debian as i am no hero with linux and shure not a programmer.

Forums: 

I tried to update version 2.3 on 2.1 my raspberry pi 2B but the result has been catastrophic.

Hello everyone.

I tried to update version 2.3 on 2.1 my raspberry pi 2B but the result has been catastrophic.

When trying to reinstall version 2.1, I no longer recognize the database or allow me to start the program.

Does anyone have a solution?

cqrlog --debug=1

**** DEBUG LEVEL 1 ****

SSL libraries:

Forums: 

QSL needed in WSJT-X CQ monitor

I'm seeing QSL needed in the WSJT-X CQ monitor and I have that band worked and confirmed on LoTW for the DXCC country. So I wondered what logic is use to determine a QSL is needed? I have "include LoTW and eQSL confirmed countries in DXCC" and "use LoTW and eQSL confirmed countries for new country or new band country etc info" checked.

I'm running what I think is the latest version of CQRLOG that I built from source. But it shows version 2.2.0 as the version.

73

Stan
KM4HQE

Forums: 

Running on Fedora 28 requires extra package (for now)

In case anybody is upgrading to Fedora 28:

I'm running CQRLOG on Fedora 28. It's working great now, but I had to add an extra package, mariadb-connector-c-devel to get it working. Without that devel package, CQRLOG gives this error:

. . . . Can not load default MySQL library ("libmysqlclient.so.16" or "libmysqlclient.so").

Installing that devel package provides the libmysqlclient.so library, and happiness ensues.

Forums: 

CQRLOG UPLOAD TO CLUBLOG ISSUE

CQRLOG ONLINE LOG UPDATE TAKES A LONG TIME TO UPLOAD HALF A DOZEN NEW QSOS TO CLUBLOG . IT UPLOADS A CALL, THEN LATER DELETES IT AND THEN DOES AN UPDATED UPLOAD FOR SAME CALL. IT UPLOADS EACH CALL TWICE AND DELETES EACH CALL ONCE. ANYONE KNOW IF THIS IS CORRECT BEHAVIOUR? IS DELETING ANYTHING CORRECT? A MANUAL UPLOAD TO CLUBLOG WITH AN ADIF FILE SEEMS TO WORK MUCH FASTER.
A RECENT UPDATE WITH THE ONLILNE LOG FEATURE OF CQRLOG GAVE THE FOLLOWING RESULT IN THE STATUS BOX. ALL THIS FOR NINE QSOS.

Forums: 

Pages

Subscribe to RSS - CQRLOG - open discusion