Hi, > > By announcing this abstraction as deprecated now, we give maintainers > > plenty of time to update their Depends and Build-Depends to point > > explicitly to MariaDB. The whole metapackage can be removed once zero > > packages depend on it in Forky+1 or +2. Users who require Oracle MySQL > > can continue to use third-party repositories, but our archive > > packaging should honestly reflect what Debian actually ships and > > supports in main. > > > > Let me know if you see any concrete blockers for your packages. ... > Can you confirm that no application will be compatible with one or the > other? Like, will my applications stop working with mysql, somehow? > > If not, I don't see the point.
I can't definitively confirm the compatibility of the latest MySQL/MariaDB versions with the larger ecosystem. I need help from maintainers to track what their specific upstreams are doing. Your current apps will certainly not stop working with the current versions of MySQL/MariaDB. Some apps are known to have started breaking with MySQL 8.4 (e.g. WordPress) but I am not aware of any definitive list. Both MariaDB 12.3. and MySQL 9.4 was just released last month. If you try using your apps with them you will discover if there are issues. I am happy to hear your about your findings if you do such testing. I also suggest you check out https://github.com/mysql/mysql-server/graphs/contributors?from=5%2F25%2F2024 to see how development activity is slowing down and note that out of the top-6 developers only two still seem to be employed by Oracle. Draw your own conclusions about the overall situation and what is likely to happen by the time Forky is released and in production, and how it might affect your apps.
