Comment 16 for bug 1872002

HI there!

> On 29 Aug 2024, at 17:31, Robie Basak <email address hidden> wrote:
>
> On Thu, Aug 29, 2024 at 04:08:04PM -0000, Dave Hibberd wrote:
>> The application will not start with MySQL.
>
> If it works with MariaDB but not MySQL, that doesn't necessarily mean
> that it only supports MariaDB, or that there's not just a bug that needs
> fixing to keep it compatible with both.

The best I have is upstream saying it depends on mariadb not mysql[1] since version 2.5.

I really don’t have time or knowledge to dig in to why this is the case, until this came around it was my understanding that they were compatible and I’ve followed upstream’s precedent in the Debian package.

>
>> Do affected users need to supply logs of the application failing to
>> start on firstrun or similar?
>
> No. That's a given. What I'd like to see is an explanation of why the
> package cannot be fixed to work with MySQL properly.
>

The problem that falls out of all this is that based on this bug when it got sent upstream to debian and that justification, I’ve moved the dependency to mariadb[2], not the virtual package.
This has already been mirrored in the next release - granted, I’ve not checked if your mirror will automatically check

If the preference in Ubuntu is to keep using mysql with this package, someone’s going to need to revert the change in the package that’s been mirrored for to not only depend on mysql and investigate why it’s not working or work with upstream to understand why they’re choosing to depend on mariadb instead.

Cheers!

[1] https://github.com/ok2cqr/cqrlog/issues/291#issuecomment-770383265
[2] https://salsa.debian.org/debian-hamradio-team/cqrlog/-/blob/master/debian/control?ref_type=heads#L36

--
  Hibby
  Debian Developer
  Packet Radioist
  MM0RFN