It looks like that the upstream Debian package (that is available on CQRLOG
GitHub and Ubuntu PPA) already depends on mariadb since 2021:
https://github.com/ok2cqr/cqrlog/issues/291#issuecomment-770383265
https://github.com/ok2cqr/cqrlog/blob/master/debian/control#L12
Daniel OK2VLK
Christoph Berg wrote:
> (If this were PostgreSQL I would tell you that depending is wrong
> since you can access databases across the network, but I guess mysql
> doesn't work like that in this context.)
yes, in this context it is supposed to use only a local database
because cqrlog spawn a datab
Re: Dave Hibberd
> 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 spec
Hi Dave,
Thanks for the detective work! :-) Interesting! One possible Debian-side
solution could be changing the virtual-mysql-client-core and
virtual-mysql-server-core to mariadb-client-core and mariadb-server-core,
default-mysql-server to mariadb-server and removing the
default-mysql-server-
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
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" (r
6 matches
Mail list logo
