• Bug#1073790: cqrlog should depend on mariadb instead of mysql

    From [email protected]@1:229/2 to All on Tue Jun 18 14:30:02 2024
    XPost: linux.debian.bugs.dist

    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

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Dave Hibberd@1:229/2 to All on Tue Jun 18 22:20:03 2024
    XPost: linux.debian.bugs.dist
    From: [email protected]

    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, [email protected] 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



    <html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I got curious, as I can’t replicate the bug! I did an install of
    cqrlog on my dev machine - it ran first time.&nbsp;<div><br></div><div>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.&nbsp;</div><div>There’s also a Recommends: on default-mysql-server which is a meta package depending on mariadb.</div><div><br></div><div>I went hunting through&nbsp;<a href="https://packages.ubuntu.com/noble/cqrlog">https://packages.
    ubuntu.com/noble/cqrlog</a>&nbsp;and subsequently&nbsp;<a href="https://packages.ubuntu.com/noble/default-mysql-server-core">https://packages.ubuntu.com/noble/default-mysql-server-core</a>&nbsp;to see ubuntu shipping mysql 8 series for these packages.</
    <div><br></div><div>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:</div><div><a href="https://salsa.debian.org/mariadb-team/mysql/-/
    blob/mysql-defaults/debian/master/debian/rules">https://salsa.debian.org/mariadb-team/mysql/-/blob/mysql-defaults/debian/master/debian/rules</a>&nbsp;for the specific exception.<br></div><div><br></div><div>Maybe this is one the Ubuntu team need to solve?
    </div><div><br></div><div>Cheers,</div><div><br></div><div><div>
    <meta charset="UTF-8"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-
    decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>--</div><div>&nbsp; Hibby<br>&nbsp;&nbsp;Debian Developer<br>&nbsp;&nbsp;Packet Radioist<br>&nbsp;&nbsp;MM0RFN</div></div>
    </div>

    <div><br><blockquote type="cite"><div>On 18 Jun 2024, at 13:18, [email protected] wrote:</div><br class="Apple-interchange-newline"><div><div>Package: cqrlog<br>Version: 2.5.2-4<br><br>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).<br><br>
    Downstream Ubuntu issue: https://bugs.launchpad.net/ubuntu/+source/cqrlog/+bug/1872002<br><br></div></div></blockquote></div><br></div></body></html>

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From [email protected]@1:229/2 to All on Wed Jun 19 15:40:01 2024
    XPost: linux.debian.bugs.dist

    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-core dependency. That would cause dependency issues on systems that already have mysql-server-8 installed, but since CQRLOG does not seem to work with mysql anymore (only with mariadb), it should not be a big problem, at
    least in my opinion.

    The other possible solution would be - as you suggested - to patch this in Ubuntu. However, I am not sure whether the CQRLOG package has any Ubuntu maintainers and also it would probably break auto-sync of the package from Debian.

    Anyway, I will also comment on this in the original Ubuntu Launchpad ticket and we'll see if there is any progress. :-)

    Thanks!

    Regards,
    Daniel (OK2VLK)

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Christoph Berg@1:229/2 to All on Wed Jun 19 15:50:01 2024
    XPost: linux.debian.bugs.dist
    From: [email protected]

    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 specific exception.

    Ubuntu seems to have been switching back and forth between the two
    mysql flavors - I've given up on tracking that in the mysql-touching
    PostgreSQL packages (postgresql-mysql-fdw, ...).

    If cqrlog only works with one of them, we should depend directly on
    that server instead of using the default-mysql-whatever meta packages.

    (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.)

    Christoph

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From [email protected]@1:229/2 to All on Thu Jun 20 19:40:01 2024
    XPost: linux.debian.bugs.dist

    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

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Daniele Forsi@1:229/2 to Christoph Berg on Wed Jun 19 17:00:01 2024
    XPost: linux.debian.bugs.dist
    From: [email protected]

    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 database server rooted in the home directory of
    the user and this doesn't seem to be configurable in the preferences.

    When running cgrlog I see this with "ps":
    /usr/sbin/mysqld
    --defaults-file=/home/ham/.config/cqrlog/database/mysql.cnf --datadir=/home/ham/.config/cqrlog/database/ --socket=/home/ham/.config/cqrlog/database/sock --port=64000

    --
    73 de IU5HKX Daniele

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)