After change of datadir in /etc/mysql/my.cnf it's not possible to install the initial database: emerge --config mysql Configuring pkg... * MySQL MY_DATADIR has changed * from /var/lib/mysql * to /data/mysql * Please provide a password for the mysql 'root' user now, in the * MYSQL_ROOT_PASSWORD env var or through the /root/.my.cnf file. * Avoid ["'\_%] characters in the password > * Retype the password > * Command: '/usr/share/mysql/scripts/mysql_install_db' '--basedir=/usr' --log-warnings=0 --loose-skip-grant-tables --loose-skip-host-cache --loose-skip-name-resolve --loose-skip-networking --loose-skip-slave-start --loose-skip-innodb --loose-skip-ssl --loose-skip-log-bin --loose-skip-relay-log --loose-skip-slow-query-log --loose-skip-external-locking --loose-skip-log-slave-updates --user=mysql * ERROR: dev-db/mysql-5.5.32::gentoo failed (config phase): * MySQL databases not installed * * Call stack: * ebuild.sh, line 93: Called pkg_config * environment, line 3490: Called mysql-v2_pkg_config * environment, line 3144: Called die * The specific snippet of code: * [[ -f "${ROOT}/${MY_DATADIR}/mysql/user.frm" ]] || die "MySQL databases not installed"; * * If you need support, post the output of `emerge --info '=dev-db/mysql-5.5.32::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-db/mysql-5.5.32::gentoo'`. * The complete build log is located at '/var/tmp/portage/dev-db/mysql-5.5.32/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-db/mysql-5.5.32/temp/environment'. * Working directory: '/usr/lib64/portage/pym' * S: '/var/tmp/portage/dev-db/mysql-5.5.32/work/mysql-5.5.32' Reproducible: Always Steps to Reproduce: 1. change datadir to somewhere else 2. emerge --config mysql 3. Actual Results: emerge fails like shown above Expected Results: Install of the initial database Looks like this is still the same as in bug 453480 I think. Can I help something to fix this? Are all others running there mysql dbs under /var/lib/mysql?
Yes, they appear the same; don't worry about it being filed as a duplicate, the maintainers will be informed about this and thus are reminded to look into. *** This bug has been marked as a duplicate of bug 453480 ***
