I got curious, as I can’t replicate the bug! I did an install of cqrlog on my dev machine - it ran first time.
I checked and it has installed mariadb - cqrlog Depends: on default-mysql-client-core and default-mysql-server-core which are metapackages depending on mariadb-client-core and mariadb-server-core. There’s also a Recommends: on default-mysql-server which is a meta package depending on mariadb. I went hunting through https://packages.ubuntu.com/noble/cqrlog and subsequently https://packages.ubuntu.com/noble/default-mysql-server-core to see ubuntu shipping mysql 8 series for these packages. Something didn’t quite add up so I went digging further - it turns out that Ubuntu is shipping mysql-* as mysql-* and Debian is shipping mariadb-* as mysql-*, see: https://salsa.debian.org/mariadb-team/mysql/-/blob/mysql-defaults/debian/master/debian/rules for the specific exception. Maybe this is one the Ubuntu team need to solve? Cheers, -- Hibby Debian Developer Packet Radioist MM0RFN > On 18 Jun 2024, at 13:18, asciiw...@seznam.cz wrote: > > Package: cqrlog > Version: 2.5.2-4 > > CQRLOG seems to be incompatible with mysql-server and require mariadb-server. > There is an "Error during connection to database" message displayed on > startup and application exits. CQRLOG starts working correctly after running > "sudo apt install mariadb-server" (replacing the mysql server with mariadb). > > Downstream Ubuntu issue: > https://bugs.launchpad.net/ubuntu/+source/cqrlog/+bug/1872002 >
