From dc6a219bbaf2812dcfdb9f83c03b32af7a1d5b44 Mon Sep 17 00:00:00 2001 From: MickLesk <47820557+MickLesk@users.noreply.github.com> Date: Fri, 13 Nov 2026 16:16:41 +0100 Subject: [PATCH] Use MySQL's current signing key and the trixie suite The RPM-GPG-KEY-mysql-2023 file expired on 2025-10-22, so every setup_mysql on Debian 13 failed at apt update. Oracle serves the same key with its expiry extended as RPM-GPG-KEY-mysql-2025. Debian 13 also took bookworm's packages, which depend on libaio1; Oracle publishes a trixie suite now. MySQL 8.4.13 installs again. --- lib/db.func | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/lib/db.func b/lib/db.func index f5d2473..14c3ce1 100644 --- a/lib/db.func +++ b/lib/db.func @@ -1119,7 +1119,9 @@ setup_mysql() { if [[ "$DISTRO_ID" == "debian" && "$DISTRO_CODENAME" =~ ^(trixie|forky|sid)$ ]]; then msg_info "Debian ${DISTRO_CODENAME} detected → using MySQL 8.4 LTS (libaio1t64 compatible)" - if ! download_gpg_key "https://repo.mysql.com/RPM-GPG-KEY-mysql-2023" "/etc/apt/keyrings/mysql.gpg" "dearmor"; then + # The 2023 key name expired on 2025-10-22; the 2025 file is the same key, extended. + # bookworm's packages need libaio1, which trixie no longer has. + if ! download_gpg_key "https://repo.mysql.com/RPM-GPG-KEY-mysql-2025" "/etc/apt/keyrings/mysql.gpg" "dearmor"; then msg_error "Failed to import MySQL GPG key" return 7 fi @@ -1127,7 +1129,7 @@ setup_mysql() { cat >/etc/apt/sources.list.d/mysql.sources <