Issue with MariaDB and MySQL updates

1. On CentOS 7 with Custombuild 2, MariaDB gets installed. When I execute a minor version update of MariaDB using custombuild, it shows teh following:

Quote:

---

package MariaDB-compat-5.5.41-1.el7.centos.x86_64 (which is newer than MariaDB-compat-5.5.41-1.el6.x86_64) is already installed

package MariaDB-common-5.5.41-1.el7.centos.x86_64 (which is newer than MariaDB-common-5.5.41-1.el6.x86_64) is already installed

package MariaDB-client-5.5.41-1.el7.centos.x86_64 (which is newer than MariaDB-client-5.5.41-1.el6.x86_64) is already installed

package MariaDB-server-5.5.41-1.el7.centos.x86_64 (which is newer than MariaDB-server-5.5.41-1.el6.x86_64) is already installed

package MariaDB-devel-5.5.41-1.el7.centos.x86_64 (which is newer than MariaDB-devel-5.5.41-1.el6.x86_64) is already installed

package MariaDB-shared-5.5.41-1.el7.centos.x86_64 (which is newer than MariaDB-shared-5.5.41-1.el6.x86_64) is already installed

mv: cannot stat '/etc/systemd/system/mysql.service': No such file or directory

---

It seems MariaDB for CentOS 7 gets installed through CentOS 7 RPM's on new DirectAdmin installations, but subsequent updates come from CentOS 6 RPM's, which then also cause the systemd warning. Why install CentOS 6 RPM's when there are RPM's available for CentOS 7?



2. I'm used to rebuilding PHP after a MySQL upgrade to update the client API, but it seems that in Custombuild 2 (for both MariaDB and MySQL) the PHP rebuild has no effect. The API version stays at mysqlnd 5.0.11. Do we still need to rebuild PHP after MySQL gets upgraded to a newer major version?

Issue with MariaDB and MySQL updates