Re: Proposing the retirement of default-mysql-* metapackages for Forky

Hi,

> > I want to start a discussion about dismantling the
> > default-mysql-server and default-mysql-client virtual packages for
> > Forky (Debian 14), and transitioning the archive to point explicitly
> > to mariadb-server and mariadb-client.
> >
> > To be clear: this change is proposed strictly for Forky and won't
> > affect any older or currently supported stable releases.
>
> Are there any implication for users upgrading from trixie to forky? i
> think the answer is no, since default-mysql-server only depends on
> mariadb in trixie (anyone who wants mysql has already worked out how to
> get it elsewhere).
>
> So the release notes would just have a small entry in the equivalent to
> https://www.debian.org/releases/trixie/release-notes/issues.html#obsolescence-and-deprecation
> saying that the meta-package is deprecated and to install mariadb-*
> directly?

There should not be any issues when upgrading to Forky - the
metapackage just becomes obsolete and is replaced by a direct
dependency.

I plan to do a mass bug filing tomorrow on these:

boinc: libboinc-app-dev
cl-sql: cl-sql-mysql
diaspora-installer/contrib: diaspora-installer-mysql
gdal: libgdal-dev
kannel: kannel-dev
lcmaps-plugins-jobrep: lcmaps-plugins-jobrep-admin
mailutils: libmailutils-dev
mysql-ocaml: libmysql-ocaml-dev
opendnssec: opendnssec-enforcer-mysql
parser-mysql: parser3-mysql
poco: libpoco-dev
rust-mysqlclient-sys: librust-mysqlclient-sys-dev
vtk9: libvtk9-dev