Your message dated Thu, 20 Jun 2024 22:34:42 +0000 with message-id <E1sKQMc-00Cy96-P9@fasolo.debian.org> and subject line Bug#1073790: fixed in cqrlog 2.5.2-5 has caused the Debian Bug report #1073790, regarding cqrlog should depend on mariadb instead of mysql to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1073790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073790 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: <submit@bugs.debian.org>
- Subject: cqrlog should depend on mariadb instead of mysql
- From: <asciiwolf@seznam.cz>
- Date: Tue, 18 Jun 2024 14:18:24 +0200 (CEST)
- Message-id: <[🔎] 2Rx.46OFn.sHpvO5{peE.1cSNiG@seznam.cz>
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
--- End Message ---
--- Begin Message ---
- To: 1073790-close@bugs.debian.org
- Subject: Bug#1073790: fixed in cqrlog 2.5.2-5
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Thu, 20 Jun 2024 22:34:42 +0000
- Message-id: <E1sKQMc-00Cy96-P9@fasolo.debian.org>
- Reply-to: Dave Hibberd <hibby@debian.org>
Source: cqrlog Source-Version: 2.5.2-5 Done: Dave Hibberd <hibby@debian.org> We believe that the bug you reported is fixed in the latest version of cqrlog, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1073790@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dave Hibberd <hibby@debian.org> (supplier of updated cqrlog package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Thu, 20 Jun 2024 23:12:05 +0100 Source: cqrlog Architecture: source Version: 2.5.2-5 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org> Changed-By: Dave Hibberd <hibby@debian.org> Closes: 1073790 Changes: cqrlog (2.5.2-5) unstable; urgency=medium . * Team upload. . * Migrate to mariadb, in line with Upstream practice and Ubuntu request - Closes: #1073790 * d/control - Change default-mysql-server-core to mariadb-server-core - Change default-mysql-client-core to mariadb-client-core - Drop virtual mysql packages - Bump standards to 4.7.0 Checksums-Sha1: 4d8a39ed98372cd8057482f69d7872fa153769dc 1864 cqrlog_2.5.2-5.dsc 192c96b7932218cdfa5b8ac595054b0da8ce653c 12740 cqrlog_2.5.2-5.debian.tar.xz 20b6af2a66d1e2ca5ff97d2d04cfb77faa261a4e 12764 cqrlog_2.5.2-5_arm64.buildinfo Checksums-Sha256: 4b57df5e625a36d8cbeca7fbf5c518b631fc1ff6c359d745d6fe203e70fcf108 1864 cqrlog_2.5.2-5.dsc 53bae3d9b77968f12c6972fa7ffebd7e524b984d7e9394c20456124a5f636435 12740 cqrlog_2.5.2-5.debian.tar.xz 1e86f12b672963d436c425324ff81b1ef2e2f7079ab27d99fe690381d6fef68e 12764 cqrlog_2.5.2-5_arm64.buildinfo Files: 12894d792645266d090fa72b12b79e09 1864 hamradio optional cqrlog_2.5.2-5.dsc 97aa8513ee11516c0d33c49d5f382e29 12740 hamradio optional cqrlog_2.5.2-5.debian.tar.xz 7f6ba43e9e0359945e727b4d3a368cb5 12764 hamradio optional cqrlog_2.5.2-5_arm64.buildinfo -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEXk9UUZPolpyKWbgKA6H7ehkEdxsFAmZ0q5YACgkQA6H7ehkE dxvqBQgAjFRPTnbi1TASQg6CquPEZkpLacRF0V0o4aBYEKPnvVHy7nHPPZgh/ZMs 0xB1ka8A5OQca5R3ZFBz8RixRzfoNRxVR7qVpHT5F0f8ClhF7tkGDKi9Vb8v62/3 xtK+YxPtfFxb6GPkIw8KyorAxGrhGqhNP9/NtHrN982Xv4UxBhFWqO70Mxb/ZI7r 3blR4mq5zSGr7rvkqa/csC4hGKntpuwixhYd08NUzmD4t14H5XInZpXZnQ2F/3rg z1oTYqUDjtP6pP7MR9opTXYtx32tSbf35nEeJ24kTlhokZ5me481wJXKSXt9xpC7 uBLKrnq1Nnk+HVWy5cVjcpDBm7M6tg== =+A+t -----END PGP SIGNATURE-----Attachment: pgpMirGYd7WD9.pgp
Description: PGP signature
--- End Message ---