The application will not start with MySQL. The referred statement is from a post dated Jan 2009 just before mariadb first appeared. It is my opinion the shortdesc has not been updated either there or on the project's Github repo. The github repo lists a dependency on mariadb specifically [1] as does his control file for self-generated debs [2]. Testing reveals it builds with mysql but does not initialise correctly. Do affected users need to supply logs of the application failing to start on firstrun or similar? [1] https://github.com/ok2cqr/cqrlog?tab=readme-ov-file#dependencies [2] https://github.com/ok2cqr/cqrlog/blob/master/debian/control -- Hibby Debian Developer Packet Radioist MM0RFN On Thu, 29 Aug 2024, at 4:45 PM, Robie Basak wrote: > The upstream website at https://www.cqrlog.com/ says: > >> CQRLOG is an advanced ham radio logger based on MySQL database. > > In Ubuntu, we default to MySQL. I think switching to MariaDB by default > requires exceptional justification, such as the upstream and codebase > very clearly not being able to function with MySQL for a specific, > stated reason. > > If that's the case, please could you provide it? > > Otherwise, "cqrlog needs to depend on mariadb instead of mysql" seems > like an unjustified assumption. > > -- > You received this bug notification because you are a member of Ubuntu > ham developers, which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1872002 > > Title: > [SRU] cqrlog needs to depend on mariadb instead of mysql > > Status in cqrlog package in Ubuntu: > Fix Released > Status in cqrlog source package in Focal: > In Progress > Status in cqrlog source package in Jammy: > In Progress > Status in cqrlog source package in Noble: > In Progress > > Bug description: > [ Impact ] > > cqrlog is unusable for all users who will want to save their data > locally. It will fail to connect with the local database server when > any user tries to use it. > > Whenever any user tries to run the application for the first time, > the user will be asked in a dialogue box: > It seems you are trying to run this program for the first time, are > you going to save data to local machine? > If you say Yes, new databases will be created. This may take a while, > please be patient. > > The user has to click "Yes" to create local database to save data > locally. > > And, then it will fail and a new dialogue box will display: > MySQL could not be started. Please check if the MySQL server is > installed properly. > > Select close. > > Another dialogue box will popup with the error: > Error during connection to database: TMySQL57Connection : Server > connect failed. > > > [ Test Plan ] > > install cqrlog > > run cqrlog from a terminal or from the launcher > Select "Yes" in the dialogue box saying: > It seems you are trying to run this program for the first time, are > you going to save data to local machine? > If you say Yes, new databases will be created. This may take a while, > please be patient. > > if the package is fixed, it will display the window of "Database > connection" with Log001 on the first row. > > Click on "Open log" -> that will display a window of "Changelog" > click "Close" -> that will display the main window of cqrlog. > > Additional question will popup about new QSL managers database and > new DXCC tables. Select "No" for both these question. > > Just to confirm cqrlog is working, enter some dummy data. > > Enter "srutest" in the box labelled "Call", move to the box labelled > Name, and enter "name1". > Click on "Save QSO". > > Close cqrlog window. > > Start cqrlog again. This time it will directly go to the window of > "Database connection" with Log001 on the first row. > Click on "Open log". This time it will directly go to the "cqrlog" > windows and will ask the additional questions about new QSL managers > database and new DXCC tables. > Select No for both. > > Enter "srutest" in the box labelled "Call", move to the box labelled > Name. The name will be autofilled now (taken from the previous > record). And on the top part of the window we should be able to see > the previous entry with timestamp. > > > [ Where problems could occur ] > > There is no change in the code. The only change is in the runtime > dependency to install mariadb instead of mysql and only impacts users > who uses local database. There is very miinimum chance of any > regression due to this change but as a worst case scenario if the > change causes some regression then the users who are using local > database will not see any new issue but will continue to see the same > problem as is now. > > [ Other Info ] > > 1. It has been fixed in the Debian package 2.5.2-5 which has been > synced to Oracular. > 2. As mentioned in the original Bug Description, the issue was caused > by a mismatch of mysql and mariadb. cqrlog needs mariadb to work. > > [ Original Bug Description ] > > > [Impact] > Due to the difference in how Debian and Ubuntu ship the mysql-* > packages, cqrlog has been using mysql-* packages in Ubuntu, which the > package is not compatible with. This means users can successfully > install, but the package fails on launch. > > In Debian, we ship mariadb-* to fulfil mysql-* requirements, but this > is not true with ubuntu [https://salsa.debian.org/mariadb- > team/mysql/-/blob/mysql-defaults/debian/master/debian/rules](Debian > Salsa ) > > [Test Plan] > This fix has already been tested and implemented in Debian upstream. > However was not available in Debian until post-Noble release. > > This has already been tested manually by others, but as soon as a > version with the patch present is available, a user should install the > updated cqrlog package and the appropriate dependencies are installed > so the program should work as usual. > > [Regression Potential] > Extremely limited. Users on systems dating back to pre-jammy have not > been able to use this package without manually installing mariadb, so > no database migration is required unless they are upgrading from before > hirsute, and they would need to migrate regardless of this bug. > > [Where problems could occur] > > Uncertain > > [Other Info] > This is already available in Debian Unstable, and also in Oracular > due to the sync. > > I am the DD responsible for cqrlog in Debian but the SRU process is > unfamiliar to me, so some handholding and sponsorship is required! > > [Original Description] > > Please update the cqrlog package (debian/control) to depend on mariadb > server instead of mysql server. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cqrlog/+bug/1872002/+subscriptions > > > _______________________________________________ > Mailing list: https://launchpad.net/~ubuntu-hams-devel > Post to :