mariadb: Deprecated program name

[codebymikey]

The default script makes use of mysql specific scripts.

However mariadb has its own version, and recommends using it instead. So there should be support for making use of the mariadb versions of the scripts so that errors aren't added by default.

Sample output when mysql or mysqldump is called on MariaDB 11.4:

mysqldump: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-dump' instead
mysql: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb' instead

[tzumbrunnen]

The script hardcodes the MySQL binary names when building its three core tool variables:

export MYSQLDUMP="mysqldump --user=... --password=... --host=..."
export MYSQLSHOW="mysqlshow --user=... --password=... --host=..."
export MYSQL="mysql    --user=... --password=... --host=..."

MariaDB 11.4+ deprecated mysqldump, mysqlshow, and mysql as compatibility shims in favour of the native binaries mariadb-dump, mariadb-show, and mariadb. Since every call to $MYSQLDUMP, $MYSQLSHOW, and $MYSQL throughout the script inherits these hardcoded names, every invocation emits a deprecation warning to stderr — polluting backup logs with noise.

---

Why the existing sed-based workaround isn't good enough

A community-posted gist patches the installed binary on disk using sed replacements. This approach has several problems:

• Breaks on plain MySQL hosts where mariadb-dump doesn't exist
• Must be re-applied after every package upgrade
• The \bmysql\b word-boundary replacement is fragile and hits unintended matches (e.g. path components like /usr/bin/mysql/ or variable names containing mysql)

---

Proposed Fix

Part 1 — Runtime auto-detection in automysqlbackup

Before the three export lines are built, add a detection block:

# Detect MariaDB vs MySQL binary names
_DUMP_BIN="${CONFIG_mysql_dump_bin:-}"
_MYSQL_BIN="${CONFIG_mysql_bin:-}"
_SHOW_BIN="${CONFIG_mysqlshow_bin:-}"

if [[ -z "$_DUMP_BIN" ]]; then
    if command -v mariadb-dump &>/dev/null; then
        _DUMP_BIN="mariadb-dump"
        _MYSQL_BIN="mariadb"
        _SHOW_BIN="mariadb-show"
    else
        _DUMP_BIN="mysqldump"
        _MYSQL_BIN="mysql"
        _SHOW_BIN="mysqlshow"
    fi
fi

Then update the three export lines to use these variables:

export MYSQLDUMP="${_DUMP_BIN} --user=${CONFIG_mysql_dump_username} --password=${CONFIG_mysql_dump_password} --host=${CONFIG_mysql_dump_host}"
export MYSQLSHOW="${_SHOW_BIN} --user=${CONFIG_mysql_dump_username} --password=${CONFIG_mysql_dump_password} --host=${CONFIG_mysql_dump_host}"
export MYSQL="${_MYSQL_BIN} --user=${CONFIG_mysql_dump_username} --password=${CONFIG_mysql_dump_password} --host=${CONFIG_mysql_dump_host}"

Part 2 — Config overrides in automysqlbackup.conf

Some systems have both MySQL and MariaDB clients installed, or binaries in non-standard paths. Three optional config knobs should be added:

# Override the client binary names if auto-detection produces wrong results.
# When unset, the script auto-detects: mariadb-dump/mariadb/mariadb-show on MariaDB,
# mysqldump/mysql/mysqlshow on MySQL.
#CONFIG_mysql_dump_bin=''
#CONFIG_mysql_bin=''
#CONFIG_mysqlshow_bin=''

---

Files to change

File	Change
automysqlbackup	Add runtime binary detection block before the export lines
automysqlbackup.conf	Add three optional CONFIG_mysql_*_bin override variables
install.sh	Echo the new config options during install
README.md	Document MariaDB binary detection and note that mysql_config_editor is not available on MariaDB

---

Compatibility

This approach is fully backward-compatible:

• Plain MySQL host — mariadb-dump is not found, old binary names are used unchanged
• MariaDB 11.4+ — native binaries are picked up automatically, deprecation warnings disappear
• Edge cases — the new CONFIG_mysql_*_bin config variables allow manual override without touching the script

[codebymikey]

That's not enough by itself, there's code further down that also checks the MySQL version by using the NODOT_VER variable.

So will also need to be updated.

I have code locally that should address this, but need to test first before proposing a PR.

[mape2k]

I've submitted a pull request using the idea from @tzumbrunnen .