Hi,
> do you have a suggestion on what to do with the "Recommends:
> virtual-mysql-server" (c.f. bug #732879)? Should it still be in use or
> should we have dropped references to those when we switched to
> default-mysql-* in 2016?
I see Bacula currently[1] has:
Package: bacula-director-mysql
Depends: bacula-common-mysql (<< ${source:Version}.1~),
bacula-common-mysql (>= ${source:Version}),
dbconfig-mysql | dbconfig-no-thanks,
default-mysql-client | virtual-mysql-client,
${misc:Depends}
Recommends: default-mysql-server | virtual-mysql-server
Maybe best to change both occurrences of 'default-mysql-server |
virtual-mysql-server' to 'mariadb-server | mysql-server |
virtual-mysql-server' in the next upload? This way Bacula will
continue with both (which upstream currently seems to support[2]) and
in the future, it can drop either MariaDB or MySQL if future versions
diverge significantly and one becomes incompatible.
I don't use Bacula myself and I think you as the maintainer are in the
best position to track what the compatibility with future versions
will be. I see the Bacula Enterprise version has a specific MariaDB
product [3] but I don't know how things will pan out. Current versions
will for sure continue to work, but over the time horizon of Forky and
Forky+1 some divergence relevant to Bacula might occur.
[1] https://salsa.debian.org/bacula-team/bacula/-/blob/master/debian/control
[2]
https://gitlab.bacula.org/bacula-community-edition/bacula-community/-/tree/Branch-15.0/bacula
[3] https://www.baculasystems.com/mariadb-backup-software-tool/
