THIS IS A MASS FILING TO ALL PACKAGE WITH A DEPEND ON virtual/mysql As was announced on the gentoo-dev-announce mailing list[1], virtual/mysql is no longer viable to depend on providing the client libraries or the mysql_config tool. Most uses of DEPEND="virtual/mysql" (or conditionals based upon it) will not work in the future. If this package (optionally) depends on libmysqlclient.so* or mysql_config for building, you will need to have dev-db/mysql-connector-c as the DEPEND/RDEPEND. If this package (optionally) depends on libmariadb.so* or mariadb_config for building, you will need to have dev-db/mariadb-connector-c as the DEPEND/RDEPEND. If this package requires the server running locally, virtual/mysql is acceptible for RDEPEND and only in DEPEND when tests demand it. The rare exception when server only files are required at build time should you keep a compatible server listed. After 60 days, roughly mid-October 2018, remaining packages will be forcefully changed to mysql-connector-c with little or no testing. The server packages will drop their compatibility DEPEND shortly after. [1] https://archives.gentoo.org/gentoo-dev-announce/message/618f39bce863911d8955ee9f83636ca4
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f3e43de56a3800cfac5cdaa3a3267ba9b587953d commit f3e43de56a3800cfac5cdaa3a3267ba9b587953d Author: Michael Orlitzky <mjo@gentoo.org> AuthorDate: 2018-09-22 23:53:01 +0000 Commit: Michael Orlitzky <mjo@gentoo.org> CommitDate: 2018-09-23 01:27:06 +0000 net-analyzer/nagios-plugins: replace virtual/mysql dependency. The nagios-plugins build system (m4/np_mysqlclient.m4) looks for the mysql_config program, and so per bug 665952, we should be depending on dev-db/mysql-connector-c instead of virtual/mysql at build time. This has the -- as far as I can tell, correct -- side effect of removing the MySQL server stuff from RDEPEND. Bug: https://bugs.gentoo.org/665952 Package-Manager: Portage-2.3.40, Repoman-2.3.9 .../nagios-plugins/nagios-plugins-2.2.1-r3.ebuild | 118 +++++++++++++++++++++ 1 file changed, 118 insertions(+)
I left this bug open because the new ebuild isn't stable yet, and the old ones still have the incorrect dependency. If the old ebuilds aren't gone by the time you decide to pull the trigger, we could just mark the new -r3 ebuild stable on all arches. That will have the same end result, but will make people rebuild to get the new dependency.
I just removed the old ebuilds (commit ec0cf769285f14f04).