summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Black <daniel@mariadb.org>2022-12-14 19:13:17 +1100
committerAndrew Hutchings <andrew@linuxjedi.co.uk>2022-12-14 20:52:06 +0000
commit9ee055a27f3f0c10fcc5a8b10084fb66147e749d (patch)
tree0fa1478636024c6ee093ab33cee2c2c4a3ff2705
parent40b62a93c6bf0f82c11ac66b19bfec296ef90192 (diff)
downloadmariadb-git-9ee055a27f3f0c10fcc5a8b10084fb66147e749d.tar.gz
Deb: mariadb-server.postinst to use mariadb-install-db
-rw-r--r--debian/mariadb-server-10.5.postinst6
1 files changed, 3 insertions, 3 deletions
diff --git a/debian/mariadb-server-10.5.postinst b/debian/mariadb-server-10.5.postinst
index 13800b7bce2..20604fd6a81 100644
--- a/debian/mariadb-server-10.5.postinst
+++ b/debian/mariadb-server-10.5.postinst
@@ -20,7 +20,7 @@ set -o pipefail
case "$1" in
configure)
- # This is needed because mysql_install_db removes the pid file in /run
+ # This is needed because mariadb-install-db removes the pid file in /run
# and because changed configuration options should take effect immediately.
# In case the server wasn't running at all it should be ok if the stop
# script fails. I can't tell at this point because of the cleaned /run.
@@ -165,12 +165,12 @@ EOF
# initiate databases. Output is not allowed by debconf :-(
# This will fail if we are upgrading an existing database; in this case
- # mysql_upgrade, called from the /etc/init.d/mariadb start script, will
+ # mariadb-upgrade, called from the /etc/mysql/debian-start script, will
# handle things.
# Debian: beware of the bashisms...
# Debian: can safely run on upgrades with existing databases
set +e
- bash /usr/bin/mysql_install_db --rpm --cross-bootstrap --user=mysql \
+ bash /usr/bin/mariadb-install-db --rpm --cross-bootstrap --user=mysql \
--disable-log-bin --skip-test-db 2>&1 | \
$ERR_LOGGER
set -e